Hello, I need help for the setup of my second website. My domain registrar is Google Domain, I am using Hostinger to configure my websites settings. Basically, I want to setup Cloudflare to handle static content for both my websites. I configured the settings for the first website, ‘atombytes’. I changed the nameserver on my Google Domain’s ‘DNS settings’ according to the instruction on Cloudflare. Now I am wanting to setup a second website (thefounderscafemy) via Hostinger’s Shared Hosting plan, I am led through the same instructions on Cloudflare to change the nameservers to ‘vida’ and ‘ernest’. However, this second website is under Hostinger’s Shared Hosting and will not appear on Google Domain’s DNS settings as it is under Hostinger. So, I changed the DNS at the DNS setting on hPanel and checked the DNS propagation status on DNS checker. However, it has been more than 72 hours and the propagation doesn’t seem to be completed as there are still ‘ns1’ and ‘ns2’ nameservers in the list. Are the methods I am using to setup my website wrong or is there another way to setup a website under a shared hosting plan? Furthermore, I can’t specifically change the nameserver on my Domain Registrar as the only domain is “Atombytes” and “thefounderscafemy” is done under Hostinger’s Shared Plan. Sorry for the lengthy summary as I am still new to DNS configuration
Hello there,
Is it thefounderscafemy.com?
Note the nameservers at the registrar (Google) have not been set to Cloudflare as required.
whois thefounderscafemy.com
Domain Name: THEFOUNDERSCAFEMY.COM
Registry Domain ID: 2700761610_DOMAIN_COM-VRSN
Registrar WHOIS Server: whois.google.com
Registrar URL: http://domains.google.com
Updated Date: 2022-06-02T04:52:38Z
Creation Date: 2022-06-02T04:34:53Z
Registry Expiry Date: 2023-06-02T04:34:53Z
Registrar: Google LLC
{snip}
Name Server: NS1.DNS-PARKING.COM
Name Server: NS2.DNS-PARKING.COM
yes, it is the second website that is under the atombytes website domain
I changed the DNS on my Google Domain interface, but the propagation is incomplete. I have waited more than 72 hours.
Here are the setting screenshots on my Google Domain and Hostinger hPanel. I changed the DNS to vida and ernest but the propagation is still incomplete after 72 hours.
@junhuichan123 Thanks for the update. At the moment, I see the site is loading. However, it does not look to me as if your propagation is complete. For, NS records seem to be updating. You’ll have to wait for couple of hours if the details entered were correct. Is it the correct order you’ve placed the NS records in Google? Still I see the above NS records as mentioned by @epic.network
This is the screenshot of the DNS nameserver on my Google Domain.
I updated the DNS nameservers last Friday, it has been more than 72 hour. Does it usually take more than 72 hours to propagate? Using DNS checker, I see that some are already updated to ‘vida’ and ‘ernest’ nameservers but not completely.
Well… I was in a bit confusion to ask you if that order was correct indeed? For eg:
ns1.something.com
Did you replace with vida.ns.cloudflare.com?
The image you’ve attached here, is it the same order mentioned by CF in the dashboard? I’m not pretty sure about this. However, this would clarify my thoughts as well.
There is no order to nameservers in whois. As long as the assigned pair of Cloudflare nameservers are the only ones listed in the whois, the domain solid validate.
The dns-parking nameservers still appear in the whois database. The DNSViz analysis reports an inconsistency between the NS records in the authoritative NS RRset and the delegation NS RRset.
This topic was automatically closed 15 days after the last reply. New replies are no longer allowed.