DDNS and inverse resolution

Kevin Darcy kcd at daimlerchrysler.com
Wed Nov 21 00:41:33 UTC 2001


Paco Orozco wrote:

> Hiya,
>
> I've got a bit trouble designing my DNS service.
>
> I've got three DNS servers, one is primary of A.COM, other is
> secondary of A.COM and the other is only used as DDNS server.
>
> Here is it:
>
> SERVER1:    Primary A.COM and 168.192.in-addr.arpa
> SERVER2:   Secondary A.COM and 168.192.in-addr.arpa
> SERVER3:   Primary DDNS.A.COM
>
> I'd like to use DDNS only in SERVER3. It will have all the DDNS
> records under DDNS.A.COM domain. This DDNS records have PTR records
> under 168.192.in-addr.arpa domain, so "someone" has to be able to
> modify this records.
>
> How can it be done? I've no problem to DDNS under DDNS-A.COM, but I'd
> like not to allow DDNS in 168.192.in-addr.arpa.

You could delegate each of the addresses you care about as a separate
zone to SERVER3, e.g. 1.2.168.192.in-addr.arpa could be delegated as a
zone, as could 2.3.168.192.in-addr.arpa, etc..

Another approach, if you want to avoid maintaining all of those zone
definitions, is to adopt a RFC 2317 scheme, where all of the PTR records
are accessed through aliases (CNAMEs). But not all DHCP servers are
necessarily able to deal with RFC 2317 (does anyone have a list of which
ones can and which ones cannot?)...




More information about the bind-users mailing list