Couple of questions. You indicate that you have migrated your web site to a VPS. Have you also set up (or do you intend to set up) your own internal DNS servers? And is so, where?
Note that the web site and name servers are two distinct functions and may reside on different servers. For a small enterprise it is not uncommon to run them on a single server (or VPS).
Your web site is up and running on the VPS; I’ll assume the domain foo.com and the IP address of 22.214.171.124 for the web server in the examples below.
The name servers will resolve the domain name www.foo.com to the address 126.96.36.199. Clients on the Internet attempting to resolve the address will need to know 2 things:
[li]What name servers are authoritative (responsible) for the domain foo.com?[/li][li]What is the IP address associated with www.foo.com?[/li][/ol]
The former function is the one your hosting company is telling you to address with the registrar. Note that you will need two authoritative name servers for your domain, and you nominally have the following options:
[li] Allow your registrar to do this for you. Registrars typically offer this function (sometimes free, sometimes for a fee) and provide a “control panel” or similar to manage your domain. In that case, you would use the control panel to add an address record (A record):[/li]
www.foo.com -> 188.8.131.52
This is the easiest route.
[li] Configure and maintain DNS software on your VPS or other server(s). Without knowing the particulars I can’t comment in detail, but by way of example you might configure BIND (the named daemon) on a Linux installation to act as the authoritative server for foo.com, and include the aforementioned A record in that configuration.[/li]
Note that you will need two name servers. For small installations without a great need for redundancy, you could use two IP addresses on the same interface of your server (or VPS), assuming your OS and/or provider supports it. For example, your VPS might have the the following IP addresses assigned to its interface:
If you ran your own DNS software, you would configure the software to listen on both of these addresses and use them as your primary and secondary DNS servers for foo.com by registering them with your registrar. For example:
The registrar would then provide NS (name server) records for your domain, and you would add A records to your own configuration thus:
ns1.foo.com -> 184.108.40.206
ns2.foo.com -> 220.127.116.11
Note that some registrars provide “glue records” and include the A records in their configuration.
Some registrars and hosting companies offer secondary DNS service wherein they operate the second name server. In that case, you would only need to run one name server (the primary), and configure the software to use the company’s system as the secondary. Again, this may be fee-based, and the particulars depend on your configuration.
[li] Use third-party or other name servers. Some companies provide standalone DNS management without requiring you to purchase registry services (a quick Google search reveals easyDNS, for example*). This would be similar to (a), above.[/li][/LIST]
Obviously, (a) and © are the easiest options if you are not technically inclined and do not wish to manage a DNS server.
A final note: if your company sends and receives email at foo.com, or has other aliases, subdomains, or A records in the DNS, these will need to be cared for in whatever scheme you decide to go with.
- I am not affiliated with this company.