[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
secondary name server that understands AAAA records
- Subject: secondary name server that understands AAAA records
- From: [email protected] (Francis Dupont)
- Date: Wed, 04 Sep 1996 13:25:33 +0200
- In-reply-to: Your message of Tue, 03 Sep 1996 23:29:01 EDT. <[email protected]>
In your previous mail you wrote:
AAAA is just another RR type. If BIND don't find AAAA record condition
is returned to resolver not found. Then go look for A RR type. I don't
see what the problem is or would be unless folks are trying to alter
BIND Server code? Good luck.
=> it is not so simple. You can look at the return code because
with NXDOMAIN it is not useful to go look for an A RR (or any RR).
Another problem is the order when you have a search list (and you
should have one, see below).
As far as transition spec. Secondaries are not required in DNS (though
useful). Some of the transition spec was left to common sense. If you
want a secondary that supports AAAA records and it don't do IPv6 that
just seems dumb. I don't think we should have to specify this in that
spec. But clearly useful for documentation as we roll out our kits and
products as vendors.
=> the common solution to this problem is to have a special zone
(for instance ipv6.<your domain name>) and to select secondaries
with AAAA support.
- common BINDs are enough for the reverse zone (which uses only PTR RRs).
- it is very easy to add AAAA support to an old BIND. The diffs are
small and can be applied to any architecture. Especially you have *not*
to run IPv6 in order to support AAAA RRs for a secondary.
to try to get an A record) or NOERROR (then there is likely an A RR).
Or is there something else at work here? I've noticed relatively
little discussion of this, or of reverse DNS issues.
=> reverse DNS is much simpler, there is only an issue for IPv4-compatible