On Wed, May 29, 2013 at 12:23:15PM +0200, Pawel Panek wrote: > 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 >
You are claiming to be authoritative for root zone. Please do not claim root zone for yourself. Aki Tuomi
signature.asc
Description: Digital signature
_______________________________________________ Pdns-users mailing list [email protected] http://mailman.powerdns.com/mailman/listinfo/pdns-users
