[Pdns-users] NXDOMAIN on CNAME and UPC

[Pawel Panek]

Hi Peter,

Thank you for reply.

> First and foremost: if this happens for a domain, the authoritative servers ARE misconfigured. However, Recursor (3.3) is also wrong in accepting the bogus data. Recursor 3.5 and 3.5.1 operate correctly and will give useful answers in these situations.

I'm asking authoritative server and get this:

dig cdn.example.com @1xx.1xx.1xx.1xx

; <<>> DiG 9.8.2rc1-RedHat-9.8.2-0.17.rc1.el6.3 <<>> cdn.example.com
@1xx.1xx.1xx.1xx
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 46370
;; flags: qr aa rd; QUERY: 1, ANSWER: 1, AUTHORITY: 1, ADDITIONAL: 0
;; WARNING: recursion requested but not available

;; QUESTION SECTION:
;cdn.example.com.            IN      A

;; ANSWER SECTION:
cdn.example.com.     3600    IN      CNAME   randomstr.cloudfront.net.

;; AUTHORITY SECTION:
.                       3600    IN      SOA     ns1.mydnsserver.net.
noc.mydnsserver.net. 2012042301 10800 3600 604800 300

;; Query time: 6 msec
;; SERVER: 1xx.1xx.1xx.1xx#53(1xx.1xx.1xx.1xx)
;; WHEN: Wed May 29 06:14:19 2013
;; MSG SIZE  rcvd: 143

what's wrong here? I need some hint how should I correct PowerDNS
config to fix configuration error (if any).

>
> We have reached out to UPC about this, and they have responded that they are aware of the issue, and are working to update their servers, which has already happened partially. Until this is done everywhere which will still take a while and in order to avoid running into the same issue at other providers they (and us!) recommend to avoid this issue by fixing the underlying configuration issue on the authoritative servers.
>

Thank you for info.

Regards,
Pawel Panek

> Kind regards,
> --
> Peter van Dijk
> Netherlabs Computer Consulting BV - http://www.netherlabs.nl/
>
>
> _______________________________________________
> Pdns-users mailing list
> Pdns-users at mailman.powerdns.com
> http://mailman.powerdns.com/mailman/listinfo/pdns-users