I see NO outgoing bits on the wire, bolstering my theory that DIG isn't finding name servers in the registry. NSLOOKUP works fine. There's no difference between the working and non working PC in the name servers listed in all the interfaces in ifconfig /all. Registry values for HKLM\system\currentcontrolset\services\tcpip\parameters\dhcpnameserver are identical.
I've deinstalled and reinstalled BIND. This is so weird. -----Original Message----- From: bind-users <bind-users-boun...@lists.isc.org> On Behalf Of Grant Taylor via bind-users Sent: Tuesday, October 23, 2018 6:55 PM To: bind-users@lists.isc.org Subject: Re: Strange DIG behavior on Windows 10: On 10/23/2018 04:21 PM, Timothy Metzinger wrote: > At this point I'm stumped and welcome any suggestions. Trust the bits on the wire. What sort of outgoing DNS queries do you see when you run dig on the problematic system without specifying the DNS server? Can you find that server listed anywhere in the output of ifconfig /all? (I think that's the command, it's been too long.) -- Grant. . . . unix || die _______________________________________________ Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
