tales.so
Name servers not updating.
Spoke to the registrar, and they have not been able to help directly.
The nameservers were updated on the registrar, nearly 10 days ago, but they haven’t propagated across yet – and causes website downtime 5-10% of times.
Nameservers
dig ns tales.so
Looks like domain is using below Cloudflare nameservers:
Name Server: stanley.ns.cloudflare.com
Name Server: ingrid.ns.cloudflare.com
Might be it needed more time (24-72h) to propagate:
Looks like you’re using Vercel 
, since returned IP address isn’t in the Cloudflare’s IP range, therefrom since the Website is working fine over HTTPS, I’d suggest you to prox 
your DNS records for security & performance from Cloudflare.
I am seeing inconsistent results when I query the nameservers for .so, here are two requests made within a few seconds of each other:
% dig soa tales.so @d.nic.so
;; AUTHORITY SECTION:
tales.so. 1200 IN NS dns1.registrar-servers.com.
tales.so. 1200 IN NS dns2.registrar-servers.com.
;; Query time: 190 msec
;; SERVER: 2001:43f8:120::54#53(d.nic.so) (UDP)
;; WHEN: Thu Nov 07 01:02:47 GMT 2024
;; MSG SIZE rcvd: 96
% dig soa tales.so @d.nic.so
;; AUTHORITY SECTION:
tales.so. 1200 IN NS ingrid.ns.cloudflare.com.
tales.so. 1200 IN NS stanley.ns.cloudflare.com.
;; Query time: 187 msec
;; SERVER: 2001:43f8:120::54#53(d.nic.so) (UDP)
;; WHEN: Thu Nov 07 01:02:49 GMT 2024
;; MSG SIZE rcvd: 97
The nameservers in Whois are also changing far too often. Either somebody is changing these all the time, or the Registry/Registrar are having an issue.
# whois.nic.so
Domain Name: tales.so
Updated Date: 2024-11-07T00:55:40Z
Name Server: dns1.registrar-servers.com
Name Server: dns2.registrar-servers.com
DNSSEC: unsigned
>>> Last update of WHOIS database: 2024-11-07T00:57:04.175Z <<<
# whois.nic.so
Domain Name: tales.so
Updated Date: 2024-11-07T00:57:47Z
Name Server: stanley.ns.cloudflare.com
Name Server: ingrid.ns.cloudflare.com
DNSSEC: unsigned
>>> Last update of WHOIS database: 2024-11-07T01:05:28.532Z <<<
I would query with your Registrar why the NS set and the whois data is changing at the times indicated above.
I agree, the registrar (Namecheap in my case) somehow has some misconfiguration that prevented the DNS propagation correctly.
However, I did the following –
This seems to work for now – the classic hard reboot. However, will keep checking for the next 24-48hrs, since the issue is more intermittent. I’m checking the DNS configurations at – DNS Checker - DNS Check Propagation Tool for the main website at https://www.tales.so.
Any better alternative than Vercel - Self hosting via Digital Ocean / Cloudflare?
I’m currently using Namecheap, but is there an alternative hosting provider that supports .so domains, which doesn’t have such an issue?
tales.so
Subdomain not resolving, DNS propagation shows the DNS to IP mapping is complete.
My domain cdn.tales.so is pointing to the IP address: 34.111.206.27 at the moment. However, when I try to open it in the browser, it doesn’t work “sometimes” – mostly in Safari.
DNS records
Try opening the url - https://cdn.tales.so/books/the-guncle/cover_image.jpg in Safari – it might not open (1/10 times)
Another thing – I run a simple wget and that also doesn’t seem to resolve correctly -
–2024-11-06 18:09:45-- https://cdn.tales.so/books/the-guncle/cover_image.jpg
Resolving cdn.tales.so (cdn.tales.so)… failed: nodename nor servname provided, or not known.
wget: unable to resolve host address ‘cdn.tales.so’
Thank you for asking and feedback.
I’ve merged your topics here to the same in the meantime.
I do self-host, but that requires a bit of knowledge and maintenance if you’re doing it yourself without hiring anyone to do it for you.
It’s working for me in Firefox:
Might be temporary due to the Web browser cache or your local ISP cache due to the DNS propagation process.
@arpit I’m not sure your precise use case. How about Cloudflare pages? You may have a glance if it meets your expectations: Cloudflare Pages documentation
Interesting - but I updated the cdn.tales.so nearly 10 days ago as well. Would you expect to see issues like –
–2024-11-06 18:09:45-- https://cdn.tales.so/books/the-guncle/cover_image.jpg
Resolving cdn.tales.so (cdn.tales.so)… failed: nodename nor servname provided, or not known.
wget: unable to resolve host address ‘cdn.tales.so’
?
Again - these issues are pretty intermittent – hence the confusion.
I’ll check it out for sure! thanks for sharing @neiljay
Here’s the current status –
Doesn’t seem like the propagation is working as expected. Is there a way to get the change logs of the name servers that are sent out from the registrar?
I’d suggest to contact domain registrar and double-check your domain nameservers using below articles.
It looks to me you’ve might added NS type of the DNS records instead of changing your old domain nameservers with the assigned Cloudflare nameservers for your CF account at Namecheap.
Disable the parking page which also might be enabled and interfering.
More in detail:
I have few domains there, no issue yet like your case.
Otherwise, write and contact https://sonic.so/ for some more information about this situation.
So I have run the above test a couple of times and here are the results –
All settings working on Cloudflare:
https://cf.sjr.org.uk/tools/check?bbdf7e1ebbbd481e86898588ba7398ff
Most settings wrong on Cloudflare:
https://cf.sjr.org.uk/tools/check?b4506264ec934214b066fb95efe96a57
Also, I spoke to Namecheap and they give me the whois link:
Which does clearly say cloudflare and is very constant as well.
Is there a way to understand why the Cloudflare settings are showing up as wrong, every once in a while?
May I ask where was domain firstly registered?
Was it at Namecheap?
Nevertheless, did you fransferred it to Cloudflare Registrar in the meantime?
This topic was automatically closed 15 days after the last reply. New replies are no longer allowed.
