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
In article ,
"Taylor, Gord" wrote:
> Also need to ensure the allow-query-cache ACL on the recursive server allows
> the client. Otherwise, name resolution may work the first time
> (allow-recursion), but not the 2nd time (allow-query-cache) since the result
> is cached.
Only if he has an exp
--- On Sun, 12/20/09, Barry Margolin wrote:
> From: Barry Margolin
> Subject: Re: strange dig behavior
> To: comp-protocols-dns-b...@isc.org
> Date: Sunday, December 20, 2009, 10:59 PM
> In article ,
> Pamela Rock
> wrote:
>
> > I've got the following
-users-bounces+gord.taylor=rbc@lists.isc.org
To: comp-protocols-dns-b...@isc.org
Sent: Sun Dec 20 22:59:12 2009
Subject: Re: strange dig behavior
In article ,
Pamela Rock wrote:
> I've got the following three scenarios
>
> The client can query a domain A residing on a
In article ,
Pamela Rock wrote:
> I've got the following three scenarios
>
> The client can query a domain A residing on a recursive name server.
What do you mean by a domain "residing" on a recursive nameserver? If a
domain resides on a server, the server should be authoritative for that
d
Pamela Rock wrote:
I don't know what is causing the refused. IP tables is off
everywhere, and there are no ACL's on routers or firewalls.
Has nothing to do with firewalls (or ACLs on routers).
The only error I'm seeing is the following in the debug log
20-Dec-2009 19:21:09.443 query-errors
I've got the following three scenarios
The client can query a domain A residing on a recursive name server.
The client can query a domain B on an authratative name server.
When client queries domain B through the RNS, a Status: refused results.
I don't know what is causing the refused. IP tabl
12 matches
Mail list logo
