On 23.06.2010 / 17:51:24 +1000, Mark Andrews wrote: > > In message <aanlktinjqorplnyqj5tso2tdwlt_ropzdmrymoiph...@mail.gmail.com>, > Piff > writes: > > Mark, > > > > more than once you have blamed firewal but I have tested without > > firewall and NSxx.DOMAINCONTROL.COM do not answer to "dig +dnssec". > > Wrong. The nameserver DO answer these queries. > > # dig +dnssec @ns33.domaincontrol.com. replacementservices.com. > > ; <<>> DiG 9.3.6-P1 <<>> +dnssec @ns33.domaincontrol.com. > replacementservices.com. > ; (1 server found) > ;; global options: printcmd > ;; Got answer: > ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 41760 > ;; flags: qr aa; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 0 > > ;; QUESTION SECTION: > ;replacementservices.com. IN A > > ;; ANSWER SECTION: > replacementservices.com. 3600 IN A 72.32.12.235 > > ;; AUTHORITY SECTION: > replacementservices.com. 3600 IN NS ns33.domaincontrol.com. > replacementservices.com. 3600 IN NS ns34.domaincontrol.com. >
This dig query timeouts on my side, checked from 3 different IPs from 3 different AS (autonomous systems). _______________________________________________ bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
