3 ms·
I think this is because an A record query for www.kodefund.com returns multiple CNAME records, which is not compliant with the DNS specification: mrowe@veg
by bdash 14y ago
I think this is because an A record query for www.kodefund.com returns multiple CNAME records, which is not compliant with the DNS specification:
mrowe@vega:~$ dig A www.kodefund.com @a.dns.gandi.net
; <<>> DiG 9.8.1-P1 <<>> A www.kodefund.com @a.dns.gandi.net
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 53562
;; flags: qr aa rd; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 0
;; WARNING: recursion requested but not available
;; QUESTION SECTION:
;www.kodefund.com. IN A
;; ANSWER SECTION:
www.kodefund.com. 10800 IN CNAME intense-ocean-3642.herokuapp.com.
www.kodefund.com. 10800 IN CNAME mie-9107.herokussl.com.
;; Query time: 125 msec
;; SERVER: 173.246.97.2#53(173.246.97.2)
;; WHEN: Sun Jul 29 16:47:59 2012
;; MSG SIZE rcvd: 110
If I perform the same query via my system resolver rather than directly against the gandi.net DNS servers then I simply receive no result:
mrowe@vega:~$ dig A www.kodefund.com
; <<>> DiG 9.8.1-P1 <<>> A www.kodefund.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 36608
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0
;; QUESTION SECTION:
;www.kodefund.com. IN A
;; Query time: 1306 msec
;; SERVER: 192.168.1.254#53(192.168.1.254)
;; WHEN: Sun Jul 29 16:48:58 2012
;; MSG SIZE rcvd: 34
This is presumably because one of the intermediate resolver is being strict about the presence of multiple CNAMEs in the result.