How to see if the entire COZA (.co.za) name space is down and / or why it’s sporadically not resolving names

Try this sequence:

  1. First determine root name servers:
$ dig NS co.za

; <<>> DiG 9.18.33-1~deb12u2-Debian <<>> NS co.za
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 34539
;; flags: qr rd ra ad; QUERY: 1, ANSWER: 3, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
;; QUESTION SECTION:
;co.za. IN NS

;; ANSWER SECTION:
co.za. 7200 IN NS coza1.dnsnode.net.
co.za. 7200 IN NS ns2.dns.net.za.
co.za. 7200 IN NS ns2us.dns.business.

;; Query time: 20 msec
;; SERVER: 102.135.240.1#53(102.135.240.1) (UDP)
;; WHEN: Thu Mar 13 13:52:29 SAST 2025
;; MSG SIZE rcvd: 123

Root name servers are coza1.dnsnode.net, ns2.dns.net.za, and ns2us.dns.business

2. Find out more about any (or all) of the name servers:

$ dig ns2us.dns.business

; <<>> DiG 9.18.33-1~deb12u2-Debian <<>> ns2us.dns.business
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 54683
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
;; QUESTION SECTION:
;ns2us.dns.business. IN A

;; ANSWER SECTION:
ns2us.dns.business. 1338 IN A 147.135.106.236

;; Query time: 176 msec
;; SERVER: 102.135.240.1#53(102.135.240.1) (UDP)
;; WHEN: Thu Mar 13 13:53:27 SAST 2025
;; MSG SIZE rcvd: 63

3. Finally, see if you can see the start of authority (SoA) for your own domain:

$ dig @147.135.106.236 SOA vanderhost.co.za
;; communications error to 147.135.106.236#53: timed out


$ ping vanderhost.co.za
ping: vanderhost.co.za: Temporary failure in name resolution

You’ll also have these error sending email:

  • host lookup did not complete
  • Temporary Local Problem

What to do?

Contact dns.business tech support or wait till any cast is working again

Share this article

Leave a Reply

Your email address will not be published. Required fields are marked *