[Pdns-users] Empty CNAME will result "server can't find: NXDOMAIN"
thomas at wapnet.nl
Sun May 6 08:21:59 UTC 2012
Google and amazon use CNAME's instead of A to point to their webservers.
Amazon and Google have the right to modify the IP of their CNAME so if you
use an A record to make http://example.com working and their modify the IP
then http://example.com isn't working anymore.
I'll get more and more requests from customers that asked me to create an
"apex cname" for there domains. Apex CNAME's in combination with Microsoft
DNS works correctly (even the RFC isn't support this officially). Apex
CNAME's in PowerDNS also works but the MX are broken after the change.
Is there any other way with PowerDNS to workaround this?
PS. I found the RFC about this issue: http://www.faqs.org/rfcs/rfc1912.html
2012/5/5 Peter van Dijk <peter.van.dijk at netherlabs.nl>
> Hello Thomas,
> On May 5, 2012, at 9:00 , Thomas Faddegon wrote:
> > Is there a way to fix this? In the past I found an article (RFC, sorry I
> can't find the source anymore) that officially empty CNAME's isn't allowed
> in DNS. But many companies works with empty CNAME's , even google and
> I have never seen Google and Amazon do anything with apex CNAMEs (what you
> call empty CNAMEs). Do you have any examples?
> Kind regards,
> Peter van Dijk
> Netherlabs Computer Consulting BV - http://www.netherlabs.nl/
> Pdns-users mailing list
> Pdns-users at mailman.powerdns.com
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Pdns-users