Corrupt cache

[Simon Waters]

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?

Looks like "org.com" have a wild card entry, and your browser,
or resolver is trying other extensions after the original
".org".

The browser or resolver is probably doing this because
openaccess.org and bingo-lan.org are so mucked up it doesn't get
an answer (or an answer in time).

This will go away if openaccess.org or www.bingo-lan.org fix
their DNS. These DNS servers are mostly lame, looks like they
get no meaningful checks or maintenance.

; <<>> DiG 9.2.0rc7 <<>> org.com axfr @ns1.meridian-ds.com
;; global options:  printcmd
org.com.                86400   IN      SOA    
ns1.meridian-ds.com. kurt\@meridian-ds.com. 2001041701 10800
3600 14400 86400
org.com.                86400   IN      NS     
ns1.meridian-ds.com.
org.com.                86400   IN      NS     
ns2.meridian-ds.com.
org.com.                86400   IN      A       208.191.14.252
ftp.org.com.            86400   IN      A       208.191.14.252
*.org.com.              86400   IN      A       208.191.14.252
www.org.com.            86400   IN      A      
208.191.14.252