Re: Naked domain resolution with DNSSEC

Thanks John!
Dave has pointed about certain 'special' records like ANAME. I think Amazon route53 also has similar 'alias' records.
It would be great if the working group could drive a standardized handling of this scenario.

Thanks
Ashu

-----Original Message-----
From: John Levine [mailto:[email protected]] 
Sent: Thursday, October 24, 2013 1:25 AM
To: [email protected]
Cc: Kumar Ashutosh
Subject: Re: [dnsext] Naked domain resolution with DNSSEC

>How will such a customer ensure that both www.contoso.com and 
>contoso.com get pointed to contoso.provider.com."

I've done it by provisioning.  My DNS management software has a hack that says that one name has the same A/AAAA as some other name.  Every few hours a daemon runs down the list, and if the target address has changed, it updates the local name.

This is a hack, but it's the least bad one I know in this situation.

Note that this also makes it a lot easier handle the fairly common situation that the web server is hosted one place and the mail is hosted in another, and the web host has no way to install MX records that point anywhere other than itself.

R's,
John
_______________________________________________
dnsext mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/dnsext