Corrupt cache

[Kevin Darcy]

org.com appears to have a wildcard record, so it happily matches
www.bingo-lan.org.com, openaccess.org.com, and any other query in org.com that you

may happen to throw its way.

But there's no reason to think that the org.com domain has any relationship to the

bingo-lan.org or openaccess.org domains.

A better question is: why were you querying names like www.bingo-lan.org.com in
the first place? Do you have some screwy resolver configuration somewhere on your
network?

- Kevin

baywood wrote:

> I recently posted about problems w/ home.com not resolving and a corrupt
> cache was mentioned as a possibility. The other day I was digging around
> trying to sort out openaccess.org and associated domains when
> www.bingo-lan quit resolving. I found the following in the dumped cache
>
> $ORIGIN org.com.
> www.bingo-lan           85406   A       208.191.14.252
> openaccess              73596   A       208.191.14.252
>
> That IP# seems to have no connection at all and what's up w/ the org.com.
> origin?
>
> Oppenacces.org has DNS problems but it doesn't seem that should cause
> cache corruption. How did it happen?, How often does it happen? How do
> I know when it happens? and Is there anything I can do to prevent it?
>
> $ host 208.191.14.252
> 252.14.191.208.in-addr.arpa. domain name pointer 208-191-14-252.ded.swbell.net.
>
> $ host www.bingo-lan.org
> www.bingo-lan.org. has address 204.201.133.111
>
> $ host openaccess.org
> $ host www.openaccess.org
> www.openaccess.org. is an alias for apollo.openaccess.org.
> apollo.openaccess.org. has address 204.201.133.10