I have a load of domain names registered with 1&1, and just bought some hosting with another provider (long story...)
My new host required me to create new private nameservers with my domain registrar (ns1 and ns2.mydomain.com) and change my domains to the new nameservers.
However, I found that the 1&1 control panel doesn't provide this, so I just set up two subdomains of mydomain (ns1 and ns2), then set A records pointing these subdomains to the IP addresses of my new host. 1&1 control panel then let me change nameservers to ns1 and ns2.mydomain.com
Everything seems to be working, but I get the feeling this is a fudge. Am I going to get problems further down the line?
Thanks!
My new host required me to create new private nameservers with my domain registrar (ns1 and ns2.mydomain.com) and change my domains to the new nameservers.
Makes no sense. I doubt that this is actually true. I suspect you are misinterpreting them, or this is simply a "suggestion".
All your host should care is that your domain name resolves to the IP address of your web server. In fact, they shouldn't even care about that. It shouldn't concern them should you choose for whatever reason to simply refer to your host by IP address and forget about DNS altogether. It's none of their business.
However, I found that the 1&1 control panel doesn't provide this, so I just set up two subdomains of mydomain (ns1 and ns2)
Are you sure that you created subdomains, or just hosts? If you simply added A records to your domain, you created hosts.
Sorry, the misuse of the term "subdomain" is an itch I scratch here often. :)
then set A records pointing these subdomains to the IP addresses of my new host.
Sounds like you created hosts, which is what you want, if you really do want or need to create vanity (they probably mean "vanity" - again the term "private nameserver" makes no sense) nameservers.
This is one of several necessary steps needed to create vanity nameservers. Except that you would point them to to your (plural, if you are following the recommended practice) nameservers, not your web host.
You would also need to register the nameservers, and create or modify NS records.
Everything seems to be working, but I get the feeling this is a fudge. Am I going to get problems further down the line?
I get the feeling it is all completely unnecessary, and they are making/suggesting that you jump through hoops that you don't need to jump through.
I would delete the new records you have added, and simply change your A records for the base domain and "www" host to your new web server's IP address and be done with it.
If "everything is working", then you somehow managed to already do this, despite your new hosts confusing instructions.
And then consider whether the move to this host was a wise one, given their apparent misdirection.
Just to be clear, I've taken a VPS hosting service with them and they provided the following instruction:
"Please note that on our network a VPS is like your own private space on the network to work from. This is why we provide your account with two dedicated IP addresses that you will need to use to register your name servers with. Please view the below name servers and IP addresses that you should use to register them.
ns1.mydomain.com <==> xx.xx.xx.xx
ns2.mydomain.com <==> xx.xx.xx.xx "
They then give instructions on creating nameservers with various registrars.
I followed the first few steps of this guide, as far as the reverse DNS instructions - couldn't see an option for that on 1&1 control panel so I stopped there: [faq.1and1.com...]
Does this make sense? Any comments appreciated - I'm keen to learn this stuff!
Cheers
[edited by: FaceLikeBambi at 7:17 pm (utc) on Oct. 6, 2007]
Please note that on our network a VPS is like your own private space on the network to work from. This is why we provide your account with two dedicated IP addresses that you will need to use to register your name servers with.
Sounds to me like they are assuming that you will run your own DNS servers on your VPS. And run them both on the same machine, to boot.
Both are horrible ideas. I won't go into the detailed reasons, as it's been covered here on WebmasterWorld many times before.
You are much better off using your registrar's DNS servers.
