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 ]
ololocc at entratek.com
ololocc at entratek.com
Thu Dec 2 05:53:44 CET 2010
Moderator, Please kindly unsubscribe my email from the group list. Thank you. Cc_ololo at yahoo.com C. C. Ololo Principal Entratek Systems LLC 9319 LBJ Freeway, Dallas, TX 75243 USA -----Original Message----- From: Niall O'Reilly <Niall.oReilly at ucd.ie> Sender: dns-wg-admin at ripe.net Date: Wed, 01 Dec 2010 22:38:54 To: <dns-wg at ripe.net> Cc: <cet1 at cam.ac.uk> Subject: Re: [dns-wg] Replacing reverse zone delegations by DNAMEs On 01/12/10 20:27, Wilfried Woeber, UniVie/ACOnet wrote: > What I fail to see at 1st glance is where the RIR and the PDP comes in? Me too. I think that the approach which Chris is suggesting sits more in LIR territory than with the RIRs. It's a truly nifty idea, IMNSHO. My employer's LIR has found no objection to this approach. Neither has the tunnel broker for my domestic IPv6 connectivity. For example: dig -x 2001:770:13f:1:: dig -x 2001:770:98:200::35:1 Unfortunately, I didn't have the DNAME option whenever I had to set up reverse DNS for a /19 and a /20 in IPv4 as 48 /24's. Now, since this isn't broken, I'm not minded to fix it. /Niall
- 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 ]