To:
Johan Ihren <johani@autonomica.se>
Cc:
"Tony Hain" <alh-ietf@tndh.net>, "Nathan Jones" <nathanj@optimo.com.au>, ngtrans@sunroof.eng.sun.com, namedroppers@ops.ietf.org, ipng@sunroof.eng.sun.com, dnsop@cafax.se
From:
Jun-ichiro itojun Hagino <itojun@iijlab.net>
Date:
Wed, 15 Aug 2001 20:36:09 +0900
In-reply-to:
johani's message of 15 Aug 2001 13:27:07 +0200. <2chev9k1h0.fsf@snout.autonomica.se>
Sender:
owner-dnsop@cafax.se
Subject:
Re: (ngtrans) Joint DNSEXT & NGTRANS summary
>> I don't understand what you are saying, AT ALL. I'm not using >> forwarding configuration. you must have some assumption in >> your head which is not presented here. > >Ok. Before I repeat the mistake of guessing at your configuration I >suggest you tell me about it. > >Personally I use a forwarding config for v6-only nameservers and I >believe that this is by far the most common case. I have been talking about a nameserver, with root.hint, on IPv4/v6 dual stack machine. to be more precise, see below. I never have talked about nameservers on IPv6-only machine, they will never work without some help from IPv4/v6 dual stack nameserver. (and it is rather unrealistic to talk about nameeservers in IPv6-only network today...) itojun --- # $NetBSD: named.conf,v 1.5 2000/03/01 11:06:29 itojun Exp $ # boot file for secondary name server # Note that there should be one primary entry for each SOA record. options { directory "/etc/namedb"; listen-on-v6 { any; }; }; zone "." { type hint; file "root.cache"; }; zone "localhost" { type master; file "localhost"; }; zone "127.IN-ADDR.ARPA" { type master; file "127"; };