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] Fwd: [enum-wg] Tier-2 provisioning: NS vs CNAME/DNAME
- Previous message (by thread): [dns-wg] Fwd: [enum-wg] Tier-2 provisioning: NS vs CNAME/DNAME
- Next message (by thread): [dns-wg] Fwd: [enum-wg] Tier-2 provisioning: NS vs CNAME/DNAME
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Niall O'Reilly
Niall.oReilly at ucd.ie
Thu Jul 15 13:54:38 CEST 2004
On 15 Jul 2004, at 11:07, Jim Reid wrote: > And it will > make DNSSEC deployment (hah!) much harder because the parent can't > secure any delegations with DS records because there are no proper > delegations. So, we'd better make sure our trial doesn't take longer than six months ? 8-) Seriously, though, this is something I need to avoid losing sight of. Thanks. > DNAME is even worse because there are plenty of name > servers and resolvers out there that don't understand this RR. This also. thanks again. > It's > not impossible that some applications will get upset if they get > CNAME-like referrals to their lookups when they only expected to get > NAPTR RRs or conventional referrals. For instance think of someone who > writes a minimal ENUM-aware resolver as a Java applet for their mobile > phone. Nobody with significant market share would be involved in inflicting such a broken application on the unsuspecting customers, would they ? 8-) Best regards, Niall O'Reilly UCD Computing Services
- Previous message (by thread): [dns-wg] Fwd: [enum-wg] Tier-2 provisioning: NS vs CNAME/DNAME
- Next message (by thread): [dns-wg] Fwd: [enum-wg] Tier-2 provisioning: NS vs CNAME/DNAME
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ dns-wg Archives ]