Reverse Lookup not working

Joseph S D Yao jsdy at cospo.osis.gov
Mon Oct 2 22:14:50 UTC 2000


On Mon, Oct 02, 2000 at 05:42:47PM -0400, Seguin, Ronald wrote:
> I don't understand why one of the reverse lookups failed and the other 
> succeeded based upon the in-addr.arpa files defined???????
> 
> nslookup 206.47.229.167
> Server:  pluto.in.bellnexxia.net
> Address:  205.207.237.48
> 
> *** pluto.in.bellnexxia.net can't find 206.47.229.167: Non-existent
> host/domain
> 
> nslookup 206.108.105.62
> Server:  pluto.in.bellnexxia.net
> Address:  205.207.237.48
> 
> Name:    sms2-quebec14-fe7-0.in.bellnexxia.net
> Address:  206.108.105.62
> 
> more 229.47.206.in-addr.arpa
> 
> 21              IN PTR  sms1-hamilton14.in.bellnexxia.net.
> 38              IN PTR  sms1-windsor12.in.bellnexxia.net.
> 54              IN PTR  sms1-sudbury98.in.bellnexxia.net.
> 74              IN PTR  sms1-london14.in.bellnexxia.net.
> 183             IN PTR  sms2-london14.in.bellnexxia.net.
> 92              IN PTR  sms1-kitchener06.in.bellnexxia.net.
> 102             IN PTR  sms1-kingston08.in.bellnexxia.net.
> 156             IN PTR  sms1-quebec14.in.bellnexxia.net.
> 167             IN PTR  sms2-quebec14.in.bellnexxia.net.
> 
> more 105.108.206.in-addr.arpa
> 
> 38              IN PTR  sms5-montreal02-fe7-0.in.bellnexxia.net.
> 42              IN PTR  sms5-montreal02-fe7-1.in.bellnexxia.net.
> 54              IN PTR  sms6-montreal02-fe7-0.in.bellnexxia.net.
> 58              IN PTR  sms6-montreal02-fe7-1.in.bellnexxia.net.
> 73              IN PTR  sms7-montreal02-fe7-0.in.bellnexxia.net.
> 81              IN PTR  sms7-montreal02-fe7-1.in.bellnexxia.net.
> 78              IN PTR  sms8-montreal02-fe7-0.in.bellnexxia.net.
> 85              IN PTR  sms8-montreal02-fe7-1.in.bellnexxia.net.
> 62              IN PTR  sms2-quebec14-fe7-0.in.bellnexxia.net.
> 66              IN PTR  sms2-quebec14-fe7-1.in.bellnexxia.net.

Based on what you are showing us, it should work.  Therefore,
obviously, the problem is in the part that you are not showing us.
;-}

If the second is succeeding at all, you have edited out the SOA and NS
records.  These are required for all zone files.  What are they?

229.47.206.in-addr.arpa	nameserver = ns4.bellglobal.com
229.47.206.in-addr.arpa	nameserver = ns3.bellglobal.com

Authoritative answers can be found from:
ns4.bellglobal.com	internet address = 198.235.216.131
ns3.bellglobal.com	internet address = 198.235.216.130

These are hosted by the bellglobal.com server.  Not by you.

105.108.206.in-addr.arpa	nameserver = TAZ.BELL-NEXXIA.NET
105.108.206.in-addr.arpa	nameserver = PLUTO.BELL-NEXXIA.NET

A lookup for the first name server fails.  A lookup for the second name
server succeeds.  Maybe you need to fix that.

bell-nexxia.net	nameserver = PLUTO.bell-nexxia.net
bell-nexxia.net	nameserver = MICKEY.bell-nexxia.net

PLUTO.bell-nexxia.net	internet address = 205.207.237.48
MICKEY.bell-nexxia.net	internet address = 205.207.237.50

QUESTION: Is it bell-nexxia or bellnexxia?  Or both?  And .com or .net?
Or both?

-- 
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.



More information about the bind-users mailing list