More specific reverse DNS?

[Ben Croswell]

If you load the parent of a domain authoritatively and then try to do a zone
forward for a child of that domain, it will only work if there are NS
records in the parent.
The reason being the nameserver sees that it loads and is authoritative for
10.x, and feels there is no reason to follow the forward because the child
doesn't exist.
Simple solution is to put NS records to the domains you intend to forward in
the db.10 domain.

-- 
-Ben Croswell

On Wed, Oct 1, 2008 at 8:25 AM, Marc Haber
<mh+bind-users at zugschlus.de<mh%2Bbind-users at zugschlus.de>
> wrote:

> Hi,
>
> for various reasons, I am running a local bind on my personal
> notebook. I have loaded empty master zones for the reverse DNS ranges
> for RFC1918:
>
> zone "10.in-addr.arpa"      { type master; file "/etc/bind/db.empty"; };
> (similiar statements for 172.16/12 and 192.168/16 snipped)
>
> I also have a forward zone statements for the IP ranges that my company
> uses in its internal network, forwarding to the actual name servers:
>
> zone "2.1.10.in-addr.arpa" {
>        type forward;
>        forwarders { 10.1.2.11; 10.1.2.15; };
>        forward only;
> };
>
> However, it looks like the 10/8 master zone takes preferences, asking
> for 92.2.1.10.in-addr.arpa's PTR record does result in an immediately
> NXDOMAIN without queries being seen on the network.
>
> Do I really need to locally delegate all internal networks from the
> 10.in-addr.arpa zone in addition to the forward statements in my
> named.conf, or is there a way to have bind query the more specific
> loaded zones automatically?
>
> Greetings
> Marc
>
> --
>
> -----------------------------------------------------------------------------
> Marc Haber         | "I don't trust Computers. They | Mailadresse im Header
> Mannheim, Germany  |  lose things."    Winona Ryder | Fon: *49 621 72739834
> Nordisch by Nature |  How to make an American Quilt | Fax: *49 3221 2323190
>
>