dig printout doesn't appear to match reality

[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 of them were fixed up correctly, but two of them aren't 100%.  The issue
was discovered because I have a cron job that gives me the top 20 hosts that
are generating "cache denied".  This cron job has alerted me to more
inconsistencies than I care to mention. =)

Frank

-----Original Message-----
From: SM [mailto:sm at resistor.net] 
Sent: Saturday, May 16, 2009 12:46 PM
To: Frank Bulk
Cc: bind-users at 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 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. 28800   IN      NS      dns.mtcnet.net.

This is unrelated to your original question.  dns.mtcnet.net does not
resolve.

Regards,
-sm