I have been using dnsmadeeasy.com since their last outage 2 years ago and have not looked back.
On Thu, Sep 4, 2014 at 12:18 PM, Cary Wiedemann via Outages < [email protected]> wrote: > More than just their 'pdns' premium DNS servers are down today. > NS31.DOMAINCONTROL.COM and NS32.DOMAINCONTROL.COM ping but don't respond > to A or MX requests regardless of where I source from: > > (From Savvis) > cary@brn-web-ftp:~$ dig +trace a sunriseseniorliving.com +short > NS m.root-servers.net. from server 204.70.127.127 in 2 ms. > NS c.root-servers.net. from server 204.70.127.127 in 2 ms. > NS g.root-servers.net. from server 204.70.127.127 in 2 ms. > NS f.root-servers.net. from server 204.70.127.127 in 2 ms. > NS j.root-servers.net. from server 204.70.127.127 in 2 ms. > NS e.root-servers.net. from server 204.70.127.127 in 2 ms. > NS b.root-servers.net. from server 204.70.127.127 in 2 ms. > NS k.root-servers.net. from server 204.70.127.127 in 2 ms. > NS d.root-servers.net. from server 204.70.127.127 in 2 ms. > NS a.root-servers.net. from server 204.70.127.127 in 2 ms. > NS l.root-servers.net. from server 204.70.127.127 in 2 ms. > NS i.root-servers.net. from server 204.70.127.127 in 2 ms. > NS h.root-servers.net. from server 204.70.127.127 in 2 ms. > ;; connection timed out; no servers could be reached > > (AT&T) > root@CaryBox:~# host -t mx sunriseseniorliving.com NS32.DOMAINCONTROL.COM > ;; connection timed out; no servers could be reached > > As I typed this email 'NS31.DOMAINCONTROL.COM' came back up, but NS32 is > still down. > > Their phone tech support says they can't find a problem. And their status > page says "No Significant Issues": > http://support.godaddy.com/system-alerts/ > > Totally inexcusable. > > - Cary > > > > On Wed, Sep 3, 2014 at 11:53 AM, Rubens Kuhl via Outages < > [email protected]> wrote: > >> >> >> >> On Wed, Sep 3, 2014 at 12:12 PM, Mike Phipps via Outages < >> [email protected]> wrote: >> >>> A few of our client domains just suddenly started failing to resolve. As >>> it turns out, those domains are ones whose name service is handled via >>> GoDaddy. There's a thread on Reddit that suggests that this is pretty >>> widespread, but the exact scope isn't known yet, and GD has not announced >>> the issue. >>> >>> >>> http://www.reddit.com/r/sysadmin/comments/2fczdc/godaddy_premium_dns_down/ >>> >>> >>> >>> Dig queries to domains that are on PDNS01 or PDNS02 fail. There are >>> probably others. >>> >> >> >> We are seeing queries to PDNS02 being refused depending on anycast >> location, but we can't pinpoint them exactly as hostname.bind queries are >> not answered. Some locations answer fine, some not, depending not only on >> country but also on transit provider. >> >> Rubens >> >> >> _______________________________________________ >> Outages mailing list >> [email protected] >> https://puck.nether.net/mailman/listinfo/outages >> >> > > _______________________________________________ > Outages mailing list > [email protected] > https://puck.nether.net/mailman/listinfo/outages > >
_______________________________________________ Outages mailing list [email protected] https://puck.nether.net/mailman/listinfo/outages
