Our DNS has seemed to stopped resolving sporadically around North America, and most of Europe, with what seems to mainly be cellular providers. We thought it was an issue just with Verizon after they confirmed an outage, but it’s seeming to be getting bigger and more random. We haven’t made any changes to our DNS recently, so it’s a bit odd.
Here is a pic of DNSChecker, note where it doesn’t resolve changes often throughout the day.
I find that DNSChecker can be a bit variable at times. I have checked a couple of others for your domain and I see no issues at all:
Are you seeing an issue with a real location you can troubleshoot directly or is it just DNSChecker?
Yes, I was in Los Angeles yesterday, in New Jersey today - and the server is reachable in and out over here on cellular, fine in LA. We also have customers in the east coast, and some midwest of the US who have been having issues since Thursday. But most if not all West Coast customers are fine. Any suggestions on digging deeper?
Could you get me some tests from an impacted connection/machine?
dig +trace example.com
dig @1.1.1.1 example.com
dig @8.8.8.8 example.com
curl example.com/cdn-cgi/trace
Replacing example.com with your hostname that you’re seeing issues with.
dig +trace api.yokepayments.com
; <<>> DiG 9.10.6 <<>> +trace api.yokepayments.com
;; global options: +cmd
. 499944 IN NS d.root-servers.net.
. 499944 IN NS e.root-servers.net.
. 499944 IN NS f.root-servers.net.
. 499944 IN NS g.root-servers.net.
. 499944 IN NS h.root-servers.net.
. 499944 IN NS a.root-servers.net.
. 499944 IN NS i.root-servers.net.
. 499944 IN NS j.root-servers.net.
. 499944 IN NS k.root-servers.net.
. 499944 IN NS l.root-servers.net.
. 499944 IN NS m.root-servers.net.
. 499944 IN NS b.root-servers.net.
. 499944 IN NS c.root-servers.net.
. 499944 IN RRSIG NS 8 0 518400 20210702050000 20210619040000 14631 . OzHVC1ExRveDSEBlDh388HRQrR/l5oGVW5Gg4v+rfqRtjMVbR45fD/+Z lc2G1igfQRMdKx1+fcnlitAg4m77fBt6UdMVPSY9H8I8JoJ8sZRSf2Vb s5CXW2NST9LN6BPL4qJiUp5ZFrJGu4AmEQYdjOeTCyHgidc5hYccO3rW MqGlgDXR9H18KlfXyE5WMp44GXrSUhFus/voEzMehVaoEfflBGmFCtFK OKTZEDoZSacY95BKbalQFJfwaC186bzwz4Q/mZw/y0ie4Yzgb9AU/ebx hhNcVrVaeTPNYO3SPOANbrJi3f57L++S/9l80cVYAxpbGn0po7ZwO707 KD1Slw==
;; Received 1086 bytes from 10.0.0.1#53(10.0.0.1) in 31 ms
com. 172800 IN NS a.gtld-servers.net.
com. 172800 IN NS b.gtld-servers.net.
com. 172800 IN NS c.gtld-servers.net.
com. 172800 IN NS d.gtld-servers.net.
com. 172800 IN NS e.gtld-servers.net.
com. 172800 IN NS f.gtld-servers.net.
com. 172800 IN NS g.gtld-servers.net.
com. 172800 IN NS h.gtld-servers.net.
com. 172800 IN NS i.gtld-servers.net.
com. 172800 IN NS j.gtld-servers.net.
com. 172800 IN NS k.gtld-servers.net.
com. 172800 IN NS l.gtld-servers.net.
com. 172800 IN NS m.gtld-servers.net.
com. 86400 IN DS 30909 8 2 E2D3C916F6DEEAC73294E8268FB5885044A833FC5459588F4A9184CF C41A5766
com. 86400 IN RRSIG DS 8 1 86400 20210702170000 20210619160000 14631 . a31jXBG7sjuO8nV3U3tGrvB8LkszzZaC/YaHcXMtp4F558JosZZNA9WX IEKwTNse7ycHQjDDnPiJtBipDbRbMUJilg5uCyJhaCvO45oBvTiYziv4 yCt7NKEuIgh4Rqnh8FDpaI0uPAM9nsReilfy3AR4A5RUpaB93+vkVhW5 2sDQk0RH0bsz1XtvpL1z4wgAo5S2Y3tWvV8/w7/eoDXA6/JEyCg/kRh/ UGqo2Qg+VZXgI2FLFc32x6+MhkLFb79OJqSD48oHhKKTBSZNnu/NCKQC Bft5eBkMQqrtIEbVHDdXujTctuh+mtzs3508g8FC3mXxROpXyXjsXLFw oSQA0g==
;; Received 1180 bytes from 199.9.14.201#53(b.root-servers.net) in 30 ms
yokepayments.com. 172800 IN NS emma.ns.cloudflare.com.
yokepayments.com. 172800 IN NS vin.ns.cloudflare.com.
CK0POJMG874LJREF7EFN8430QVIT8BSM.com. 86400 IN NSEC3 1 1 0 - CK0Q1GIN43N1ARRC9OSM6QPQR81H5M9A NS SOA RRSIG DNSKEY NSEC3PARAM
CK0POJMG874LJREF7EFN8430QVIT8BSM.com. 86400 IN RRSIG NSEC3 8 2 86400 20210625042355 20210618031355 54714 com. pne4vfraJMP9+efUAtN+Q4JMIrxqPp4ImPRXdwqsDLIkZaqoPFadrUzQ zBArW2c2prtzMBeRyT5yDWfMMGhbw8nZhM4xksB7Y/tQ2xEwFmRl2Rso Zti/nbvB71ccKyZKem0DaRlzDoyWLjLMm3LhSEQXQlEb3PtuaaS9c4Hy OYuHxgqrKziziH5Rl/ii95XTm7lwWaT6RGSdwIIesyFirA==
CCAEB5NQ21ROA7AA000B0368C2BIQNB9.com. 86400 IN NSEC3 1 1 0 - CCAF1IBU1P7AS6ELB1KSMPRJ3L3P4RBQ NS DS RRSIG
CCAEB5NQ21ROA7AA000B0368C2BIQNB9.com. 86400 IN RRSIG NSEC3 8 2 86400 20210625044043 20210618033043 54714 com. J0IzIrwZDv/kEbEPXxTgnTSG8SdnRv0OY3231P87BUNuckTpRrdud6OZ KqAPwXKjU7d9b9jvBnRwLoG0A2psF33Cq+m6IOw70E4ApECsctS/KQQ8 yol4tLvzexg3Bc7t8MbgAuRuHZ83hgAs+/TARwB3mWXsoHHOz1D5AWnQ dQd+67xWM+Pq4lcXG4AeeruF66CgBvrgfyt2qou78ucvQA==
;; Received 913 bytes from 192.5.6.30#53(a.gtld-servers.net) in 37 ms
api.yokepayments.com. 300 IN A 45.55.165.144
;; Received 65 bytes from 172.64.33.245#53(vin.ns.cloudflare.com) in 29 ms
dig @1.1.1.1 api.yokepayments.com
; <<>> DiG 9.10.6 <<>> @1.1.1.1 api.yokepayments.com
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 39496
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
;; QUESTION SECTION:
;api.yokepayments.com. IN A
;; ANSWER SECTION:
api.yokepayments.com. 300 IN A 45.55.165.144
;; Query time: 106 msec
;; SERVER: 1.1.1.1#53(1.1.1.1)
;; WHEN: Sat Jun 19 18:58:06 EDT 2021
;; MSG SIZE rcvd: 65
dig @8.8.8.8 api.yokepayments.com
; <<>> DiG 9.10.6 <<>> @8.8.8.8 api.yokepayments.com
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 51928
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 512
;; QUESTION SECTION:
;api.yokepayments.com. IN A
;; ANSWER SECTION:
api.yokepayments.com. 299 IN A 45.55.165.144
;; Query time: 42 msec
;; SERVER: 8.8.8.8#53(8.8.8.8)
;; WHEN: Sat Jun 19 18:58:35 EDT 2021
;; MSG SIZE rcvd: 65
curl api.yokepayments.com/cdn-cgi/trace
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<html><head>
<title>404 Not Found</title>
</head><body>
<h1>Not Found</h1>
<p>The requested URL /cdn-cgi/trace was not found on this server.</p>
<hr>
<address>Apache/2.4.7 (Ubuntu) Server at api.yokepayments.com Port 80</address>
</body></html>
Ok - so all of those DNS queries resolved just fine here. Can you find a location where it is not working to share with us?
Yeah seems to be working now, it is a bit in and out. I’ll run one of these when its out and report back.
One of my coworkers was traveling and didn’t have time to run through these, but I updated the DNS to have everything route through a proxy to see if that would help and it cleared up everyones issues. Super odd. Any idea why this could’ve caused such a random and massive outage?
This topic was automatically closed 15 days after the last reply. New replies are no longer allowed.