On Mon, 21 Jun 2010, Rok Potočnik wrote:
Anyway.. I found out what the problem is... they don't reply to dnssec
enabled requests...
$ dig +short @ns33.domaincontrol.com. replacementservices.com.
72.32.12.235
$ dig +short +dnssec @ns33.domaincontrol.com. replacementservices.com.
;; connection timed out; no servers could be reached
wanna boycott godaddy?
I don't see that issue:
[p...@bofh ~]$ dig +norecurse +dnssec -t ns replacementservices.com.
@ns33.domaincontrol.com.
; <<>> DiG 9.6.2-P2-RedHat-9.6.2-4.P2.fc12 <<>> +norecurse +dnssec -t ns
replacementservices.com. @ns33.domaincontrol.com.
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 35398
;; flags: qr aa; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 0
;; QUESTION SECTION:
;replacementservices.com. IN NS
;; ANSWER SECTION:
replacementservices.com. 3600 IN NS ns33.domaincontrol.com.
replacementservices.com. 3600 IN NS ns34.domaincontrol.com.
;; Query time: 29 msec
;; SERVER: 216.69.185.17#53(216.69.185.17)
;; WHEN: Mon Jun 21 11:58:31 2010
;; MSG SIZE rcvd: 93
Paul
_______________________________________________
bind-users mailing list
bind-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/bind-users
