: Should I sub-domain my VPS name servers? While trying to setup up my VPS, I came across the name server settings. Most of what I found online were regarding how to setup name servers, which
While trying to setup up my VPS, I came across the name server settings.
Most of what I found online were regarding how to setup name servers, which advised something like ns1.mydomain.com and then my IP address.
Why should I setup a name server as above (as opposed to what is currently default set by provider)?
Why should I create a second name server like 'ns2', and should it be a different IP or the same as 'ns1'? (If the IP for 'ns1' and 'ns2' match isn't that redundant?)
The cPanel has name servers—do those have to match the domain name servers?
More posts by @Karen161
2 Comments
Sorted by latest first Latest Oldest Best
It sounds like you aren't really wanting to set up your own nameservers, rather you are assigning child nameservers.
This may be useful to thinly disguise where your site is hosted e.g. I have done this when I don't want it blatantly obvious that two sites are associated by being with the same hosting company. Note the 'thinly' :P
Another use is if you are running a hosting business, then you can tell your customers to use ns1.yourhost.com and voila, their domain is managed by your server. It looks more professional than using your hosting service's nameservers.
Setting your own nameservers instructs the domain provider to stop managing the DNS zone file (kinda like setting for a domain)
One of the advantages to this is that it allows easy hosting migration.
In terms of redundancy having two nameserver on one or more IPs that are on the same ip block doesn't matter. Since if one goes down so does the other.
It might help that it is two different network paths. (Don't know)
Terms of Use Create Support ticket Your support tickets Stock Market News! © vmapp.org2024 All Rights reserved.