Someone asked me why the domain viewtrip.com wasn’t working on our network. IE was returning that it couldn’t find the server. This soon pointed in the direction of DNS. The nslookup of the domain also failed. The Global Logs in the DNS Manager returned some 5504 events.
The DNS server encountered an invalid domain name in a packet from 126.96.36.199. The packet will be rejected. The event data contains the DNS packet.
After hitting Google with this event it soon gave me a couple of options to solve it. A big thank you goes to Shilpesh Desai! Source
- Check following registry key and value set for it:
According to KB 198410 it should have a non-zero value
- Packet was forwarded to non-recursive DNS server. I will recommend to switch to forwarders for few days to check if that helps.
- Server is quering for DNAME record, which is not supported. Reponses containing DNAME (rrtype – 0x0027) record.
- Extended DNS (EDNS) packets are received but the server that is attempting to resolve the EDNS traffic doesn’t support EDNS or have it enabled. An easy workaround is to disable EDNS.
dnscmd /Config /EnableEDnsProbes 0
One disadvantage of this solution is that DNSSEC is not possible anymore as this relies on the EDNS principle.