Problems with named default configuration in 6-STABLE

[Michael Nottebrock]

On Tuesday, 17. July 2007, Yuri Pankov wrote:
> On Mon, Jul 16, 2007 at 11:19:41PM +0200, Michael Nottebrock wrote:
> > I finally updated my desktop from 5.5-RELEASE to 6-STABLE. This got me a
> > new named.conf, which I modified to run named as a local resolver, like I
> > had before:
> >
> > listen-on       { 127.0.0.1; };
> > listen-on-v6    { ::1; };
> > forward only;
> > forwarders {
> >      192.168.8.1;
> > };
> >
> > Everything else is default. However, with this default configuration,
> > named will not resolve any hosts of my local domain (my.domain), which
> > uses addresses in the 192.168.8 subnet. My dns server on 192.168.8.1,
> > running 6.2-RELEASE, has a very simple dynamic dns setup: a zone
> > "my.domain" and a reverse zone 8.168.192.in-addr.arpa which are both
> > dynamically updated by dhcpd.
> >
> > To make this work again, I had to delete everything in the default
> > named.conf from "/*      Slaving the following zones from the root [...]"
> > to "zone "ip6.int"                  { type master;
> > file "master/empty.db"; };".
> >
> > I'm a DNS n00b, but I suspect that such drastic measures shouldn't be
> > required and somehow my setup is flawed. What can I do to make this work
> > right?
> >
> >
> > Cheers,
> > --
> >    ,_,   | Michael Nottebrock               | lofi at freebsd.org
> >  (/^ ^\) | FreeBSD - The Power to Serve     | http://www.freebsd.org
> >    \u/   | K Desktop Environment on FreeBSD | http://freebsd.kde.org
>
> Hi Michael,
>
> If I understood you correctly, you can't resolve 8.168.192.in-addr.arpa
> anymore, and the line below (from default named.conf) is the cause:
>
> zone "168.192.in-addr.arpa"   { type master; file "master/empty.db"; };

Yes - and this:

zone "." {
        type slave;
        file "slave/root.slave";
        masters {
                192.5.5.241;    // F.ROOT-SERVERS.NET.
                192.228.79.201; // B.ROOT-SERVERS.NET.
                192.33.4.12;    // C.ROOT-SERVERS.NET.
                192.112.36.4;   // G.ROOT-SERVERS.NET.
                193.0.14.129;   // K.ROOT-SERVERS.NET.
        };
        notify no;
};

prevents me from resolving hostnames in "my.domain". What I'm still wondering 
though, is this an oversight or by design? I can't imagine setups like mine 
are very rare. Doug?

-- 
   ,_,   | Michael Nottebrock               | lofi at freebsd.org
 (/^ ^\) | FreeBSD - The Power to Serve     | http://www.freebsd.org
   \u/   | K Desktop Environment on FreeBSD | http://freebsd.kde.org
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 187 bytes
Desc: This is a digitally signed message part.
Url : http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20070717/b8e3bb47/attachment-0001.pgp