name servers taken a while to update

Hi

Am trying to add two new domains to my cwp server

i have created two accounts  fixcomputers.co.uk and njt-builders.com.
(others work fine on it for example freddio.co.uk or linuxshed.com - test domains for learning how to use cwp).

updated the name servers to ns1 and ns2.clickns.cloud but the domains don't seem to be updating waited over 3 days for njt-builders.com and a day for fixcomputers.co.uk -you can see its updated on whatsmydns in Pakistan or India but none of the other countries show the name servers updating.

Anything am missing?

Thanks in advance.

Thanks
Dave

not sure if this is because of the issue

i read something about restarting the bind dns server which i did and i got this error

● named.service - Berkeley Internet Name Domain (DNS)
   Loaded: loaded (/usr/lib/systemd/system/named.service; enabled; vendor preset: disabled)
   Active: failed (Result: exit-code) since Fri 2024-11-29 17:50:03 UTC; 38s ago
  Process: 2093310 ExecStop=/bin/sh -c /usr/sbin/rndc stop > /dev/null 2>&1 || /bin/kill -TERM $MAINPID (code=exited, status=0/SUCCESS)
  Process: 2089687 ExecReload=/bin/sh -c if /usr/sbin/rndc null > /dev/null 2>&1; then /usr/sbin/rndc reload; else /bin/kill -HUP $MAINPID; fi (code=exited, status=1/FAILURE)
  Process: 2093328 ExecStart=/usr/sbin/named -u named -c ${NAMEDCONF} $OPTIONS (code=exited, status=1/FAILURE)
  Process: 2093325 ExecStartPre=/bin/bash -c if [ ! "$DISABLE_ZONE_CHECKING" == "yes" ]; then /usr/sbin/named-checkconf -z "$NAMEDCONF"; else echo "Checking of zone files is disabled"; fi (code=exited, status=0/SUCCESS)
 Main PID: 697 (code=exited, status=0/SUCCESS)

Nov 29 17:50:03 svruk01.clickns.cloud named[2093330]: using 1 UDP listener per interface
Nov 29 17:50:03 svruk01.clickns.cloud named[2093330]: using up to 21000 sockets
Nov 29 17:50:03 svruk01.clickns.cloud named[2093330]: loading configuration from '/etc/named.conf'
Nov 29 17:50:03 svruk01.clickns.cloud named[2093330]: /etc/named.conf:13: change directory to '/var/named' failed: permission denied
Nov 29 17:50:03 svruk01.clickns.cloud named[2093330]: /etc/named.conf:13: parsing failed: permission denied
Nov 29 17:50:03 svruk01.clickns.cloud named[2093330]: loading configuration: permission denied
Nov 29 17:50:03 svruk01.clickns.cloud named[2093330]: exiting (due to fatal error)
Nov 29 17:50:03 svruk01.clickns.cloud systemd[1]: named.service: Control process exited, code=exited status=1
Nov 29 17:50:03 svruk01.clickns.cloud systemd[1]: named.service: Failed with result 'exit-code'.
Nov 29 17:50:03 svruk01.clickns.cloud systemd[1]: Failed to start Berkeley Internet Name Domain (DNS).

Hi,

The DNS propagation process is fully automatic and it could take up to 72 hours to be finished.

According to whatsmydns.net your domains use the nameservers:

ns1.clickns.cloud
ns2.clickns.cloud

So it looks good for me.

Yes, the key is to give it time (24, 48, up to 72 hours) to propagate worldwide. Unless your infrastructure is Cloudflare based, then you will just have to wait seconds for worldwide propagation.