What it means
A nameserver answers over UDP but not over TCP. DNS normally uses UDP, but switches to TCP when an answer is too large for one UDP packet, which is common with DNSSEC, long TXT records and many records at one name.
Why it matters
Large answers can't be delivered, so the records that need them fail for everyone. DNSSEC-signed zones are hit hardest. The DNS standards require TCP, and a firewall that only allows UDP port 53 is the usual cause.
How to fix it
- Check the server's firewall and any network firewall in front of it: allow TCP port 53 inbound, not only UDP.
- If the server runs behind a load balancer, check that it forwards TCP as well.
- If it's a provider's server, report the problem to the provider.
Check it worked
Run the DNSSEC and nameserver check again. The transports column should show TCP as answering for every server.