Reverse Delegation Problem.

Barry Margolin barmar at genuity.net
Mon Mar 18 19:43:34 UTC 2002


In article <a75e5r$k17 at pub3.rc.vix.com>, Aaron Endly  <aaron at nac.net> wrote:
>
>I currently have BIND setup to deligate DNS to a customer of mine.  This is 
>the problem that i have.  When i go to a remote nameserver and do an 
>nslookup, i get a server failed response when doing a reverse lookup.  If i 
>go to the nameserver that i am delegation the request to, it works 
>fine.  If i then go to my nameserver, it also works, showing that the 
>delegation appears to work.  Here is where it gets weird.  If i go back to 
>the remote nameserver, it all of a sudden works.  It seemes to only start 
>to work after i make the request manually to my nameserver, like its 
>cached.  This only seems to happen when i deligate a /24.

What address block are you delegating reverse DNS for?  I know it's not the
192.2.28/24 block you used in your example, because reverse DNS for
192.2/16 is delegated to us, not you.

If you don't provide this information, it's almost impossible for us to
diagnose the problem.

-- 
Barry Margolin, barmar at genuity.net
Genuity, Woburn, MA
*** DON'T SEND TECHNICAL QUESTIONS DIRECTLY TO ME, post them to newsgroups.
Please DON'T copy followups to me -- I'll assume it wasn't posted to the group.


More information about the bind-users mailing list