No, I don't think that's the problem.
Your configuration is buggy.
expireddomains.co.za -> NS -> ns3.gransy.com.
ns3.gransy.com -> NS -> ns1.anycastdns.cz.
And
D:\temp>nslookup -type=NS anycastdns.cz.
anycastdns.cz nameserver = ns5.gransy.cz
anycastdns.cz nameserver = ns2.gransy.cz
anycastdns.cz nameserver = ns4.gransy.cz
anycastdns.cz nameserver = ns3.gransy.cz
anycastdns.cz nameserver = ns.gransy.cz
That's a name server loop, there are no glue records.
And ns.gransy.cz -> SOA ns.gransy.com.
Same with dig:
:~$ dig NS ns.gransy.com.
; <<>> DiG 9.11.3-1ubuntu1.11-Ubuntu <<>> NS ns.gransy.com.
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 38707
;; flags: qr rd ra ad; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 512
;; QUESTION SECTION:
;ns.gransy.com. IN NS
;; AUTHORITY SECTION:
gransy.com. 1132 IN SOA ns1.anycastdns.cz. root.gransy.com. 2588707815 86400 900 1209600 1800
;; Query time: 0 msec
;; SERVER: 192.168.0.1#53(192.168.0.1)
;; WHEN: Wed May 06 00:31:32 CEST 2020
;; MSG SIZE rcvd: 100
:~$ dig NS anycastdns.cz.
; <<>> DiG 9.11.3-1ubuntu1.11-Ubuntu <<>> NS anycastdns.cz.
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 60502
;; flags: qr rd ra ad; QUERY: 1, ANSWER: 5, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 512
;; QUESTION SECTION:
;anycastdns.cz. IN NS
;; ANSWER SECTION:
anycastdns.cz. 1511 IN NS ns3.gransy.cz.
anycastdns.cz. 1511 IN NS ns2.gransy.cz.
anycastdns.cz. 1511 IN NS ns5.gransy.cz.
anycastdns.cz. 1511 IN NS ns4.gransy.cz.
anycastdns.cz. 1511 IN NS ns.gransy.cz.
;; Query time: 0 msec
;; SERVER: 192.168.0.1#53(192.168.0.1)
;; WHEN: Wed May 06 00:35:52 CEST 2020
;; MSG SIZE rcvd: 138
:~$ dig NS ns3.gransy.cz.
; <<>> DiG 9.11.3-1ubuntu1.11-Ubuntu <<>> NS ns3.gransy.cz.
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 6261
;; flags: qr rd ra ad; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 512
;; QUESTION SECTION:
;ns3.gransy.cz. IN NS
;; AUTHORITY SECTION:
gransy.cz. 1800 IN SOA ns.gransy.com. root.gransy.com. 2588707810 86400 900 1209600 1800
;; Query time: 178 msec
;; SERVER: 192.168.0.1#53(192.168.0.1)
;; WHEN: Wed May 06 00:36:04 CEST 2020
;; MSG SIZE rcvd: 96
:~$ dig NS ns3.gransy.com.
; <<>> DiG 9.11.3-1ubuntu1.11-Ubuntu <<>> NS ns3.gransy.com.
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 57872
;; flags: qr rd ra ad; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 512
;; QUESTION SECTION:
;ns3.gransy.com. IN NS
;; AUTHORITY SECTION:
gransy.com. 714 IN SOA ns1.anycastdns.cz. root.gransy.com. 2588707815 86400 900 1209600 1800
;; Query time: 0 msec
;; SERVER: 192.168.0.1#53(192.168.0.1)
;; WHEN: Wed May 06 00:36:22 CEST 2020
;; MSG SIZE rcvd: 101
One domain -> next domain -> next domain -> first domain.
Query NS, answer SOA.
So it's unclear how to find the ip addresses of your name servers.