BIND having trouble resolving service.graphicly.com

Posted by Keith Burgoyne on Server Fault See other posts from Server Fault or by Keith Burgoyne
Published on 2010-05-19T14:12:24Z Indexed on 2010/05/19 14:21 UTC
Read the original article Hit count: 239

Filed under:
|
|
|

Since about two weeks ago, we haven't been able to resolve service.graphicly.com:

dig @192.168.0.12 service.graphicly.com

; <<>> DiG 9.3.4-P1 <<>> @192.168.0.12 service.graphicly.com
; (1 server found)
;; global options:  printcmd
;; connection timed out; no servers could be reached

Digging on the name servers listed for graphicly.com shows that service.graphicly.com is a CNAME to takecomicsadmin.cloudapp.net. Digging on cloudapp.net's name servers seems to fail:

dig @NS1.LIVEDNS.MSFT.NET takecomicsadmin.cloudapp.net

; <<>> DiG 9.3.4-P1 <<>> @NS1.LIVEDNS.MSFT.NET takecomicsadmin.cloudapp.net
; (1 server found)
;; global options:  printcmd
;; connection timed out; no servers could be reached

Somehow, my home ISP's name servers can resolve service.graphicly.com without issue. Has anyone else noticed this problem? Does anyone know what the cause of this problem could be? Thanks!

© Server Fault or respective owner

Related posts about bind

Related posts about resolve