Re: dig printout doesn't appear to match reality

2009-05-16 Thread Mark Andrews
In message , "Frank Bulk" write s: > Wow, I wasn't aware of that nuance. I have been making incorrect > assumptions. > > It doesn't make sense to me how DNS3.UIOWA.EDU can return the correct cached > result for the NS records of sioux-center.k12.ia.us but an incorrect "norec" > result. Doesn't

RE: dig printout doesn't appear to match reality

2009-05-16 Thread Frank Bulk
riginal Message- From: SM [mailto:s...@resistor.net] Sent: Saturday, May 16, 2009 12:46 PM To: Frank Bulk Cc: bind-users@lists.isc.org Subject: Re: dig printout doesn't appear to match reality At 08:53 16-05-2009, Frank Bulk wrote: >It appears that dig is printing results that it attribut

Re: dig printout doesn't appear to match reality

2009-05-16 Thread SM
At 08:53 16-05-2009, Frank Bulk wrote: It appears that dig is printing results that it attributes to the wrong server. While troubleshooting an inconsistent NS issue (upstream from us), a trace [snip] sioux-center.k12.ia.us. 28800 IN NS ns1.netins.net. sioux-center.k12.ia.us. 288

Re: dig printout doesn't appear to match reality

2009-05-16 Thread sthaug
> If the dns3.uiowa.edu's cache was flushed for sioux-center.k12.ia.us, what > do you think the query results for > dig @DNS3.UIOWA.EDU sioux-center.k12.ia.us ns +noall +answer > would be? I think you would get what you get right now with +norec, *until* the name server acquired some of the

RE: dig printout doesn't appear to match reality

2009-05-16 Thread Frank Bulk
-Original Message- From: sth...@nethelp.no [mailto:sth...@nethelp.no] Sent: Saturday, May 16, 2009 11:35 AM To: frnk...@iname.com Cc: cbux...@menandmice.com; bind-users@lists.isc.org Subject: Re: dig printout doesn't appear to match reality > It doesn't make sense to me how D

Re: dig printout doesn't appear to match reality

2009-05-16 Thread sthaug
> It doesn't make sense to me how DNS3.UIOWA.EDU can return the correct cached > result for the NS records of sioux-center.k12.ia.us but an incorrect "norec" > result. Doesn't specifying "no recursion" mean that it has to be either > authoritative for that domain or have the entry cached in order

RE: dig printout doesn't appear to match reality

2009-05-16 Thread Frank Bulk
To: frnk...@iname.com Cc: bind-users@lists.isc.org Subject: Re: dig printout doesn't appear to match reality One could certainly argue that DNS3.UIOWA.EDU should not behave this way. Steinar Haug, Nethelp consulting, sth...@nethelp.no ___ bind-

RE: dig printout doesn't appear to match reality

2009-05-16 Thread Frank Bulk
Buxton [mailto:cbux...@menandmice.com] Sent: Saturday, May 16, 2009 11:09 AM To: Frank Bulk Cc: bind-users@lists.isc.org Subject: Re: dig printout doesn't appear to match reality If you send the server a recursive query, you get an answer from its cache. If you sent it an iterative query

Re: dig printout doesn't appear to match reality

2009-05-16 Thread sthaug
> It appears that dig is printing results that it attributes to the wrong > server. Not really. > While troubleshooting an inconsistent NS issue (upstream from us), a trace > (at the end of this message) shows that DNS3.UIOWA.EDU listed two NS > records, when in fact, if you query DNS3.UIOWA.EDU

Re: dig printout doesn't appear to match reality

2009-05-16 Thread Chris Buxton
If you send the server a recursive query, you get an answer from its cache. If you sent it an iterative query, you get a referral from its authoritative zone. $ dig @DNS3.UIOWA.EDU sioux-center.k12.ia.us ns +noall +auth +norec ; <<>> DiG 9.4.3-P1 <<>> @DNS3.UIOWA.EDU sioux-center.k12.ia.us n