dig printout doesn't appear to match reality

2009-05-16 Thread Frank Bulk
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 (at the end of this message) shows that DNS3.UIOWA.EDU listed two NS records, when in fact, if you query DNS3.UIOWA.EDU for the domain in quest

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

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 Frank Bulk
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 specifying "no recursion" mean that it has to be

RE: dig printout doesn't appear to match reality

2009-05-16 Thread Frank Bulk
Thanks for the response. The wheels are already in motion to get this inconsistency resolved. Unfortunately, the stated response time for this state agency is 2 weeks. =( Frank -Original Message- From: sth...@nethelp.no [mailto:sth...@nethelp.no] Sent: Saturday, May 16, 2009 11:20 AM T

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
Ok, now I'm following youI don't live and breathe this like you and Chris do. =) 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? Frank -Original M

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 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 Frank Bulk
Yes, dns.mtcnet.net does not resolve because that host name been deprecated, although the IP address it represented still functions, but only as a caching-only server limited to our customer base. The organization that manages k12.ia.us was informed of the changes over a month ago and almost all o

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