Reverse problems

[Joseph S D Yao]

On Wed, Jul 05, 2000 at 03:23:07PM -0700, keith at mail.telestream.com wrote:
> I have two /24's that my upstream is pulling ptr's from us for.
> The problem is that one of the /24's will reverse just fine where the
> other will not if querying from any ns not associated with verio or
> myself. I'm curious if this could be a problem on my end or there
> end. Here is all the info. Hope this isn't to general a question.
> 
> /24 #1     205.238.16/24
> /24 #2     205.238.4/24
> 
> My name server  ns.telestream.com
> Upstream name servers  c.ns.verio.net   u.ns.verio.net
> 
> If I do a reverse lookup on any IP in either /24 they work fine if
> querying my server or either of the verio ns servers. If using some other
> ns to query the 205.238.16/24, it fails where the 205.238.4/24's
> will work just fine.
> Any idea's where the problem may be? Thanks for any and all info. 
> If I've not given enough info let me know. 

16.238.205.in-addr.arpa	nameserver = NS1.VERIO.NET
16.238.205.in-addr.arpa	nameserver = NS2.VERIO.NET
16.238.205.in-addr.arpa	nameserver = NS0.VERIO.NET

4.238.205.in-addr.arpa	nameserver = NS1.VERIO.NET
4.238.205.in-addr.arpa	nameserver = NS2.VERIO.NET
4.238.205.in-addr.arpa	nameserver = NS0.VERIO.NET

*** No address information is available for "1.16.238.205.in-addr.arpa."

1.4.238.205.in-addr.arpa	name = router.telestream.com
4.238.205.in-addr.arpa	nameserver = C.NS.VERIO.NET
4.238.205.in-addr.arpa	nameserver = U.NS.VERIO.NET
C.NS.VERIO.NET	internet address = 129.250.35.33
U.NS.VERIO.NET	internet address = 192.67.14.17

It looks like Verio has an inconsistency in its name server lists for
4.238.205.in-addr.arpa.  Nevertheless, Verio has a reverse-DNS entry
for 1.4.238.205.in-addr.arpa.

I have either picked a bad number for the 16.* network, or Verio does
not have it entered correctly - or, possibly, in the right name servers.

Good luck.

-- 
Joe Yao				jsdy at cospo.osis.gov - Joseph S. D. Yao
COSPO/OSIS Computer Support					EMT-B
-----------------------------------------------------------------------
This message is not an official statement of COSPO policies.