| |
|
Welcome to KnowledgeSutra - Dear Guest | |
How To Park .de Domain
Started by mrchadmur, Nov 17 2006 01:07 AM
15 replies to this topic
#1
Posted 17 November 2006 - 01:07 AM
Hello i can't change my .de domain NameServers to your servers:
NS1.COMPUTINGHOST.COM
NS2.COMPUTINGHOST.COM
Error: RegCCTLDSvc: VerifyHostsForRegistration request failure - Hosts are NOT
on different networks
Hosts are NOT on different networks
Please help me!
Thank you very much!
NS1.COMPUTINGHOST.COM
NS2.COMPUTINGHOST.COM
Error: RegCCTLDSvc: VerifyHostsForRegistration request failure - Hosts are NOT
on different networks
Hosts are NOT on different networks
Please help me!
Thank you very much!
#2
Posted 17 November 2006 - 04:31 AM
Next time please provide your full domain and how you are hosted/registered with ComputingHost.
Who did you purchase your domain name from? What is your domain name? Do you have the ability to control nameserver change under your domain control panel?
Get back with these information for further assistance.
Who did you purchase your domain name from? What is your domain name? Do you have the ability to control nameserver change under your domain control panel?
Get back with these information for further assistance.
#4
Posted 19 November 2006 - 01:01 AM
Your NS records at the parent servers are:
parkct1.secureserver.net. [64.202.165.112 (NO GLUE)] [US]
parkct2.secureserver.net. [68.178.211.119 (NO GLUE)] [US]
[These were obtained from s.de.net]
You must unpark from GoDaddy and change those nameservers to ComputingHost's nameservers.
Once you have changed nameservers to ComputingHost, then use the cpanel to Park your domain OR contact ComputingHost support to change your registered domain with your hosting.
Two hosting companies cannot claim one domain name. And currently GoDaddy has the claim over your domain point.
parkct1.secureserver.net. [64.202.165.112 (NO GLUE)] [US]
parkct2.secureserver.net. [68.178.211.119 (NO GLUE)] [US]
[These were obtained from s.de.net]
You must unpark from GoDaddy and change those nameservers to ComputingHost's nameservers.
Once you have changed nameservers to ComputingHost, then use the cpanel to Park your domain OR contact ComputingHost support to change your registered domain with your hosting.
Two hosting companies cannot claim one domain name. And currently GoDaddy has the claim over your domain point.
#5
Posted 19 November 2006 - 03:32 PM
BuffaloHELP, on Nov 19 2006, 01:01 AM, said:
Your NS records at the parent servers are:
parkct1.secureserver.net. [64.202.165.112 (NO GLUE)] [US]
parkct2.secureserver.net. [68.178.211.119 (NO GLUE)] [US]
[These were obtained from s.de.net]
You must unpark from GoDaddy and change those nameservers to ComputingHost's nameservers.
Once you have changed nameservers to ComputingHost, then use the cpanel to Park your domain OR contact ComputingHost support to change your registered domain with your hosting.
Two hosting companies cannot claim one domain name. And currently GoDaddy has the claim over your domain point.
parkct1.secureserver.net. [64.202.165.112 (NO GLUE)] [US]
parkct2.secureserver.net. [68.178.211.119 (NO GLUE)] [US]
[These were obtained from s.de.net]
You must unpark from GoDaddy and change those nameservers to ComputingHost's nameservers.
Once you have changed nameservers to ComputingHost, then use the cpanel to Park your domain OR contact ComputingHost support to change your registered domain with your hosting.
Two hosting companies cannot claim one domain name. And currently GoDaddy has the claim over your domain point.
parkct1.secureserver.net - it's godaddy's default NameServers, when I change them to computinghost servers godaddy sends me an error:
Error: RegCCTLDSvc: VerifyHostsForRegistration request failure - Hosts are NOT
on different networks
Hosts are NOT on different networks
After this error, godaddy setup their default servers again.
Edited by mrchadmur, 19 November 2006 - 03:33 PM.
#6
Posted 19 November 2006 - 07:23 PM
Ah... so we're back to the beginning of a circle.
Have you contacted GoDaddy support line to see what might be causing the issue?
Basically, if you cannot relinquish nameserver for your domain it's either GoDaddy does not allow changing of nameserver by the client OR you do not have the permission to do so at this time.
Have you contacted GoDaddy support line to see what might be causing the issue?
Basically, if you cannot relinquish nameserver for your domain it's either GoDaddy does not allow changing of nameserver by the client OR you do not have the permission to do so at this time.
#8
Posted 21 November 2006 - 12:21 AM
I have just receive a reply from GoDaddy:
===============================
Thank you for contacting Online Support. There are 3 things to keep in mind when entering nameserver information for .DE domain names.
. The first 3 bits of the IP address (C-class) is different for each nameserver.
. A glue record is necessary for the domain on the nameservers.
. The SOA (Start of Authority) must be within the following guidelines:
refresh : 10000 - 86400
retry: 1800 -28800
expire: 604800 - 3600000
ttl: 180 - 345600
You can go to Denic.de to read more about the requirements needed for .DE domain names.
Please let us know if there is any other way we can assist you.
=================================
As I understand your NS not meet Denic.de requirements for .DE domain. Can you fix this problem ASAP?
Thanks.
===============================
Thank you for contacting Online Support. There are 3 things to keep in mind when entering nameserver information for .DE domain names.
. The first 3 bits of the IP address (C-class) is different for each nameserver.
. A glue record is necessary for the domain on the nameservers.
. The SOA (Start of Authority) must be within the following guidelines:
refresh : 10000 - 86400
retry: 1800 -28800
expire: 604800 - 3600000
ttl: 180 - 345600
You can go to Denic.de to read more about the requirements needed for .DE domain names.
Please let us know if there is any other way we can assist you.
=================================
As I understand your NS not meet Denic.de requirements for .DE domain. Can you fix this problem ASAP?
Thanks.
Edited by mrchadmur, 21 November 2006 - 12:23 AM.
Reply to this topic

1 user(s) are reading this topic
0 members, 1 guests, 0 anonymous users













