CNAME, DNAME, NS, A

[Patrik Fältström]

On 31 jan 2008, at 21.53, John C Klensin wrote:

>> How much of a load does DNAME place on the various components
>> in this picture? What about CNAME? If IDNs start getting used
>> heavily, will CNAME and DNAME scale well? Does the
>> pre-resolution library scale better? Should any of this have
>> an effect on the design of IDNAbis?
>
> You should probably have a look at
> draft-ietf-dnsext-rfc2672bis-dname-08.txt because the answer to
> the first question depends critically on whether the client
> resolver making a query fully supports DNAME

FWIW: I have not seen any resolvers understanding DNSSEC that do NOT  
understand DNAME. It is also laid out in the draft-ietf-dnsext- 
rfc2672bis-dname document why a resolver must understand DNAME if  
DNSSEC is understood. Given the requirement for DNSSEC grows fast at  
the moment, also support (and because of that ability to use DNAME in  
an effective way without CNAME) for DNAME grows.

That said, there are as pointed out issues at the apex, and draft-ietf- 
dnsext-rfc2672bis-dname is a good read on the issues, including for  
example target of MX etc.

    Patrik

-------------- next part --------------
A non-text attachment was scrubbed...
Name: PGP.sig
Type: application/pgp-signature
Size: 186 bytes
Desc: This is a digitally signed message part
Url : http://www.alvestrand.no/pipermail/idna-update/attachments/20080201/178edc63/PGP.bin