My custom domain fails to point to netlify nameservers

Hi, my custom domain is juanjesc.dev, in my cpanel in my domain provider, I have configured the CNAME of www.juanjesc.dev with the value of juanjesc.netlify.app, in addition, type A with the value of the IP correctly, and on the other hand in the DNS section I put the DNS of Netlify DNS1 dns1.p01.nsone.net, DNS2 dns2.p01.nsone.net … etc
However if we go to webs like https://hostadvice.com/tools/whois/ and we put juanjesc.dev the nameserver appears as juanjesc.netlify.app, instead of dns1.p01.nsone.net, etc.
My website is working fine, but I don’t want people to somehow know that my website points to juanjesc.netlify.app.
I ask this because I have friends who use Netlify with custom domain, and in the nameservers the netlify ones appear correctly.
thanks and best regards

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

Please take a look. Additionally, we have this Support Guide too that outlines all of our DNS resources. Lastly, 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.

Hi @hillary , I did a few days ago all the things in the post you gave me, and I still see that in the web I mentioned my nameserver is juanjesc.netlify.app and not the nameservers of netlify, so I think the problem is not solved, I don’t know what I’m doing wrong.

Maybe I need to add a new record in the Netlify dashboard in this capture?


A greeting.

I can see the correct nameservers:

dig NS +short juanjesc.dev
dns1.p01.nsone.net.
dns2.p01.nsone.net.
dns3.p01.nsone.net.
dns4.p01.nsone.net.

Hi @hrishikesh i see that in this page https://es.hostadvice.com/tools/whois/#juanjesc.dev
image

Hi @Juanjesc,

Thanks for the follow-up.

I am seeing on your site domain page that the SSL certificate has been successfully created. Going to both www.juanjesc.dev and juanjesc.dev resolves properly and I see that the site is served by Netlify.

Are you still having issues?

Hi @Melvin yes, I still don’t know why my website nameservers appear as juanjesc.netlify.app and not as Netlify servers (dns1.p01.nsone.net, dns2.p01.nsone.net, dns3.p01.nsone.net, dns4.p01.nsone.net.).
My website works without problems but I still see the nameservers like the above screenshot.

For example in this other application of mine https://apimovie.netlify.app/ if we place it on the web https://es.hostadvice.com/tools/whois/#https://apimovie.netlify.app/ You can see how the nameservers are correct, that does not happen with my personal web juanjesc.dev. It’s strange don’t you think?

image

Hi @Juanjesc,

I’m not sure what that tool is showing, or how it works. What I do know is, the tools that are more reliable and meant for this purpose are showing it correctly, for example dig:

dig NS +short juanjesc.dev
dns1.p01.nsone.net.
dns2.p01.nsone.net.
dns3.p01.nsone.net.
dns4.p01.nsone.net.

whois:

whois juanjesc.dev | grep "Name Server"
Name Server: dns1.p01.nsone.net
Name Server: dns2.p01.nsone.net
Name Server: dns3.p01.nsone.net
Name Server: dns4.p01.nsone.net

Hi @hrishikesh the problem is that although it works correctly, and the nameservers are well placed in my domain registry, people can access the CNAME that points to my domain, juanjesc.netlify.app, if people have access to this information they can easily access the web through 2 different URLs, which does not transmit me much security, in fact I have applications hosted on Netlify that if people have access to the CNAME and put the alternative url the application does not behave the same, so it is a problem.
It is a bit desperate because I asked support on the website I showed you, and they told me to contact Netlify support. I really appreciate your altruistic help but I’m still trying to see what’s going on. Thanks again

How is this insecure? By that logic, millions of website hosted on Netlify are insecure.

Would be happy to investigate that if supported by some evidence.

As mentioned before, we don’t know what that tool does, or how it works and scans for information. We cannot debug that. It’s on them to answer how they scan for information. We can answer according to tops that follow the standards which is dig and whois.

Lastly, if you really feel it’s insecure or causing problems, you can use Netlify Redirects to redirect everyone from the .netlify.app subdomain to your custom domain.