al Message-
From: bind-users On Behalf Of Timothy
Metzinger
Sent: Tuesday, October 23, 2018 8:13 PM
To: bind-users@lists.isc.org
Subject: RE: Strange DIG behavior on Windows 10:
I see NO outgoing bits on the wire, bolstering my theory that DIG isn't finding
name servers in the registry. NSLO
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 wit
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 anyw
That's a good Avenue to explore I will see if I can find any differences
Tim Metzinger
703.963.3015
From: bind-users on behalf of Kevin Darcy
Sent: Tuesday, October 23, 2018 6:44:52 PM
To: bind-users@lists.isc.org
Subject: Re: Strange DIG behavior on Wi
To be honest, I don't have a lot of experience running dig on Windows, but
I assume it would use the same resolvers as everything else, in which case
they're either statically defined (typically through Control Panel) or
assigned via DHCP.
One thing to consider, though: on Windows, resolvers tend
I have two windows 10 pro boxes, both with Bind 9.12.3 tools installed. On one
machine, entering "dig" by itself gives me back the root server list as
expected. On the other machine, I get an error that says no name servers could
be contacted.
However, if I specify the local name server on t
6 matches
Mail list logo
