Nameserver issues with co.za domain

[sp3ctre69]

Hi,

I am looking to transfer a co.za (South African) domain onto my server, but I am getting the following message back from the co.za registry:


;; The Nameserver "ns.<my domain>." at IP "<my ip>"
;; does not have a reverse FQDN entry and as such will be rejected.
;; A 'dig -x <my ip>' gives:-

; <<>> DiG 9.4.1-P1 <<>> -x <my ip>
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 57450
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;56.14.65.69.in-addr.arpa. IN PTR

;; AUTHORITY SECTION:
14.65.69.in-addr.arpa. 3600 IN SOA ns1.servernap.com. hostmaster.servernap.com. 2008052101 10800 3600 604800 3600

;; Query time: 0 msec
;; SERVER: 206.223.136.193#53(206.223.136.193)
;; WHEN: Thu Jun 19 20:45:23 2008
;; MSG SIZE rcvd: 106


As far as I can see I need to setup reverse lookups on my name servers? I thought this was already done, but apparently not. Please can someone point me in the direction of how to do it?

My name servers have been working fine for over a year, seemingly without reverse lookup? Is that normal?

Thanks in advance,

Jim

 

[jimmy1987]

Yes that is normal, i'm not having revese lookups at my server too and it has been running fine for over a year.

 

[sp3ctre69]

yeah, unfortunately the transfer is not being alowed until this situation is resolved... I really dont understand why co.za registry is so damn fussy?

 

[bhd]

We had a couple of customers (yesterday one and today two) trying to setup .co.za domains in their WHM reseller and they had exactly the same problem. We definitely have reverse DNS setup so I think .co.za is messed up.

(Also keep in mind that their ISP [Telkom, I beleive] has been experiencing problems and that could also cause their servers not to resolve your IP correctly)

 

[sp3ctre69]

We had a couple of customers (yesterday one and today two) trying to setup .co.za domains in their WHM reseller and they had exactly the same problem. We definitely have reverse DNS setup so I think .co.za is messed up.

(Also keep in mind that their ISP [Telkom, I beleive] has been experiencing problems and that could also cause their servers not to resolve your IP correctly)

Thanks for that... not sure what I can do, but it's good to hear i'm not alone.

 

[sp3ctre69]

Would someone mind please giving me a quick pointer as to getting reverse dns on my name servers (in WHM), not entirely sure other than it's the PTR record, right?

EDIT: Scratch that, I found I needed to get it added by my ISP... Gigenet are awesome! (they did it straight away, like always with my requests!)

Thanks

 

[bhd]

Thanks for that... not sure what I can do, but it's good to hear i'm not alone.

For the most port, just send through the request again. They usually get it right on the 2nd or 3rd attempt.

I just heard from one of our resellers and he told me it worked on his second attempt.