Inverse DNS screwed up?

Re: Inverse DNS screwed up?

From:

Date:

Time:

At 12:07 AM -0600 12/17/99, Mia's Virtual Post Office wrote:
>Just curious, I noticed pretty much all the reverse dns records on our
>206.190.23.* subnet have disappeared. Basically they're just reversing to
>the name of the ip instead of the name of the actual host.
>
>Name: 204.192.23.190.206.in-addr.arpa
>Address: 206.190.23.204
>
>should reverse to home.mia.net

And it does:

Answer:
204.23.190.206.in-addr.arpa. CNAME 204.192.23.190.206.in-addr.arpa.
204.192.23.190.206.in-addr.arpa. PTR home.mia.net.

Authority:
192.23.190.206.in-addr.arpa. NS homer.alpha.net.
192.23.190.206.in-addr.arpa. NS helen.alpha.net.
192.23.190.206.in-addr.arpa. NS jer.mia.net.

Additional:
homer.alpha.net. A 156.46.10.10
helen.alpha.net. A 156.46.10.20
jer.mia.net. A 206.190.23.194

I notice that your server (jer.mia.net) has some bad data in its cache, data which should have been purged by now. Here's the current data:

23.190.206.in-addr.arpa. 86400 SOA homer.alpha.net.
manager.alpha.net.
1999121501 ; serial
10800 ; refresh (3 hours)
3600 ; retry (1 hour)
604800 ; expire (7 days)
86400 ; minimum (1 day)

Here's what your server has cached:

23.190.206.in-addr.arpa. 31502 SOA homer.alpha.net.
manager.alpha.net.
1999121500 ; serial
10800 ; refresh (3 hours)
3600 ; retry (1 hour)
604800 ; expire (7 days)
86400 ; minimum (1 day)

Note the difference in serial numbers. Your server also has this cached:
204.23.190.206.in-addr.arpa. 20253 PTR 204.192.23.190.206.in-addr.arpa.

This record no longer exists on the authoritative servers (homer and helen at your ISP). Looks like your ISP did something stupid on Wednesday, then fixed it. This should clear up momentarily.
____________________________________________________________________
Chris Buxton cbuxton@menandmice.com
Men & Mice http://www.menandmice.com
Makers of: QuickDNS Pro

Sales:
888/4-DPOINT

Support:
858/452-3696