I have been trying to setup a PTR record and or RDNS on my server which I kept getting errors all the time and when I got to set it up clean with no Errors it's not working or I cannot get my Registrar to register a domain on it. I have configured two ISPConfig Server's one being the main hosting server with with all services and the other one as a secondary DNS Server both using a Single interface. I have an IP range of 197.228.128.0/24 and the main server is using a Static IP of 197.228.128.21/24 and the Secondary server is on 197.228.128.33/24. And What I need to know is how do I configure RDNS for these servers to get my Registrar to register my domains on it. I have downloaded the ISPConfig book which has made me more confused than I was before and there is no Section providing proper and clear explanasion on how to get this to work. Searching the net for answers has let me to find more people having issues and with no proper solutions. This is what I get from the Registrar when registering the domain's and their support has advised me that the RDNS is not working. Provided Nameserver information Primary Server : ns1.somedomain.co.za Secondary 1 : ns2.somedomain.co.za Domain "mydomain.co.za", SOA Ref (), Orig "" Pre-existing Nameservers for "mydomain.co.za":- Syntax/Cross-Checking provided info for Nameserver at 6a: ns1.somedomain.co.za Syntax/Cross-Checking provided info for Nameserver at 6e: ns2.somedomain.co.za Adding application Checking quoted Nameservers.... NS1-1 FQDN: ns1.somedomain.co.za. NS1-1 IPV4: 197.228.128.21 NS1-1 ORIGIN: ns1.somedomain.co.za. NS1-1 E-MAIL: [email protected]. NS1-1 SER-NO: 2015111804 NS1-1 NS RECORD1: ns1.somedomain.co.za. NS1-1 NS RECORD2: ns2.somedomain.co.za. NS2-1 FQDN: ns2.somedomain.co.za. NS2-1 IPV4: 197.228.128.33 NS2-1 ORIGIN: ns1.somedomain.co.za. NS2-1 E-MAIL: [email protected]. NS2-1 SER-NO: 2015111804 NS2-1 NS RECORD1: ns1.somedomain.co.za. NS2-1 NS RECORD2: ns2.somedomain.co.za. ERROR: No valid nameservers found - rejecting request. --- ZA Central Registry Co.Za Domain Administrators For Support: http://www.coza.net.za or e-mail [email protected] Telephone: +27 11 314 0077 Fax: +27 11 314 0088
The rdns should not be related to registering a domain as no registra checks rdns, so these are probably 2 non related issues. So we should start with the dns zone of the domain that you want to register first, please post a screenshot of the dns zone that you added in ispconfig and a screenshot of the records tab of that zone. The Message "ERROR: No valid nameservers found - rejecting request." refers to the dns zone, it is not related to reverse dns. Regarding rdns record, there are detailed step by step instructions with screenshots on how to create a verse dns record in the ispconfig manual, as howtoforge subscriber you can download the ispconfig manual here: https://www.howtoforge.com/download-the-ispconfig-3-manual But it is unlikely that you have to add a rdns record at all as such a rdns record is the dns record of the IP and is added by the ISP that manages this subnet and not be the user that uses this subnet on its server.
The records look fine doe far. the ns1 and ns2 a-records are not necessary as the dns server of this zone is not the zone itself, but it does not hurt that they exist, they will just not be used. I tested your dns record and it works fine, both ns servers are responding properly for the domain, so the dns setup is correct. Code: root@ns10:/# dig @ns1.datafusion.co.za dfhostedservices.co.za ; <<>> DiG 9.8.4-rpz2+rl005.12-P1 <<>> @ns1.datafusion.co.za dfhostedservices.co.za ; (1 server found) ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 23570 ;; flags: qr aa rd; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 0 ;; WARNING: recursion requested but not available ;; QUESTION SECTION: ;dfhostedservices.co.za. IN A ;; ANSWER SECTION: dfhostedservices.co.za. 3600 IN A 197.221.107.21 ;; AUTHORITY SECTION: dfhostedservices.co.za. 3600 IN NS ns2.datafusion.co.za. dfhostedservices.co.za. 3600 IN NS ns1.datafusion.co.za. ;; Query time: 183 msec ;; SERVER: 197.221.107.21#53(197.221.107.21) ;; WHEN: Tue Nov 24 07:24:05 2015 ;; MSG SIZE rcvd: 103 root@ns10:/# dig @ns2.datafusion.co.za dfhostedservices.co.za ; <<>> DiG 9.8.4-rpz2+rl005.12-P1 <<>> @ns2.datafusion.co.za dfhostedservices.co.za ; (1 server found) ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 43730 ;; flags: qr aa rd; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 0 ;; WARNING: recursion requested but not available ;; QUESTION SECTION: ;dfhostedservices.co.za. IN A ;; ANSWER SECTION: dfhostedservices.co.za. 3600 IN A 197.221.107.21 ;; AUTHORITY SECTION: dfhostedservices.co.za. 3600 IN NS ns2.datafusion.co.za. dfhostedservices.co.za. 3600 IN NS ns1.datafusion.co.za. ;; Query time: 189 msec ;; SERVER: 197.221.107.33#53(197.221.107.33) ;; WHEN: Tue Nov 24 07:24:15 2015 ;; MSG SIZE rcvd: 103
So what you are saying is that this should work fine with no problems? This is one feedback I also got from the Registrar. Good Day Kindly ask your ISP to please setup the domain on the specified name servers, once the domain is setup on the given name servers, please resend your application form to "[email protected]" and also please cc "[email protected]". Regards Vicky
The domain dfhostedservices.co.za is setup on nameservers ns1.datafusion.co.za and ns2.datafusion.co.za, you can send them the dig output from above.
Hi I gave my registrar all the details and they advised that There are no PTR records on my name server's. Is there a way that I can add just one PTR record to use with any domain I register on My ISPConfig? Thanks and Regards Ernest Manamela
A PTR record is the dns record of the IP and not the domain, so a PTR is not domain specific. Normally the PTR is set by the datacenter where you host the server or the internet access provider that assigned you the IP. The PTR is not related to the registration of a domain, so I have no Idea why the insist on a PTR. As the provider where you got the Ip address of this server from ify they maintain the ptr or if the delegated the PTR for this IP subnet to your server. If they tld you that the DNS for this IP is delegated to you, then add a reverse zone for this IP address as described in the ISPConfig manual.
Bind is restarting fine. service bind9 restart * Stopping domain name service... bind9 waiting for pid 1053 to die [ OK ] * Starting domain name service... bind9
Ok, this means that Bind rejected the dns zone. you can test the pri.107.221.197.in-addr.arpa.err zone file with the named_checkzone tool from BIND to see why it got rejected.
Finally I have won the Battle, Was about to give-up on ISPConfig. Hope all works well from this Point on.
