Thanks for your interest in my problem. It's quite a mission to solve given the dns propagation delays. So I'll tackle it one step at a time.
I have access to a web server via a Plesk interface. It has an IP number 1.2.3.4 and a name h1-2-3-4.n-01.net. On this server, I can create a domain called mydomain.co.za and add DNS records to the domain. Some of the records I have are:
ns1.mydomain.co.za. A 1.2.3.4
ns2.mydomain.co.za. A 1.2.3.5
1.2.3.4 / 24 PTR ns1.mydomain.co.za.
1.2.3.5 / 24 PTR ns2.mydomain.co.za.
So now I assume that the nameserver ns1.mydomain.co.za exists on the server h1-2-3-4.n-01.net.
Then I try to register the domain via the coza bot. It requires a FQDN of the nameserver and the ip address of it. So I provide:
Primary server FQDN: ns1.mydomain.co.za
Primary server IP address: 1.2.3.4
Secondary server FQDN: ns2.mydomain.co.za
Secondary server IP address: 1.2.3.5
However, it fails with the message:
***BEGIN ERROR MESSAGE***
There is no pre-existing SOA record for mydomain.co.za.
CHECKING: Nameserver Pair 6a, 6b: ns1.mydomain.co.za, 1.2.3.4
INFO: Name "h1-2-3-4.n-01.net" -
ERROR: Nameserver Pair 6a, 6b:, Reverse check. ns1.arounduct.co.za not in h1-2-3-4.n-01.net
! Nameserver Pair 6a, 6b:, Reverse check. You specified 1.2.3.4 would give ns1.mydomain.co.za, DNS returned h1-2-3-4.n-01.net
***END ERROR MESSAGE***
Which makes sense because the IP 1.2.3.4 points to the server h1-2-3-4.n-01.net. And the server h1-2-3-4.n-01.net hosts multiple domains!
So I have a hunch that although I have PTR records associated with mydomain.co.za on the 1.2.3.4 server, it is insufficient because reverse dns is not enabled. Can this be enabled with Plesk administrator privaleges?
Regarding the solution suggest by Faris: unfortunately the coza bot requires that I have fully functional nameservers before it will register the domain, and it gives no default nameservers.
I'm so confused. Any help would be greatly appreciated.
Regards,
Indika