Date: Tue, 17 Jul 2007 09:39:59 +0200 From: Volker <volker@vwsoft.com> To: Michael Nottebrock <lofi@freebsd.org> Cc: freebsd-stable@freebsd.org, Yuri Pankov <yuri@darklight.org.ru> Subject: Re: Problems with named default configuration in 6-STABLE Message-ID: <469C724F.1030400@vwsoft.com> In-Reply-To: <200707170920.24692.lofi@freebsd.org> References: <200707162319.41724.lofi@freebsd.org> <20070717052823.GA1277@darklight.org.ru> <200707170920.24692.lofi@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 07/17/07 09:20, Michael Nottebrock wrote:
> 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@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;
The root zone MUST be of type hint. You do not want to be a slave of
the root... don't you? ;)
> 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?
>
Yes, if the servers of the root zone can't be resolved, all queries
will fail.
If you've got a file /etc/namedb/named.root set it like
file "/etc/namedb/named.root";
and change the zone type to "hint" and all should be well again.
Volker
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?469C724F.1030400>