Hi,
I have 'use-caps-for-id' set to 'yes' in my private local Unbound DNS
server for about 2 years now. I noticed about 4 days ago that all
domains that are hosted on domaincontrol.com. DNS servers (GoDaddy)
returned a SRVFAIL.
Further investigation revealed that the DNS servers now always send back
the domain name in the answer as lowercase, no matter what the casing in
the request was:
Example:
dig WiMp.com @ns03.domaincontrol.com .
; <<>> DiG 9.7.3 <<>> WiMp.com @ns03.domaincontrol.com .
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 5762
;; flags: qr aa; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 0
;; QUESTION SECTION:
;wimp.com. IN A
;; ANSWER SECTION:
wimp.com. 3600 IN A 208.43.68.142
;; AUTHORITY SECTION:
wimp.com. 3600 IN NS ns03.domaincontrol.com.
wimp.com. 3600 IN NS ns04.domaincontrol.com.
;; Query time: 105 msec
;; SERVER: 216.69.185.2#53(216.69.185.2)
;; WHEN: Sun Jun 12 12:19:52 2011
;; MSG SIZE rcvd: 94
Because of the huge number of domains affected, that makes
'use-caps-for-id' almost useless.
Does anyone know what new DNS server software is used at GoDaddy? Anyone
seeing the same issue?
-- Carsten
Jaap
June 12, 2011, 11:14am
2
;; AUTHORITY SECTION:
wimp.com. 3600 IN NS ns03.domaincontrol.com.
wimp.com. 3600 IN NS ns04.domaincontrol.com.
;; Query time: 105 msec
;; SERVER: 216.69.185.2#53(216.69.185.2)
;; WHEN: Sun Jun 12 12:19:52 2011
;; MSG SIZE rcvd: 94
Because of the huge number of domains affected, that makes
'use-caps-for-id' almost useless.
Does anyone know what new DNS server software is used at GoDaddy? Anyone
seeing the same issue?
fpdns thinks it is ATLAS:
fpdns ns03.domaincontrol.com
fingerprint (ns03.domaincontrol.com, 216.69.185.2): ATLAS
fpdns ns04.domaincontrol.com
fingerprint (ns04.domaincontrol.com, 208.109.255.2): ATLAS
jaap
I don't know what they are using, but it isn't ATLAS. For one thing, ATLAS doesn't have this problem...
* Jaap Akkerhuis:
Does anyone know what new DNS server software is used at GoDaddy? Anyone
seeing the same issue?
fpdns thinks it is ATLAS:
But ATLAS does not share this behavior (obviously 8-).
* Carsten Strotmann:
Does anyone know what new DNS server software is used at GoDaddy? Anyone
seeing the same issue?
It's broken in other ways, too. It seems to process queries as ASCII
internally.
excellent, time to update fpdns to recognise the difference using this test
Paul