<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:Tahoma
}
--></style>
</head>
<body class='hmmessage'>
Jay,<BR>
<BR>
I see what you're saying. I was missing the difference in the feedback from the recurse / no recurse options. Makes sense. Thanks very much for the excellent help!<BR>
<BR>
Marty<BR>
<BR> <BR>
> Date: Mon, 15 Nov 2010 10:57:40 -0600<BR>> From: jay-ford@uiowa.edu<BR>> To: sun-guru@live.com<BR>> Subject: RE: how to see ALL NS records in a zone file with dig<BR>> <BR>> On Mon, 15 Nov 2010, M. Meadows wrote:<BR>> > Thanks for the reply Jay. Does that work for you? It doesn't work for me.<BR>> <BR>> Yep, it works for me. Here's an example for zone healthcare.uiowa.edu with<BR>> the query answered by an authoritative server for the parent (uiowa.edu).<BR>> <BR>> The query with recursion disabled shows dns-cb returning its view as the<BR>> parent above the uiowa.edu -> healthcare.uiowa.edu delegation cut:<BR>> <BR>> jnford@seatpost: dig +norec +nostats -t ns healthcare.uiowa.edu @dns-cb.uiowa.edu<BR>> <BR>> ; <<>> DiG 9.7.1-P2 <<>> +norec +nostats -t ns healthcare.uiowa.edu @dns-cb.uiowa.edu<BR>> ;; global options: +cmd<BR>> ;; Got answer:<BR>> ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 31651<BR>> ;; flags: qr ra; QUERY: 1, ANSWER: 0, AUTHORITY: 2, ADDITIONAL: 2<BR>> <BR>> ;; QUESTION SECTION:<BR>> ;healthcare.uiowa.edu. IN NS<BR>> <BR>> ;; AUTHORITY SECTION:<BR>> healthcare.uiowa.edu. 86400 IN NS dns1.uihealthcare.com.<BR>> healthcare.uiowa.edu. 86400 IN NS dns2.uihealthcare.com.<BR>> <BR>> ;; ADDITIONAL SECTION:<BR>> dns1.uihealthcare.com. 2305 IN A 129.255.116.10<BR>> dns2.uihealthcare.com. 1178 IN A 129.255.116.11<BR>> <BR>> It returns no answers, just a referral to what it's been told the servers are<BR>> for healthcare.uiowa.edu.<BR>> <BR>> <BR>> The query with recursion enabled shows dns-cb returning the information it<BR>> has cached for healthcare.uiowa.edu:<BR>> <BR>> jnford@seatpost: dig +nostats -t ns healthcare.uiowa.edu @dns-cb.uiowa.edu<BR>> <BR>> ; <<>> DiG 9.7.1-P2 <<>> +nostats -t ns healthcare.uiowa.edu @dns-cb.uiowa.edu<BR>> ;; global options: +cmd<BR>> ;; Got answer:<BR>> ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 29488<BR>> ;; flags: qr rd ra; QUERY: 1, ANSWER: 5, AUTHORITY: 0, ADDITIONAL: 0<BR>> <BR>> ;; QUESTION SECTION:<BR>> ;healthcare.uiowa.edu. IN NS<BR>> <BR>> ;; ANSWER SECTION:<BR>> healthcare.uiowa.edu. 3283 IN NS hc-dc3.healthcare.uiowa.edu.<BR>> healthcare.uiowa.edu. 3283 IN NS hc-dc4.healthcare.uiowa.edu.<BR>> healthcare.uiowa.edu. 3283 IN NS hc-dc5.healthcare.uiowa.edu.<BR>> healthcare.uiowa.edu. 3283 IN NS hc-dc1.healthcare.uiowa.edu.<BR>> healthcare.uiowa.edu. 3283 IN NS hc-dc2.healthcare.uiowa.edu.<BR>> <BR>> It returns answers rather than a referral.<BR>> <BR>> Note that in neither cases is the response authoritative, because dns-cb<BR>> doesn't hold authority over the healthcare.uiowa.edu zone. It has the<BR>> configured hints about how to get to the authoritative servers, & it will<BR>> cache the server list from the authoritative servers.<BR>> <BR>> Is that not the type of behavior you're getting with your servers?<BR>> <BR>> ________________________________________________________________________<BR>> Jay Ford, Network Engineering Group, Information Technology Services<BR>> University of Iowa, Iowa City, IA 52242<BR>> email: jay-ford@uiowa.edu, phone: 319-335-5555, fax: 319-335-2951<BR> </body>
</html>