Michael Nottebrock
2007-Jul-16 21:19 UTC
Problems with named default configuration in 6-STABLE
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@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/20070716/bc61c1bf/attachment.pgp
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@freebsd.org > (/^ ^\) | FreeBSD - The Power to Serve | http://www.freebsd.org > \u/ | K Desktop Environment on FreeBSD | http://freebsd.kde.orgHi 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"; }; Yuri -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 187 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20070717/3891f8ff/attachment.pgp