Problems when parking a domain.

gardar

Member
May 14, 2007
7
0
151
I had my dns managed at another server but recently made my own nameserver in cpanel.

When I had my dns managed on another server I had my domain registered on the IP's of that server... ns1.domain.net and ns2.domain.net
Now when I made my own nameserver I changed the IP's for ns1.domain.net and ns2.domain.net at my domain registrar to my new IP's (the ip's of my nameserver).
It has been working great, I have been able to add and park .com, .net, .info domains in my cpanel.

But when I was trying to park two .org domains I just bought (at the same registrar as some of the domains already parked at my server) then I ran into some problems...

I get this error message:

Error from park wrapper: Using nameservers with the following IPs: xx.xxx.xxx.x,xx.xxx.xxx.x Sorry, the domain is already pointed to an IP address that does not appear to use DNS servers associated with this server. Please transfer the domain to this servers nameservers or have your administrator add one of its nameservers to /etc/ip.remotedns and make the proper A entries on that remote nameserver.
the IP's there (not shown for security reasons) are the IP's of my old nameserver.... however my ns1.domain.com and ns2.domain.com have been successfully registered on to the IP's of my new nameserver... (Just ran a whois check on ns1.domain.com and ns2.domain.com at about 5 different sites and they all showed my new IP's).

So as you can see the problem does not seem to be at my domain or my domain registrars end but at the cpanel end.
Icluded all this (useless and useful) information in case it matters.

Can anyone help me?

Thanks in advance.
 

gardar

Member
May 14, 2007
7
0
151
Ok, I got two fails.

FAIL Open DNS servers

ERROR: One or more of your nameservers reports that it is an open DNS server. This usually means that anyone in the world can query it for domains it is not authoritative for (it is possible that the DNS server advertises that it does recursive lookups when it does not, but that shouldn't happen). This can cause an excessive load on your DNS server. Also, it is strongly discouraged to have a DNS server be both authoritative for your domain and be recursive (even if it is not open), due to the potential for cache poisoning (with no recursion, there is no cache, and it is impossible to poison it). Also, the bad guys could use your DNS server as part of an attack, by forging their IP address. Problem record(s) are:

Server xxxxxxxxxx (removed the IP of NS1) reports that it will do recursive lookups. [test] Server xxxxxxxx (removed the IP of ns2) reports that it will do recursive lookups. [test] See this page for info on closing open DNS servers.
and then what seems to be the real problem...


FAIL Mismatched glue


ERROR: Your nameservers report glue that is different from what the parent servers report. This will cause DNS servers to get confused; some may go to the IP provided by the parent servers, while others may get to the ones provided by your authoritative DNS servers. Problem record(s) are:

ns2.my-domain.net.:
Parent server (g.gtld-servers.net) says A record is (the ip I want as ns2), but
authoritative DNS server (the IP I want as ns1) says it is (the IP of my old ns2)

ns1.my-domain.net.:
Parent server (g.gtld-servers.net) says A record is (the IP I want as ns1), but
authoritative DNS server (the IP I want as ns1) says it is (the ip of my old ns1)

ns1.my-domain.net.:
Parent server (g.gtld-servers.net) says A record is (the ip I want as ns1), but
authoritative DNS server (the IP I want as ns2) says it is (the IP of my old ns1)

ns2.my-domain.net.:
Parent server (g.gtld-servers.net) says A record is (the IP I want as ns2), but
authoritative DNS server (the IP I want as ns2) says it is (the ip of my old ns2)
I have removed the IP's. Explaination:
the IP I want as ns1 - means that there is the IP I have set my ns1 to be on.
the IP I want as ns2 - means that there is the IP I have set my ns2 to be on.
the IP of my old ns1 - means there is the IP of ns1 on my old nameserver.
the IP of my old ns2 - means there is the IP of ns2 on my old nameserver.



Can anyone tell me how I could fix this?

Thanks in advance :)