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/[email protected]/
[dns-wg] RIPE's MNAME recommendation
- Previous message (by thread): [dns-wg] RIPE's MNAME recommendation
- Next message (by thread): [dns-wg] RIPE's MNAME recommendation
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Måns Nilsson
mansaxel at sunet.se
Sat Oct 1 13:49:30 CEST 2005
--On den 1 oktober 2005 12.40.09 +0200 Patrik Fältström <paf at cisco.com> wrote: > My suggestion would be to put a domain name there in the domain that > hosts the domain, a hostname that can receive the traffic generated by > any tool that uses the mname in the SOA for something. In the interest of sanity, I'd suggest adding "should answer queries about said domain with the AA bit set" (in addition to swallowing/properly rejecting/processing updates and allowing/properly refusing zone transfers). That is the The Right Thing to do, IMHO, but it might be hard to get that kind of enforcement into any kind of document short of an ops memo inside one organisation. I for one require it for anything I operate. -- Måns Nilsson Systems Specialist +46 70 681 7204 cell KTHNOC +46 8 790 6518 office MN1334-RIPE -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 186 bytes Desc: not available URL: </ripe/mail/archives/dns-wg/attachments/20051001/7161938f/attachment.sig>
- Previous message (by thread): [dns-wg] RIPE's MNAME recommendation
- Next message (by thread): [dns-wg] RIPE's MNAME recommendation
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ dns-wg Archives ]