Problems with named default configuration in 6-STABLE
- From: Michael Nottebrock <lofi@xxxxxxxxxxx>
- Date: Mon, 16 Jul 2007 23:19:41 +0200
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@xxxxxxxxxxx
(/^ ^\) | FreeBSD - The Power to Serve | http://www.freebsd.org
\u/ | K Desktop Environment on FreeBSD | http://freebsd.kde.org
Attachment:
signature.asc
Description: This is a digitally signed message part.
- Follow-Ups:
- Re: Problems with named default configuration in 6-STABLE
- From: Yuri Pankov
- Re: Problems with named default configuration in 6-STABLE
- Prev by Date: Re: Problem with KDM not passing to Xorg/KDE after login
- Next by Date: GlidePoint trackpad not detected
- Previous by thread: Promotion Acomba 3 pour 1*
- Next by thread: Re: Problems with named default configuration in 6-STABLE
- Index(es):