This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/dns-wg@ripe.net/
DNS recommendations - the paper
- Previous message (by thread): DNS recommendations - the paper
- Next message (by thread): DNS recommendations - the paper
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Piet Beertema
Piet.Beertema at cwi.nl
Wed Nov 25 12:08:10 CET 1998
CNAMEs map nicknames to cannonical names. Fortunately they're not *that* agressive. :-) CNAMEs have very few uses (see above example, RFC 2317, ...). Be especially aware that nicknames must not be used as the right hand of NS, MX, ... RRs. Having CNAMEs in the RHS of an NS RR is not explicitly forbidden (yet?), so there's only an indirect way to explain why they are: they collide with glue RRs, leading to a violation of the rule that CNAMEs may not have any other RRs associated with them: XX. SOA () ns.foo.xx. A 1.2.3.4 foo.xx. NS ns.foo.xx. foo.xx. SOA () @ NS ns.foo.xx. ns.foo.xx. CNAME myhost.foo.xx. This leads to the illegal combination: ns.foo.xx. CNAME myhost.foo.xx. ns.foo.xx. A myhost.foo.xx. but not [visibly] in either of the zone files themselves! Piet
- Previous message (by thread): DNS recommendations - the paper
- Next message (by thread): DNS recommendations - the paper
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ dns-wg Archives ]