Results 1 to 12 of 12
Thread: Registrar says NSs aren't reachable to be set up, hosting provider says registrar has to set them up
-
11-03-2016, 05:41 AM #1Newbie
- Join Date
- Oct 2016
- Posts
- 7
Registrar says NSs aren't reachable to be set up, hosting provider says registrar has to set them up
Hi there,
I recently bought a VPS from a vendor (which is here too), with one IP (in retrospective, I should've had two, as most registrars won't allow for one only and it's considered good practice to have two). I'm having troubles to change the DNS with the registrar and, while the registrar blames the bad name servers set up and the VPS vendor blames the registrar for not doing their job, I'm left hanging.
So, with due apologies for the long message below, I would appreciate it if you could please have a look and suggest some solution(s) if possible.
I want the domain name mydomain.com to have its own name servers, like this, ns1.mydomain.com and ns2.mydomain.com. The domain name already exists and it has a website on it, which works just fine and is now hosted somewhere else - but, naturally, I want to transfer it to the VPS I bought. I made the data transfer successfully, I've tested the installation and everything looks all right. The only thing left is to change the name servers at the registrar, from its current hosting provider to the VPS I bought. However, despite my long email exchange with the registrar and almost as many with the VPS vendor, I'm exactly where I started, nowhere, that is.
When I try to change the name servers in the registrar panel, I get an error (can't be done type of error) and I get in tocuh with the registrar to enquire about it. The registrar says "The problem are actually the nameservers itself. The ones you want to set are not online or reachable, so you can not set them as your domain would not work with them." I go to the VPS vendor, and he says that if the registrar won't first change the name servers there, they cannot be online; the registrar needs to add the name servers before he checks that these are online. The IP the VPS vendor gave us is online.
I go back to the registrar with a request to tell me what exactly does he gets when he makes his tests. Is there an error because I have the same IP on both name servers, or is there somehting else? I make a print screen with my current set up in the DNS Zone in WHM and ask him is he sees anything out of order there, something that I would need to fix. I use Google Public DNS for DNS resolution, so that shouldn't be a problem. I then ask for specifics, precisely to avoid generic answers and learn from my mistakes if there's something to learn:
- what tools / methods are you using to determine that the names of the servers can't be resolved on the internet?
- which IP are you testing? Our VPS IP is 185.x.x.x - and it's certainly reachable, like I said before.
- How exactly do you make a lookup on the server names?
... thinking that if he answers point by point, I can then explain in those terms what I have done and why - should that be the method he is using, although I doubt it - simply pinging ns1.mydomain.com won't work. To which he goes like this:
"Okay, so - if you want to set nameservers for a domain, you can not use nameservers that are not online yet. The nameservers need to be online, active and give answer. So the domaintool checks if the server you filled in is reachable and works. This is not the case for your servers - these are not online und the name ns1.mydomain.com and not reachable. The system does not accept servernames that are not reachable right now."
The VPS vendor says that the registrar needs to actually register these name servers for them to work. If he can't do it using eh domain name (ns1.mydomain.com), he should use the IP I've provided them with. The set up can only be made at the registrar end and there's nothing he can help me with. He goes on to suggest that since the registrar doesn't allow me to set up the name servers using the IP, I should change the registrar. This, while sounds appealing, would add extra expenses, particularly time-wise and I'm not very keen to do it.
Now this is been happening since 2 weeks ago or more and I'm at the end of my patience. I need to make a decision and I would appreciate someone more experienced than me to suggest a direction.
Thanks for reading.
P
-
11-03-2016, 07:47 AM #2The VPS vendor says that the registrar needs to actually register these name servers for them to work
They need to be created before they can be used.Your one stop shop for decentralization
-
11-03-2016, 01:56 PM #3Newbie
- Join Date
- Oct 2016
- Posts
- 7
Thanks, @bear, that was helpful.
It looks like I finally got through to the registrar as well after I requested the guy assigned with my case to pass it to someone else in the firm.
-
11-04-2016, 11:09 AM #4Newbie
- Join Date
- Oct 2016
- Posts
- 7
An update to my situation.
The registrar tells me the following:
"There are 2 things wrong - first, the names of the nameservers ns1.mydomain.com and ns2.mydomain.com need to be resolvable by name (so the nameservers answer with the IP).
Also we can not register two nameservers on the same IP-address, you would have to set up 2 IP's."
I know some registrars don't accept the same IP for both nameservers, so I suppose I'll have to buy another IP. But what does he mean when he says that the nameservers need to be resolvable by name? Can these nameservers be resolvable by name before they are registered? And if yes, what exactly does that mean for me, what do I have to do to comply with that, please?
Thanks.
/P
-
11-04-2016, 04:25 PM #5Technology Consultant
- Join Date
- Feb 2013
- Posts
- 657
Ok,
1) Your hosting provider will create the DNS Zones in their server.
2) Your hosting provider will give you the IP addresses for their DNS Servers. (Where the specific zones for your domain name were created).
3) The domain registrar will now be able to accept your IPs as nameservers and finally allow your domain to work.
If this is not respected, it will not work. And yes, it will be unreachable for your domain registrar. (This apply, when using your host dns servers to hold your domain zone).█ IT
█ Is Nice.
-
11-05-2016, 08:54 AM #6Newbie
- Join Date
- Oct 2016
- Posts
- 7
Thanks for your input.
Forgive my ignorance please, but if I understood this correctly, then for:
1) It should already be done, apart from the second IP, which will need to be added in the DNS Zones.
2) It already gave me one IP; once it gives me the 2nd one and I'll add it in the DNS Zones, it should all be all right, am I correct?
But I don't quite understand what does the registrar means by "nameservers answer with the IP" and not being resolvable by name. Is there something else that I have to consider or change?
Thanks again.
-
11-05-2016, 04:00 PM #7Technology Consultant
- Join Date
- Feb 2013
- Posts
- 657
The thing is, the registrar servers have to "authenticate" if your domain exists in your host or not, if it doesn't, you'll see the error you're speaking about.
So it doesn't matter whether this is 1 IP, 2 IPs, 3 IPs, ect. This might be a registrar condition, mostly requires two different IPs to work. Although, the servers "configured" to "listen" in these IPs, might "reply" hey this domain "xxx.com" exists here, if they doesn't, then the registrar won't accept the configuration...█ IT
█ Is Nice.
-
11-06-2016, 08:33 PM #8Web Hosting Master
- Join Date
- Nov 2004
- Location
- Tega Cay
- Posts
- 823
You will need to add A records for your ns records. Maybe that's what the registrar requires. Seems weird they can't just set your nameservers up though. Every registrar I use has this automated and does not require the domain to have any DNS before setup of the nameservers. Who is the registrar?
-
11-07-2016, 10:38 AM #9Newbie
- Join Date
- Nov 2016
- Posts
- 12
-
11-07-2016, 04:30 PM #10Newbie
- Join Date
- Oct 2016
- Posts
- 7
-
11-07-2016, 04:35 PM #11Newbie
- Join Date
- Oct 2016
- Posts
- 7
-
11-08-2016, 05:19 PM #12Newbie
- Join Date
- Oct 2016
- Posts
- 7
OK, this can be closed now, the transfer was finally made and it's all working fine. Apparently I had set up everything correctly, it was just the "missing" second IP for the DNS2 that caused the incredibly long delay.
Thanks everyone for your answers, I appreciate it.
Similar Threads
-
What does it take to be the perfect hosting provider?
By DinkyHost in forum Web HostingReplies: 24Last Post: 08-25-2012, 02:28 AM -
It has to be done
By AussieHosts in forum Web Hosting LoungeReplies: 541Last Post: 03-30-2008, 09:50 AM -
OMG - Dialtone Internet has to be the BEST host EVER!!!!
By B-Broker in forum Web HostingReplies: 1Last Post: 08-11-2001, 08:21 PM -
It has to be done
By AussieHosts in forum Web HostingReplies: 462Last Post: 06-21-2001, 11:23 AM