Thanks for removing that record. The A record was blocking the Netlify record from resolving correctly. I’ve just recreated that record on our end to solve that issue. However, your NS records are no longer pointing to Netlify:
% dig NS bruceevaristo.com +short
ns1.domain.com.
ns2.domain.com.
Can you ensure those nameservers are pointing to:
dns1.p07.nsone.net.
dns4.p07.nsone.net.
dns3.p07.nsone.net.
dns2.p07.nsone.net.
Yesterday when I checked, I saw the same thing as I mentioned 18 days ago here:
I see the incorrect ns*.domain.com nameservers when checking locally.
Checking via dnschecker.org I also see the incorrect ns*.domain.com records via ‘Cloudflare’.
The other ‘DNS Server’ checks (Google, Opendns etc), all show the correct Netlify NS records.
I am a bit confused here… I checked my DNS Panel, and I have deleted both “ns1.domain.com” and “ns2.domain.com”. I have checked each and every individual one in dnschecker.org. All of them work well for the most part (though, I have noticed that “_acme-challenge.bruceevaristo.com” is somewhat an ambiguous record seeing it works fine for most other nations’ servers but returns error on one).
I see what you mean now… would I have to wait for propagation to take effect until ns*.domain.com are deleted, or edit the DNS Panel again?
It confuses me too because I deleted the 4 dns*.p07.nsone.net records.
Why would you delete those, they’re what you were told to add here…
Hello, I fixed up my DNS Records, I removed the ones associated with domain.com and restored the ones associated with Netlify… I realize that it may not have been a DNS issue but it’s possible that it’s a SSL Certificate issue. I would like to thank you all for still reaching out and helping regardless.
