[Pdns-users] PDNS/Win 2.9.15 not resolving CNAMEs

domainholdings scott at domainholdings.com
Mon Sep 26 16:05:24 UTC 2011

Interesting... this is the same DB as on Linux (we've always had this
mistake), so it does seem to point different behavior over the two
platforms, or that this mistake is forgiven in later Pdns versions.

So aside from removing the NS and SOA records for our CNAMEs, we can only
use CNAMEs for subdomains?

Hello Scott,

On Sep 26, 2011, at 5:10 PM, domainholdings wrote:

> The actual records (select * from records where Name in 
> ('dh.internettraffic.com', 'streaming.com')):
> id	domain_id	name	type	content	ttl	prio	change_date
> 100000752	752	streaming.com	CNAME	dh.internettraffic.com	1800	NULL
> 1295376693

This line is invalid. A CNAME record must always live alone on a name, while
yours has brothers of type NS and SOA. As the SOA is required, the basic
rule is that a domain itself cannot be a CNAME.

> Currently, the Linux servers are resolving this correctly, but you can 
> hit
> to see the issue.

They may be doing what you were expecting/hoping, but when you put CNAME and
other in a database together, there is no "correctly". This domain is broken
on both of your platforms until you remove the streaming.com CNAME.

Kind regards,
Peter van Dijk

View this message in context: http://old.nabble.com/PDNS-Win-2.9.15-not-resolving-CNAMEs-tp32503884p32503952.html
Sent from the PowerDNS mailing list archive at Nabble.com.

More information about the Pdns-users mailing list