DNS Problem: Help!

[Simon Waters]

Mike Diggins wrote:
> 
> The IP address for their
> name server NS.CGOCABLE.NET comes back as 24.226.1.11 which is wrong, it's
> not even a name server. It should be 24.226.1.94! If I restart named it
> sometimes picks up the correct address. I just restarted both my name
> servers and find that they have, once again, an incorrect address.

You must run BIND 8 or earlier, as the correct thing to do would
be to ignore the whole domain like BIND 9 should ;-). Upgrade!

The wrong IP address is because of stale glue. The gtld-servers
think it is 24.226.1.11, and pass this stale data along.
 
> Is there anyway to force our name servers to lookup
> this information again without restarting named? Any help would be
> appreciated.

Of the three IP address for the name servers for this /24 two
are lame and one is not a name server.

If the zone is further delegated from the ISP to the customer
servers, you could slave the delegated zone, or mock up a
working zone for the IP addresses if it is just to satify the
requirement to reverse lookup correctly, and thus bypass the ISP
config, otherwise I'd say it is the customers problem if there
ISP is can't run their DNS correctly.

 Simon