Peter,
The DIG output is as follows:
; <<>> DiG 9.8.1 <<>> +norecurse streaming.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 3885
;; flags: qr aa; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;streaming.com. IN A
;; AUTHORITY SECTION:
streaming.com. 86400 IN SOA ns1.dnslink.com.
admin.dnslink.c
om. 2011091400 10800 3600 604800 3600
;; Query time: 811 msec
;; SERVER: 216.150.5.54#53(216.150.5.54)
;; WHEN: Mon Sep 26 11:04:28 2011
;; MSG SIZE rcvd: 96
The PDns log:
Mon 26 Sep 10:52:22 (4): Authoritative empty NO ERROR to 74.207.196.74
for 'streaming.com' (A), other types do exist
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
400000752 752 streaming.com NS ns1.dnslink.com 1800 NULL
1295376693
500000752 752 streaming.com NS ns2.dnslink.com 1800 NULL
1295376693
600000752 752 streaming.com SOA ns1.dnslink.com
admin.dnslink.com 2011091400
10800 3600 604800 3600 86400 NULL 1295376693
1000000003 0 dh.internettraffic.com A 208.87.32.69 1800
NULL 1295376693
I also updated my config to include "skip-cname=no" just in case.
Currently, the Linux servers are resolving this correctly, but you can hit
216.150.5.54 to see the issue.
---------------
> I've recently installed PDns Authoritative Server 2.9.15 on Windows
> without running the recursor. CNAMEs refuse to resolve though, even
> though they resolve fine on Linux using the same DB (although a later
> version of PDns).
> Furthermore, using nslookup against a domain on PDns/Linux resolving
> through a CNAME returns the exact same information as going against a
> domain on PDns/Windows, although the Windows one doesn't resolve.
>
> Has anyone seen this issue or know of any CNAME tricks that are
> necessary on PDns/Win?
I can't imagine CNAMEs behaving differently between the Windows and Linux
versions. Could you tell us your IP and (broken) name, or perhaps show us
some "dig +norecurse" output (not host, not nslookup) that demonstrates the
issue?
--
View this message in context:
http://old.nabble.com/PDNS-Win-2.9.15-not-resolving-CNAMEs-tp32503884p32503946.html
Sent from the PowerDNS mailing list archive at Nabble.com.
_______________________________________________
Pdns-users mailing list
Pdns-users@mailman.powerdns.com
http://mailman.powerdns.com/mailman/listinfo/pdns-users
