If I do:
dig @localhost +short +trace somehost.okstate.edu
on a server authoritative for the okstate.edu domain, I would
expect resolution via that authoritative system. I do get it but
the query takes the scenic route and I get all the root name
servers just as if the query was for some host
-Original Message-
From: Martin McCormick mar...@dc.cis.okstate.edu
Date: Wednesday, November 7, 2012 1:12 PM
To: bind-users@lists.isc.org bind-users@lists.isc.org
Subject: Should Root Servers Always be Queried First? bind9.7.7
If I do:
dig @localhost +short +trace somehost.okstate.edu
, November 07, 2012 1:13 PM
To: bind-users@lists.isc.org
Subject: Should Root Servers Always be Queried First? bind9.7.7
If I do:
dig @localhost +short +trace somehost.okstate.edu
on a server authoritative for the okstate.edu domain, I would expect
resolution via that authoritative system. I do
: Wednesday, November 07, 2012 1:13 PM
To: bind-users@lists.isc.org
Subject: Should Root Servers Always be Queried First? bind9.7.7
If I do:
dig @localhost +short +trace somehost.okstate.edu
on a server authoritative for the okstate.edu domain, I would expect
resolution via that authoritative
Thanks to all who reminded me how dig resolves lookups.
I have since learned that we are apparently having
intermittent network issues that are causing a lot of systems to
behave oddly and our DNS's are only reflecting those conditions.
We were taking anywhere from 0 milliseconds
5 matches
Mail list logo
