On 03/10/2013 10:19 AM, Peter Eckel wrote: > Hi Austin, > > since your A record is fine and can be resolved, the issue is obviously not BIND related but lies somewhere in your network/firewall configuration. > > The last address that is visible in the tracereoute output from here is > >> 15 ip-208-109-113-174.ip.secureserver.net (208.109.113.174) 163.811 ms 163.984 ms 164.166 ms > so the issue must be somewhere between 208.109.113.174 and 173.201.189.43. Another IP (probably another customer of GoDaddy) in your /24 range is directly connected to 208.109.113.174 which makes it likely to be your next hop as well: > >> 15 ip-208-109-113-174.ip.secureserver.net (208.109.113.174) 178.314 ms 165.344 ms 165.293 ms >> 16 ip-173-201-189-1.ip.secureserver.net (173.201.189.1) 164.007 ms 163.767 ms 163.820 ms > > So probably the issue is in your router setup (packet filters and/or NAT, if applicable) or in the configuration of your own machine (iptables?). And along with this, you have DNSSEC enabled, so your firewall and router have to support EDNS. I am fighting that for my domain right now....