7 msgshow all RECORDS
4 msgbind server fails to deliver

Reverse Problem
\ Chris Wittenberg (26 Feb 2005)
. \ Barry Margolin (26 Feb 2005)

6 msgMS DNS - Internal WWW Resolving to External IP
2 msgNonexistent zone respond on query
4 msgdetails of bug reports
1 msgsquid + caching name server
5 msgReverse DNS Delegation howto?
7 msgDSL/DNS Confusion
8 msgWhy wont this MX record work properly?
1 msgMemory leak in bind 9.3.0 with DNSSEC
3 msgI: Problem w startup (disperatly)
8 msgstops answering at same time every day
3 msgProblem w startup (disperatly)
4 msgcannot get reverse dns to work for 65.58.240.197
2 msgquestion: setup
2 msgPLZ ANYBODY KNOWS WHY ICAP PROTOCOL IS USED?
16 msgFail-over
1 msgGUI to add A & PTR records to solaris bind9?
1 msgBind Configuration - Is it correct?
Subject:Reverse Problem
Group:Bind9-users
From:Chris Wittenberg
Date:26 Feb 2005


 
Hello,

I'm running bind 9.2.1 on a solaris box.

We noticed some inconsistencies with email between us and usc.edu -
causing some email to bounce with an error "you don't have permission
to send email".

Further checking revealed that of our ip ranges (we have 4 class C's),
one of them will not do a reverse lookup unless you are doing the
lookup directly from our server: 206.117.187.1. According to my logs,
there are no problems loading the zone (207.151.131), and all lookups
work perfectly - but only if the lookup is done using our server.

If you do a "host" or "nslookup" from another server, I get:
Host 8.131.151.207.in-addr.arpa not found: 3(NXDOMAIN)

All other networks perform the reverse lookup properly (i.e.,
206.117.187, 206.117.219), and all forward resolution works properly.

I am royally stumped as to why just one range wouldn't be working. Can
anyone shed some light on what I should check on?

Thanks very much for any help! If you need more info, just let me know.

-Chris








© 2004-2008 readlist.com