It’s just one number difference, but I need to know if it’s affecting anythingˌ My guess is that it does not matter and that the p02 and p04 just refer to port 02 or port 04 and are probably recommended based on locationˌ
I’ve had trouble with vavoomhairavanˌcom [vavoomhairavanˌnetlifyˌapp] for monthsˌ The SSL/TLS certificate cannot be provisionedˌ When I try to Retry DNS Verification I get the error message DNS verification failed * vavoomhairavanˌcom doesn’t appear to be served by Netlifyˌ
I can’t figure out how to fix the SSL and I thought I’d start at the topˌ
When I go to https://appˌnetlifyˌcom/sites/vavoomhairavan/domain-management#https and click on “ Awaiting External DNS”, it says make sure that the domain provider’s name servers for vavoomhairavanˌcom are set to the following hostnames:
dns2ˌp02ˌnsoneˌnet <–NOTICE that one starts with dns2 instead of dns1ˌ
dns1ˌp02ˌnsoneˌnet
dns3ˌp02ˌnsoneˌnet
dns4ˌp02ˌnsoneˌnet
So first of all, which of these two sets of numbers do I trust? And secondly does the order in which they appear in the domain registrar’s DNS & Nameserver’s section actually matter? [domainˌcom in this instance for the registrarˌ]
I ask because for some reason the dns2ˌp02ˌnsoneˌnet nameserver appears first in the recommendation given to me in the netlify domain management popup when I click " Awaiting External DNS"ˌ
Note: Because I’m a new user and a lot of links aren’t permitted, and it sees dns hostnames as links, all the Full Stop characters [.] have been replaced with unicode+02CC - modifier letter low vertical line [ˌ]ˌ Trust me it drives me nuts alsoˌ Also I apologize in advance because I suspect that I broke the chatbot trying to troubleshoot thisˌ I thought perhaps the issue was some DNS misconfiguration that involved a lack of IPv6 support/AAAA name and the bot actually gave me the IPv6 addresses for Netlify to add to the AAAA name before telling me outright that Netlify does not have support at all for IPv6ˌ I’m not sure it was supposed to do that, because it is no longer responding to me with anything except errorsˌ I also noticed a lack of a type of CNAME in both my domainˌcom dns and in the nameservers available on vavoomhairavanˌnetlifyˌappˌ
But again, first thing’s first - I need to troubleshoot why vavoomhairavanˌcom does not appear to be served by Netlifyˌ
Let me try to address all of this before we do anything else.
Cool, I’m using the correct ones if you meant "Servers Shown on https://app.netlify.com/sites/vavoomhairavan/domain-management#https when I click “ Awaiting External DNS”. Otherwise I’m using the wrong ones and need to clarify by asking “shown where”
In my case, that IP address that wasn’t from Netlify was in the domain.com DNS records. It turns out the client had purchased some multi-service webmail and hosting package from web.com months ago, and somehow the DNS records at domain.com were altered to allow web.com to host the website, but without any content. I deleted those records, and the Let’s Encrypt security is working now.
Not sure what you’ll see when you dig, but as far as I can tell it is set up properly at this point. Sid Mann pointed out a few things to me over private email. The documentation at [Support Guide] DNS Quick Start - How to set up DNS helped, but didn’t prepare me for the possibility that a client might have authorized a 3rd party service to make some changes to the DNS settings at Domain.com.
If I were to try to troubleshoot this exact issue for another person, I’d tell them that when a client has access to the domain registrar, to check both the DNS Records and Nameservers at Domain.com and make sure there aren’t a bunch of 3rd party DNS records added.
Yes, those were the default domain.com servers. On Domain.com specifically, no changes can be made to the DNS Records for a website unless the nameservers point to domain.com `[ns1.domain.com and ns2.domain.com nameservers specifically.] So one guess is someone added those in order to add the web.com DNS records but not outright delete the four Netlify nameservers.
Another self-deprecating guess is that the web.com DNS records were there the entire time that I was first building the website and just didn’t notice - but it doesn’t look like the web.com records are that old. Either way, I think it’s repaired now.
Just blogging this for good documentation. Thank you for your help with the dig!
The Quick Start documentation you referenced is when using external DNS configuration which this domain is not using.
Do you see NETLIFY records on the Domains page of the Netlify dashboard?
Based on the output below I would say you don’t, and instead you see the A and CNAME records you created.
$ dig vavoomhairavan.com
vavoomhairavan.com. 15 IN A 75.2.60.5
$ dig www.vavoomhairavan.com
www.vavoomhairavan.com. 15 IN CNAME vavoomhairavan.netlify.app.
vavoomhairavan.netlify.app. 27 IN A 54.253.236.10
vavoomhairavan.netlify.app. 27 IN A 54.66.176.79
You don’t add these records when using Netlify DNS.
Awaiting External DNS”, it says make sure that the domain provider’s name servers for vavoomhairavanˌcom are set to the following hostnames: