I have the domain attack.capital setup using Netflix DNS (originally purchased from Porkbun, with Nameservers set for Netlify). The Domain doesn’t work sometimes, for myself and some friends in Korea even though I set it up 4 days ago. (Note: Website is made using React + Firebase)
I was researching old support questions and some recommended generating a new SSL Certificate. I have done it multiple times but the ‘Renew Certificate’ button never does a change for me. It still shows, the SSL updated day as Jan 23 at 1:08 PM.
Heya @luke & @SamO : Guys, I am new to the forums but saw that you guys were able to resolve a similar problem in other posts. I have tried the solutions presented, but it still doesn’t work for me.
Would really appreciate your help. Netlify newb here, deploying a React + Firebase Auth website
@hrishikesh: Hi! I don’t think it’s a propagation issue. I already deleted the DNS Cache on my mac using *sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder*
The issue is still happening. For some users, it appears as they visit different pages of the web app. My current bet is that it is due to some HTTPS/SSL issue
That checker reliably fails in some places; it’s not ours and we can’t fix it
I’ve set up a monitor to see if we can catch it happening from our side to see if we can get any more insights into what might be wrong; we can’t see any obvious misconfiguration.
Hi, @dragonwarrior. The DNS lookup works in most places. In the places where it is not working we would need additional information from that system. When testing locally, I always use dig with the +trace option.
This is what I see locally (which is a working DNS lookup):
$ dig +trace attack.capital
; <<>> DiG 9.10.6 <<>> +trace attack.capital
;; global options: +cmd
. 68786 IN NS a.root-servers.net.
. 68786 IN NS b.root-servers.net.
. 68786 IN NS c.root-servers.net.
. 68786 IN NS d.root-servers.net.
. 68786 IN NS e.root-servers.net.
. 68786 IN NS f.root-servers.net.
. 68786 IN NS g.root-servers.net.
. 68786 IN NS h.root-servers.net.
. 68786 IN NS i.root-servers.net.
. 68786 IN NS j.root-servers.net.
. 68786 IN NS k.root-servers.net.
. 68786 IN NS l.root-servers.net.
. 68786 IN NS m.root-servers.net.
. 68786 IN RRSIG NS 8 0 518400 20230212170000 20230130160000 951 . k0sWKQXQH9ki5TulYuN7D24yk1jNWf5CNiMF76nSxr7SKh0sZf4yzHAZ xIHaUD6013h2+529FYqdK+t33Hggfx1hJ8Dh8zzbLmHjRV7w+7wcamKW duwEtdy8KE3xemW075FmWQUkLQJOlC7d4CZFy5X5Bwi5D/s+qkpSAQu8 ruGqE7AaUq2Ou+n+lr9mM5bLS5rch+pKzhnqjjr1ORlsxFO1lvZh+djf BDxzO6RPZUichCdtnbKP4+hLf4C1Jt0M8aUgrdRXPxNhJ1K/uuFu6Doa 66qXY6k6ShY61EM0lsH89ocMjCx9Bi/x+WW4kuKLF2wc7Dzdgn6CjCFu RQqiRg==
;; Received 525 bytes from 8.8.4.4#53(8.8.4.4) in 26 ms
capital. 172800 IN NS v0n0.nic.capital.
capital. 172800 IN NS v0n1.nic.capital.
capital. 172800 IN NS v0n2.nic.capital.
capital. 172800 IN NS v0n3.nic.capital.
capital. 172800 IN NS v2n0.nic.capital.
capital. 172800 IN NS v2n1.nic.capital.
capital. 86400 IN DS 9469 8 2 E4832B3A24031E377C4D82A22C87EFADEE41FAC941FD1FAC7A2AB5EC C9B821A0
capital. 86400 IN RRSIG DS 8 1 86400 20230212210000 20230130200000 951 . ULD43xEAeP5FevJ3NUqjOvrXtm2yG1WKvdfatHJOJYvLMXZMLoBcfyuy fJX1VnOkRdyd7fTdYXXesBz1b4/PbYjwu7dQWWWu4WZvExOglB2+lSPK QPnTjZHQMImu78GNHMMdU8mCYY4n8+gwdX4l+AaPiBGRiu8sxGSPCxnS hX1M2cag27psmSc45BPqSv6ULXb4cKJBfcJlWbGYI4DE4HOVICFi6r0g 6Ne7Ke8tONPZNns9+z7pQ3QlA7ve5O2Uslb2Qyk4cMpxdxv9E7IEGlYz 78WpVDpK7+zH72UUAYGsolvkGHwBYKGvWFEqTp8y70iCPjUksS+mfvKY kv/7gw==
;; Received 760 bytes from 192.203.230.10#53(e.root-servers.net) in 21 ms
attack.capital. 3600 IN NS dns4.p01.nsone.net.
attack.capital. 3600 IN NS dns2.p01.nsone.net.
attack.capital. 3600 IN NS dns3.p01.nsone.net.
attack.capital. 3600 IN NS dns1.p01.nsone.net.
6rst29ic8chgi3b1r62ppupeme49pslh.capital. 3600 IN NSEC3 1 1 10 332539EE7F95C32A 6SBGR0CSUFR6U3QL0S378A5UUE5J7LV9 NS SOA RRSIG DNSKEY NSEC3PARAM
6rst29ic8chgi3b1r62ppupeme49pslh.capital. 3600 IN RRSIG NSEC3 8 2 3600 20230221004522 20230130234522 24513 capital. V5A+rdI7ssktWraIzeT5LrzPS+5j9DcJCYYs5PZQoEvJv6j2WErZDzrh Yt/nZqIMvJsUcpPb32p5I2TnGVU0rCieK8+pfh9hs7xNe+JNvotFYGm4 GERoqfThs17N+zGBA1jtxqlL5rcj5iWZFwW7TMqdOhFicFUj8TcxnpgI FYk=
pkg5opi9bn3e6h75e57kdf9i7fkqk5tl.capital. 3600 IN NSEC3 1 1 10 332539EE7F95C32A PLAF4UFIU2E7TAGT33BLEBVIQN47SKMF NS DS RRSIG
pkg5opi9bn3e6h75e57kdf9i7fkqk5tl.capital. 3600 IN RRSIG NSEC3 8 2 3600 20230215152737 20230125142737 24513 capital. C3y91Ihii59pnvoNAfoFCIX+galxXEPhZiZUthLKAQzFEeKWwAYhiHjv c3z7DI6ABBukUr1afcQQhInyQSfDFuq+qEpp0ZPzMrtwlYQDmVP+J5Hi SOE7Ntk50PELO+7LThy5qByBWimRD2cdpEnzZCeMe5/SkxtzlhBwOYbF UhU=
;; Received 641 bytes from 161.232.14.10#53(v0n3.nic.capital) in 26 ms
attack.capital. 20 IN A 34.168.247.115
attack.capital. 20 IN A 35.199.181.187
;; Received 75 bytes from 198.51.44.65#53(dns3.p01.nsone.net) in 20 ms
I would need the same output from one of the non-working systems to troubleshoot this. However, the site you linked to doesn’t offer a way to get this information. Without that information, I would only be guessing as to the nature of the issue.
If you can gather that information from the non-working locations and post it here, that should reveal the root cause.
