The cache on my name server is up to date. When it was given this old A record for B at 3:55am EDT this morning it complained:

20-Jun-2006 07:55:36.245 default: warning: check_hints: A records for B.ROOT-SERVERS.NET class 1 do not match hint records

I'm wondering why it accepted this address. If one of the root servers had handed it out I assume other people would have seen the same thing. If it wasn't given this address by a root server then I thought it wouldn't accept it. Is that the case?

On Tue, Jun 20, at 12:00%P so wrote Pete Ehlke (pde@rfc822.net):

> On Tue Jun 20, 2006 at 17:56:19 +0200, Peter Dambier wrote:
> >Maria Iano wrote:
> >> This morning, on one of my name servers I noticed this error message (time in GMT):
> >>
> >> 20-Jun-2006 07:55:36.245 default: warning: check_hints: A records for B.ROOT-SERVERS.NET class 1 do not match hint records
> >>
> >> When I perform a lookup of B.ROOT-SERVERS.NET against this name server, it gives me no answer:
> >>

> [ results snipped ]
> >>
> >> I've checked against 8 other name servers of ours and have not seen this issue on any of those - they all have the correct IP for B.ROOT-SERVERS.NET. I'm very glad to see that my name server does not seem to trust this bad A record for B.ROOT-SERVERS.NET.
> >>
> >> Any idea how/why this happened? Anything I should do?
> >>
> >> Thanks,
> >> Maria
> >>

> >
> >
> >I just tried
> >
> >host_look("128.9.0.107","128.9.0.107","2148073579").
> >host_name("128.9.0.107","ns1.isi.edu").
> >

> [ more results snipped ]
> >
> >No harm done. Seems isi.edu have their own internal root and they are
> >a copy of one of the root-server.net.
> >
> >

> b's address was changed in January of 2004.
>
> http://www.root-servers.org/news/new-ip-b.html
>