I and customers are having random issues resolving .com.tw domains
this morning.  When I dig +trace, for the longest time f.dns.tw would
not give me an answer other than an SOA.  Now I am getting NS answers
again from f, but g.dns.tw is doing the same SOA only answer.  I can't
get a connection to e.dns.tw at all (though it seems like it's a local
negative cache issue b/c if I query the IP for e I get from the root
servers, I get answers back).

What's not working:

[todd@tlyons ~]$ dig com.tw @g.dns.tw

; <<>> DiG 9.7.3 <<>> com.tw @g.dns.tw
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 50495
;; flags: qr aa rd; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; WARNING: recursion requested but not available

;; QUESTION SECTION:
;com.tw.                                IN      A

;; AUTHORITY SECTION:
tw.                     900     IN      SOA     a.dns.tw. snw.twnic.net.tw. 
2001275018 3600 900 1296000 900


It should be returning:

[todd@tlyons ~]$ dig com.tw @f.dns.tw

; <<>> DiG 9.7.3 <<>> com.tw @f.dns.tw
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 18896
;; flags: qr rd; QUERY: 1, ANSWER: 0, AUTHORITY: 8, ADDITIONAL: 11
;; WARNING: recursion requested but not available

;; QUESTION SECTION:
;com.tw.                                IN      A

;; AUTHORITY SECTION:
com.tw.                 86400   IN      NS      a.twnic.net.tw.
com.tw.                 86400   IN      NS      b.twnic.net.tw.
com.tw.                 86400   IN      NS      c.twnic.net.tw.
com.tw.                 86400   IN      NS      d.twnic.net.tw.
com.tw.                 86400   IN      NS      e.twnic.net.tw.
com.tw.                 86400   IN      NS      f.twnic.net.tw.
com.tw.                 86400   IN      NS      g.twnic.net.tw.
com.tw.                 86400   IN      NS      ns2.cuhk.edu.hk.

;; ADDITIONAL SECTION:
a.twnic.net.tw.         86400   IN      A       192.83.166.9
b.twnic.net.tw.         86400   IN      A       203.73.24.203
c.twnic.net.tw.         86400   IN      A       168.95.192.10
d.twnic.net.tw.         86400   IN      A       210.17.9.229
e.twnic.net.tw.         86400   IN      A       211.20.231.12
f.twnic.net.tw.         86400   IN      A       220.229.225.196
g.twnic.net.tw.         86400   IN      A       203.119.3.2
a.twnic.net.tw.         86400   IN      AAAA    
2001:288:1:1006:21b:fcff:fe41:6c81
b.twnic.net.tw.         86400   IN      AAAA    2001:cd8:800::203
d.twnic.net.tw.         86400   IN      AAAA    2001:c50:ffff:1::229
e.twnic.net.tw.         86400   IN      AAAA    2001:b000:1e0:c000::12

;; Query time: 162 msec
;; SERVER: 163.28.1.10#53(163.28.1.10)
;; WHEN: Mon Sep 10 10:38:05 2012
;; MSG SIZE  rcvd: 399


Am I the only one?

...Todd
-- 
The total budget at all receivers for solving senders' problems is $0.
 If you want them to accept your mail and manage it the way you want,
send it the way the spec says to. --John Levine
_______________________________________________
dns-operations mailing list
[email protected]
https://lists.dns-oarc.net/mailman/listinfo/dns-operations
dns-jobs mailing list
https://lists.dns-oarc.net/mailman/listinfo/dns-jobs

Reply via email to