Hi, @MikeF. The first step is to create a new DNS zone for this custom domain here:
The instructions for this can be found here.
Important: When the DNS zone is created check the name servers at they might be different from the ones you configured at Hover.
There are several sets of DNS servers used by Netlify DNS (which are all name servers at NS1.com as our DNS service uses their IaaS DNS services).
The name server domain names look like this where the
p0# can be any number 1 through 6 (subject to change of course):
When a new DNS zone is created, it will get only one of the six sets of four DNS servers to use. This could be the
p01 name servers:
It could be the
p06 name servers:
Which one is assigned is determined when the zone is created and which is picked cannot be controlled.
I’m pointing this out because you’ve used the
p06 name servers and those many not end up being the correct name servers once the DNS zone is actually created.
To summarize what is happening, you have pointed your domain to four name servers that don’t know anything about your domain. The solution will be to create a DNS zone for this custom domain at Netlify.
Again, this might then require updating the name servers again at Hover because the ones in the Netlify DNS configuration might be
p04 instead of
Finally, once the DNS zone at Netlify is created and the name servers configured at Hover match the ones in the Netlify DNS zone, there is one more step. The last step is to delete and then add back the custom domains to the site’s custom domain settings here:
Why do you need to delete and re-add the custom domains there?
Because adding those custom domains will trigger the creations of NETLIFY (and possibly NETLIFYv6) type DNS records in the DNS zone to connect the custom domain to our CDN nodes. There is more about these NETLIFY/NETLIFYv6 DNS records here.
Please let us know if there are any questions or if this doesn’t resolve the issue.