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-wg] Replacing reverse zone delegations by DNAMEs
- Previous message (by thread): [dns-wg] Replacing reverse zone delegations by DNAMEs
- Next message (by thread): [dns-wg] Replacing reverse zone delegations by DNAMEs
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Tony Finch
dot at dotat.at
Thu Dec 2 15:41:38 CET 2010
On Thu, 2 Dec 2010, Florian Weimer wrote: > > It should still work. In the parent, you'd have: > > 169.129.in-addr.arpa. IN NS ns1.example.net. > 169.129.in-addr.arpa. IN NS ns2.example.net. > > And ns*.example.net. would serve > > 169.129.in-addr.arpa. IN DNAME reverse.example.com. The point is to put the DNAME in the parent zone to save the effort of maintaining the delegated zone, i.e. all the stuff you have to do even if the zone is nearly empty. Tony. -- f.anthony.n.finch <dot at dotat.at> http://dotat.at/ HUMBER THAMES DOVER WIGHT PORTLAND: NORTH BACKING WEST OR NORTHWEST, 5 TO 7, DECREASING 4 OR 5, OCCASIONALLY 6 LATER IN HUMBER AND THAMES. MODERATE OR ROUGH. RAIN THEN FAIR. GOOD.
- Previous message (by thread): [dns-wg] Replacing reverse zone delegations by DNAMEs
- Next message (by thread): [dns-wg] Replacing reverse zone delegations by DNAMEs
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ dns-wg Archives ]