Delegating reverse DNS to a customer

[Ben Croswell]

The issue is probably that you need to delegate the 251.250.63.in-addr.arpa
to your client in the 250.63.in-addr.arpa zone.
If you load 251.250.63.in-addr.arpa to try and delegate it, your servers
will answer for it because they load it.

Think of it in the same mind of delegating a forward subdomain of a domain
you load. If you want to delegate foo.bar.com to someone you put the NS
records in bar.com not foo.bar.com.

-- 
-Ben Croswell

On Tue, Aug 18, 2009 at 8:31 AM, Tim Huffman <Tim at bobbroadband.com> wrote:

>  Guys,
>
>
>
> We’re a smallish (but growing) ISP, and we’ve been asked by one of our
> customers to delegate reverse DNS for 63.250.251.0/24 to their DNS
> servers, ns1.emns.com – ns4.emns.com. Unfortunately, we’ve never had to
> delegate DNS to a customer before, and we’re having problems getting it to
> work.
>
>
>
> We’re running BIND 9.5.1 on Fedora.
>
>
>
> Can anyone give me an example of how this should be done in named.conf and
> the file 251.250.63.in-addr.arpa.zone? I’d appreciate it!
>
>
>
> --
>
> Tim
>
>
>
> _______________________________________________
> bind-users mailing list
> bind-users at lists.isc.org
> https://lists.isc.org/mailman/listinfo/bind-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.isc.org/pipermail/bind-users/attachments/20090818/18473a25/attachment.html>