On Mon 2016-Apr-04 17:41:32 -0400, Chuck Anderson via Outages <outages@outages.org> wrote:
I can't resolve DNS from genhost.in hosted DNS. Queries are REFUSED by one nameserver, connection timed out for the other:
dig +noall +answer +authority +additional +norec @b2.in.afilias-nst.org. ns1.genhost.in. ns genhost.in. 86400 IN NS ns1.genhost.in. genhost.in. 86400 IN NS ns2.genhost.in. ns1.genhost.in. 86400 IN A 167.114.208.229 ns2.genhost.in. 86400 IN A 192.95.37.62
dig +norec @167.114.208.229 ns1.genhost.in. ns ; <<>> DiG 9.10.3-P4-RedHat-9.10.3-12.P4.fc23 <<>> +norec @167.114.208.229 ns1.genhost.in. ns ; (1 server found) ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: REFUSED, id: 52683 ;; flags: qr; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 4096 ;; QUESTION SECTION: ;ns1.genhost.in. IN NS
;; Query time: 29 msec ;; SERVER: 167.114.208.229#53(167.114.208.229) ;; WHEN: Mon Apr 04 17:38:11 EDT 2016 ;; MSG SIZE rcvd: 43
dig +norec @195.95.37.62 ns1.genhost.in. ns ; <<>> DiG 9.10.3-P4-RedHat-9.10.3-12.P4.fc23 <<>> +norec @195.95.37.62 ns1.genhost.in. ns ; (1 server found) ;; global options: +cmd ;; connection timed out; no servers could be reached
Anyone else seeing the same issue?
Yes; same symptoms. Coming from Canada; path to 192.95.37.62 is via direct peering with 16276 at The SIX. We had previously pref'd our path to 167.114.0.0/16 to head through our own backbone and out in Toronto because of performance issues reaching something in that block from out this side if doing hot potato via the SIX. -- Hugo