Netlify DNS Issues with 3rd Party Domain, Duplicate A Records

[SeintDev]

We recently switched to a new domain name. Both the old domain and the new domain are hosted by a 3rd party registrar, but we use Netlify’s DNS. The new domain is properly pointed to Netlify’s DNS servers. The website seems to be working alright for the most part…

However, under Domain Settings → SSL/TLS I’m noticing the following message: www.seintgallery.com doesn't appear to be served by Netlify

When I query the DNS using dig I’m noticing that there are two A records associated with the new domain seintgallery.com I’m pretty sure this is part of the issue. When I click on Netlify DNS and look at the settings for seintgallery.com everything appears to be correct. However, it doesn’t make sense that there would also be the same duplicate DNS settings for www.seintofficial.com

Also, when I use the DNS Checker, it shows that DNS has not fully propagated, even though it’s been over 48 hours:

DNS Propagation Checker - Global DNS Checker Tool

Thanks, and I appreciate any help regarding this matter.

[perry]

Hi there! We’ve created this DNS Quickstart guide for this very purpose - to get you up and running as quickly as possible.

[Support Guide] DNS Quick Start - How to set up DNS

Last reviewed: August 2023 Note: All options discussed in this guide assume you have already added your custom domain to your Netlify site. Hi there! Need to get your site up and running with DNS? Start here with either Newly purchased domain or Existing domain that you’ve already used. Newly purchased domain If you have a brand new domain purchased from a registrar such as Namecheap or GoDaddy, and you want to quickly get your DNS set up, you have two options: External DNS - Create these …

Please take a look - we have many resources listed at the bottom, too. And, there are tons of DNS questions you can access through our search! If your problem still persists after reading through all relevant guides, please post again and we will troubleshoot with you.

[SeintDev]

Thank you for your help. I’ve looked through most of the articles you’ve mentioned, at the bottom of the page. The main issue in this case is: duplicate A records exist for both seintgallery.com and www.seintgallery.com

There should only be one A record for each domain/subdomain. I don’t think there should be Netlify DNS settings for both seintgallery.com and www.seintgallery.com - only for the primary domain - www.seintgallery.com

Basically, I have two sets of identical A records. How do I remove the Netlify DNS settings from everything except the primary domain? I need to get rid of the duplicate DNS records that are not tied to the primary domain. Thanks again.

[luke]

Hi, @SeintDev. This actually is not true with our service:

There should only be one A record for each domain/subdomain.

We always return two IP addresses for CDN nodes closest to the source IP address for the DNS lookup.

When I checked the SSL certificate for this site, the error message was for a previous renewal attempt. It is not a current error. It is the last error which occurred (if any) for troubleshooting purposes.

I tested a renewal and it was successful.

To summarize, the duplicate A records are both intentional and working correctly. The SSL certificate renewal also worked correctly the first time I tested.

Regarding delays in DNS changes those are controlled by the time to live (TTL) values of the previous (not the current) DNS records:

[Support Guide] Why do DNS / SSL changes take up to 48 hours to propagate? (TTL)

Last reviewed by Netlify Support on August 2023 How do time to live (TTL) values affect changes to DNS records? People often ask why the changes to DNS (Domain Name System) records are not taking effect. The answer to this often involves a core mechanism of how DNS functions - the “time to live” (TTL) values for the DNS records themselves. This topic is here to answer those questions! ! If you’d prefer a TL:DR; in the form of a video, check this out: [WHAT IS PROPAGATION? - Netl…

If there are other questions or concerns, please let us know.

[SeintDev]

Thanks for the clarification @luke. I didn’t realize that was how Netlify’s CDN was supposed to work. The DNS propagation looks better today. And yes, I do realize it takes time due to TTLs. I guess I should’ve tried to renew the SSL cert again, just to see if it would work Thanks again for your prompt response!