Hi,
Just wondering if someone can shed any light on this situation...
Basically my old dedicated server disappeared last week due to my old hosting company dissapearing...
I got a new server with UK2.net and I'm having some problems:
The original name servers set on the domain where ns1.uk2net.com and ns2.uk2net.com, i have the domain theserverstation.com which i usually use ns1.theserverstation.com & ns2 respectively.
I went to godaddy.com where theserverstation.com is from and put in the information to set ns1 & ns2 to the ip addresses on my server which are 2 from the 3 ip addresses i have; 83.170.87.25 (ns1) and 83.170.87.121 (ns2)
If i now ping ns1.theserverstation.com it resolves to 83.170.87.25 and ns2 resolves to 83.170.87.121 correctly, however any domain that has these set as the name servers; greenday.co.uk and willymason.co.uk and even theserverstation.com just time out as if the nameservers arn't working.
The only domain that does work on the server is the server address which is server50784.uk2net.com, that apparently according to uk2 has the ns records of ns1.uk2net.com and ns2.uk2net.com which point to their DNS servers of 83.170.64.2 & 83.170.69.2.
The response i got from UK is:
"think I figured out your problem. The theserverstation.com and other domains on the server seem to be pointing to ns1.theserverstation.com and ns2.theserverstation.com
However, to use these two as nameservers they have to be mapped onto some sort of IP address not onto themselves which is what it seems at the moment. The reason server50784.uk2net.com works because it is using uk2 nameservers 83.170.64.2 and 83.170.69.2. So, I think before you can use ns1.theserverstation.com and ns2.theserverstation.com as name servers they have to be glued to some IP as in the ones on your server.
However, if you try and change for example greenday.co.uk to use fasthost's (I presume fasthost is the domain's registra) nameservers and have this domain point to 83.170.87.25 then I think this should work. Let me know how you get on."
I don't want to change any of the nameservers of any domains as i like them all pointing to ns's i control so that i can change the server at any point and they will resolve there.
I get this report from:
http://www.dnsreport.com/tools/dnsreport.ch?domain=theserverstation.com
Says this:
Parent
PASS Missing Direct Parent check OK. Your direct parent zone exists, which is good. Some domains (usually third or fourth level domains, such as example.co.us) do not have a direct parent zone ('co.us' in this example), which is legal but can cause confusion.
INFO NS records at parent servers Your NS records at the parent servers are:
ns1.theserverstation.com. [83.170.87.25] [TTL=172800] [GB]
ns2.theserverstation.com. [83.170.87.121] [TTL=172800] [GB]
[These were obtained from f.gtld-servers.net]
PASS Parent nameservers have your nameservers listed OK. When someone uses DNS to look up your domain, the first step (if it doesn't already know about your domain) is to go to the parent servers. If you aren't listed there, you can't be found. But you are listed there.
PASS Glue at parent nameservers OK. The parent servers have glue for your nameservers. That means they send out the IP address of your nameservers, as well as their host names.
PASS DNS servers have A records OK. All your DNS servers either have A records at the zone parent servers, or do not need them (if the DNS servers are on other TLDs). A records are required for your hostnames to ensure that other DNS servers can reach your DNS servers. Note that there will be problems if your DNS servers do not have these same A records.
NS
FAIL NS A timeout occurred getting the NS records from your nameservers! None of your nameservers responded fast enough. They are probably down or unreachable. I can't continue since your nameservers aren't responding. If you have a Watchguard Firebox, it's due to a bug in their DNS Proxy, which must be disabled (31 Jul 2006 UPDATE: several years after being informed of this, there is a rumor that there is a fix that allows the Watchguard DNS proxy to work).
Anyone got any ideas? Losing my patience with uk2 support lol.
Cheers
Just wondering if someone can shed any light on this situation...
Basically my old dedicated server disappeared last week due to my old hosting company dissapearing...
I got a new server with UK2.net and I'm having some problems:
The original name servers set on the domain where ns1.uk2net.com and ns2.uk2net.com, i have the domain theserverstation.com which i usually use ns1.theserverstation.com & ns2 respectively.
I went to godaddy.com where theserverstation.com is from and put in the information to set ns1 & ns2 to the ip addresses on my server which are 2 from the 3 ip addresses i have; 83.170.87.25 (ns1) and 83.170.87.121 (ns2)
If i now ping ns1.theserverstation.com it resolves to 83.170.87.25 and ns2 resolves to 83.170.87.121 correctly, however any domain that has these set as the name servers; greenday.co.uk and willymason.co.uk and even theserverstation.com just time out as if the nameservers arn't working.
The only domain that does work on the server is the server address which is server50784.uk2net.com, that apparently according to uk2 has the ns records of ns1.uk2net.com and ns2.uk2net.com which point to their DNS servers of 83.170.64.2 & 83.170.69.2.
The response i got from UK is:
"think I figured out your problem. The theserverstation.com and other domains on the server seem to be pointing to ns1.theserverstation.com and ns2.theserverstation.com
However, to use these two as nameservers they have to be mapped onto some sort of IP address not onto themselves which is what it seems at the moment. The reason server50784.uk2net.com works because it is using uk2 nameservers 83.170.64.2 and 83.170.69.2. So, I think before you can use ns1.theserverstation.com and ns2.theserverstation.com as name servers they have to be glued to some IP as in the ones on your server.
However, if you try and change for example greenday.co.uk to use fasthost's (I presume fasthost is the domain's registra) nameservers and have this domain point to 83.170.87.25 then I think this should work. Let me know how you get on."
I don't want to change any of the nameservers of any domains as i like them all pointing to ns's i control so that i can change the server at any point and they will resolve there.
I get this report from:
http://www.dnsreport.com/tools/dnsreport.ch?domain=theserverstation.com
Says this:
Parent
PASS Missing Direct Parent check OK. Your direct parent zone exists, which is good. Some domains (usually third or fourth level domains, such as example.co.us) do not have a direct parent zone ('co.us' in this example), which is legal but can cause confusion.
INFO NS records at parent servers Your NS records at the parent servers are:
ns1.theserverstation.com. [83.170.87.25] [TTL=172800] [GB]
ns2.theserverstation.com. [83.170.87.121] [TTL=172800] [GB]
[These were obtained from f.gtld-servers.net]
PASS Parent nameservers have your nameservers listed OK. When someone uses DNS to look up your domain, the first step (if it doesn't already know about your domain) is to go to the parent servers. If you aren't listed there, you can't be found. But you are listed there.
PASS Glue at parent nameservers OK. The parent servers have glue for your nameservers. That means they send out the IP address of your nameservers, as well as their host names.
PASS DNS servers have A records OK. All your DNS servers either have A records at the zone parent servers, or do not need them (if the DNS servers are on other TLDs). A records are required for your hostnames to ensure that other DNS servers can reach your DNS servers. Note that there will be problems if your DNS servers do not have these same A records.
NS
FAIL NS A timeout occurred getting the NS records from your nameservers! None of your nameservers responded fast enough. They are probably down or unreachable. I can't continue since your nameservers aren't responding. If you have a Watchguard Firebox, it's due to a bug in their DNS Proxy, which must be disabled (31 Jul 2006 UPDATE: several years after being informed of this, there is a rumor that there is a fix that allows the Watchguard DNS proxy to work).
Anyone got any ideas? Losing my patience with uk2 support lol.
Cheers