Struggle for more than 2 weeks - Help needed

[Frankc]

Hello

I already achieved a lot and learnt very fast but RDNS is getting me down. I followed all the posts regarding RDNS everywhere and already asked three different companies to assist without any success yet. Somewhere, somehow we missid something.

Before we can register co.za domains the nameservers must have rdns.

The server have the following IP's available: 196.22.134.65, 66, 67, 68, 69 and 70

65 = network address
66 = shared IP and server address.

Initially the service provider assign 66 to ns1 and 67 to ns2 but after a lot of trying the error from registrar keeps saying that ns1 gave address 67. (not 66 as configured)

I at last gave up and changed ns1 to 67 and ns2 to 68 on my server while the registrar also change the rdns on their system to the same. (It's not delegated to me)

The rdns mismatch error from registrar at last disappeared but now getting the following error.

There is no SOA record for linux-servers.co.za. at 196.22.134.67
The Host is currently unpingable (unreachable)

The most common reason for this is that no one has got around to
setting this machine up yet as a Primary or Secondary server yet...
or has simply forgotten to do so. However, if this problem is not
fixed soon, access to your domain may be hindered by 'Lame
Delegations' (For both Ip 67 and 68)

The relevant domain is setup under the shared IP, 196.22.134.66.

Can anyone perhaps help or give me some clue as to what I must do pls?

 

[markhard]

as i know rDNS is setup by ISP/Dedicated Server provider, may be you can ask your ISP/Server provider

 

[elix]

http://www.dnsreport.com/tools/dnsreport.ch?domain=linux-servers.co.za
http://www.dnsstuff.com/tools/lookup.ch?name=linux-servers.co.za&type=A

[------------------------------------]

Are you sure that you have a DNS record for the domain name?

Regards,

 

[Frankc]

So far I can see the rdns resolve correct yes but point to IP's 196.22.134.67 and 68. My problem now is how to point or relay 67 and 68 to IP 66 (the shared IP with SOA records)

(www.dnsreport.com and www.dnsstuff.com are not accessible from us. They perhaps blocked access for some countries)

I am 3 years in hosting reseller business but this is my first server. Something that I am a bit confused with and perhaps related to above problem is.

All 5 IP addresses belongs to my server. Each IP address can be regarded as a "separate" server. The shared IP is the server address and domain setup under this server. The NS1 and NS2 have their own IP's and are therefore regarded as two separate servers (The goal of two nameservers is that it's located on two different servers so that one can act as backup in case the other one fails - With modern software it's however possible to have both on the same machine but let outside computers believe it's separate machines)

This is how far I understands it and think I am correct but:

How can I handle that in such way that NS1 and NS2 (separate servers) point to the shared IP where the accounts are hosted?

As is, the main problem from our Registrar is that there is no SOA records on IP's 67 and 68 (the nameservers) while the domains are actually under IP 66 with appropriate SOA records.

That is: The NS1 = 67, NS2 = 68 and actual hosting and SOA records IP 66.

 

[Frankc]

The domain linux-servers.co.za are NOT registered yet.

Our registrar require proper setup of SOA and rdns records before they register a domain.

I use megaproxy to access dnsstuff.com and it seems domain name servers NS1 and NS2 are setup correctly to point to IP 67 and 68 so it's just the SOA record for above domain that's still a problem. (as said it's under 66 while our registrar look for it under 67 and 68)

Can it perhaps be because I don't add master nameserver and/or cluster info at Cpanel main settings? This is a sisngle standalone server without any trust relationship between other outside servers.

 

[markhard]

the domain name need to be registered first! then create account on your cpanel, then contact your ISP/server provider to set rDNS for your domain.

 

[Frankc]

It don't work that way sorry.

With our registrar the domain must be setup correctly before they register the domain.

Can also not ask the provider to setup rdns because it's going to be hosted on our server and there is no trust relationship with the service provider's DNS server.

On all our other servers at Hostgator we simple create the account and then register the domain name.

With this new server it seems settings are not correct so creating an account on the server are not correct and the registrar reject registration requests due to that error.

 

[Frankc]

The Reverse DNS for name servers is already correct at datacenter level.

The problem is that it points to my server Ip addresses 67 and 68 while the hosting account was created (SOA records) under server shared Ip address 66.

It's not a datacenter level problem otherwise it don't make sense at all to install Cpanel. If only datacenters can create DNS entries then Cpanel and relevant services such as Bind is useless because nobody can add hosting accounts without "ag please daddy" to the datacenter to setup dns records.

 

[Frankc]

I am a Hostgator reseller for relative long time and that guys know their stuff but recently it happens twice that, when I created a hosting account and want to register it, the registar come back with the following. (rembember that with .co.za domains the hosting account must first be setup correctly before they register the domain)

There is no SOA record for exampledomainname.co.za. at 196.22.134.67
The Host is currently unpingable (unreachable)
!
! The most common reason for this is that no one has got around to
! setting this machine up yet as a Primary or Secondary server yet...
! or has simply forgotten to do so. However, if this problem is not
! fixed soon, access to your domain may be hindered by 'Lame
! Delegations' - which I'd rather not explain about - so please get
! someone to do something about this now?
!

There is no SOA record for exampledomainname.co.za. at 196.22.134.68
The Host is currently unpingable (unreachable)
!
! The most common reason for this is that no one has got around to
! setting this machine up yet as a Primary or Secondary server yet...
! or has simply forgotten to do so. However, if this problem is not
! fixed soon, access to your domain may be hindered by 'Lame
! Delegations' - which I'd rather not explain about - so please get
! someone to do something about this now?
!
ERROR: No valid nameservers found - rejecting request

As said before exampledomain.co.za was setup under shared IP 66 but the registrar error said it's not find under 67 and 68 (nameserver IP's)

 

[Frankc]

I am a Hostgator reseller for relative long time and that guys know their stuff but recently it happens twice that, when I created a hosting account and want to register it, the registar come back with the following. (rembember that with .co.za domains the hosting account must first be setup correctly before they register the domain)

There is no SOA record for exampledomainname.co.za. at 196.22.134.67
The Host is currently unpingable (unreachable)
!
! The most common reason for this is that no one has got around to
! setting this machine up yet as a Primary or Secondary server yet...
! or has simply forgotten to do so. However, if this problem is not
! fixed soon, access to your domain may be hindered by 'Lame
! Delegations' - which I'd rather not explain about - so please get
! someone to do something about this now?
!

There is no SOA record for exampledomainname.co.za. at 196.22.134.68
The Host is currently unpingable (unreachable)
!
! The most common reason for this is that no one has got around to
! setting this machine up yet as a Primary or Secondary server yet...
! or has simply forgotten to do so. However, if this problem is not
! fixed soon, access to your domain may be hindered by 'Lame
! Delegations' - which I'd rather not explain about - so please get
! someone to do something about this now?
!
ERROR: No valid nameservers found - rejecting request

As said before exampledomain.co.za was setup under shared IP 66 but the registrar error said it's not find under 67 and 68 (nameserver IP's)

A bit strange that, after so long period, hostgator server now also gave such error. (Their tech's fixed the problem but I don't know how they did it)

 

[Frankc]

This issue is now resolved thanks.

I unfortunatelly don't know how because the guys at http://www.platinumservermanagement.com fixed the problem for me.