Re: Naked domain resolution with DNSSEC

This really should be handled by SRV or seperate MX like record.

Unfortunately http server operators, http browser developer and
http proxy developers misused/abused CNAME as it nearly provided
what was needed and never asked a appropriate record to say "this
site is hosted on this server" despite MX records existing to do
exactly this for SMTP.

Mark

In message <E66B38BB793BAF439EF374F3E7EBEE464B620A63@SINEX14MBXC415.southpacifi
c.corp.microsoft.com>, Kumar Ashutosh writes:
> Thanks Dave!
> 
> 
> -----Original Message-----
> From: Dave Lawrence [mailto:[email protected]] 
> Sent: Thursday, October 24, 2013 12:33 AM
> To: Kumar Ashutosh
> Cc: Jim Reid; Thirunadha Reddy; [email protected] Group; Sourav Sain
> Subject: RE: [dnsext] Naked domain resolution with DNSSEC
> 
> Kumar Ashutosh writes:
> > I agree on CNAME behaviour. My concern here is what option does the 
> > customer have in case he needs contoso.com and www.contoso.com both to 
> > be redirected to say contoso.dnsprovider.com
> 
> The customer in this case needs special handling by the authoritative server 
> to hand out address records at the apex instead.  Several DNS providers handl
> e this in their own software; for example, Akamai has a feature called "tople
> vel name redirection" to do it.  DNS Made Easy has what they call an "ANAME r
> ecord", described at http://www.dnsmadeeasy.com/services/aname-records/.  It 
> isn't really an IETF/IANA acknowledged DNS record, but rather just the way th
> ey describe how to configure it into their system.
> 
> This is a fundamental limitation of the DNS protocol.  To achieve the desired
>  effect you must use some mechanism that is outside the scope of current DNS 
> standards documents.
> 
> 
> _______________________________________________
> dnsext mailing list
> [email protected]
> https://www.ietf.org/mailman/listinfo/dnsext
-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: [email protected]
_______________________________________________
dnsext mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/dnsext