Frederic Beck <frederic.beck@loria.fr> writes: > /etc/bind/ipv6.renumbering.loria.fr: > @ IN SOA ipv6.renumbering.loria.fr. luffy.loria.fr. ( The first two parametres after "SOA" must be the name of the primary server and the email address of the administrator (with "@" changed to "."). > /etc/bind/2001:660:4501:aaaa_64 > @ IN SOA ipv6.renumbering.loria.fr. luffy.loria.fr. ( Ditto. > $ORIGIN a.a.a.a.1.0.5.4.0.6.6.0.1.0.0.2.ip6.int That can't be right: the name doesn't end with a dot, so BIND treats it as a subdomain of the current origin, resulting in "a.a.a.a.1.0.5.4.0.6.6.0.1.0.0.2.ip6.int.a.a.a.a.1.0.5.4.0.6.6.0.1.0.0.2.ip6.arpa." But adding the dot wouldn't be right either, as the origin would then be outside the zone. If you want to serve the same data for both ip6.int and ip6.arpa, I think the easiest way is to remove the $ORIGIN directive and put two zone statements in named.conf, both pointing to the same zone file. > *** Can't find aria.ipv6.renumbering.loria.fr: No answer It might be helpful to enable rndc querylog and see whether the query gets to the server.
Attachment:
pgpnXvAWbSUOy.pgp
Description: PGP signature