Why do I need 2 IPs for a my VPS?
- Thread starter Tommyhara
- Start date
ISOS6
Verified User
You can use 1 IP for name servers. But som domain registrar does not accept same IP in hei GLUE records.
Thanks ISOS6 for your reply. it will be more problems if I only use 1 IP?
I checked with DNS health check tool, seem it has got yellow warning
nobaloney
NoBaloney Internet Svcs - In Memoriam †
If you only use one IP# for both DNS servers then yes, you'll see a warning with any system you use to check DNS, because you in effect only have one nameserver.
You should really use two separate servers for DNS if at all possible because in the event of DNS failure you'd still be better off if your sites returned an IP# even if it doesn't exist. Search these forums for slave dns.
Jeff
You should really use two separate servers for DNS if at all possible because in the event of DNS failure you'd still be better off if your sites returned an IP# even if it doesn't exist. Search these forums for slave dns.
Jeff
kaufenpreis
Verified User
- Joined
- Aug 24, 2014
- Messages
- 40
If you want to have a private nameservers you need atleast 2 ip and 1 ip for web. I dont recomend you to have private nameserver on a vps. For security you need to split dns in to 2 vps on diffrents ip network.
Last edited:
nobaloney
NoBaloney Internet Svcs - In Memoriam †
Let's make the answer a bit more generic by explaining:
Best practices are to always have redundant DNS. DNS was designed with redundancy in mind, and one of the methods used to force DNS redundancy was (is) for registrars to require you have two nameservers. Some TLDs require they be on separate IP#s, but all require at least two DNS servers.
And DNS checking sites all let you know if the domain you're checking uses redundant DNS, by checking not only for at least two nameserver names, two IP#s, and even if they appear to be on the same or adjacent netblocks, which usually means they're geographically close (on the same network).
To easily get around the need for two nameservers without requring you to have two separate physical nameservers, DirectAdmin will set up two different nameserver names pointing to your same physical machine. But that's not real redundancy; only a way to satisfy registration requirements.
Best practices means you should either run two separate nameservers, or buy a service somewhere to slave your DNS with various degrees of automation. (I used to offer the service but have recently stopped, since all my clients ended up hosting their own on separate machines).
DirectAdmin offers you Multi-Server Option so if you have two DirectAdmin servers you can share all your DNS zones among both. DirectSlave (search these forums) allows you to use Multi-Server Option even if you only have one server running DirectAdmin, as long as you rent another small VPS server (hopefully on another network). I also offer Master2Slavel DNS Replicator (search these forums), which was ritten before DirectAdmin includedl Multi-Server Option, which does the same thing.
No matter how you do it, best practice is to run DNS on two separate machines. If you can't do that, then yes, get a second IP# for your only DirectAdmin server, and fake it.
Jeff
Best practices are to always have redundant DNS. DNS was designed with redundancy in mind, and one of the methods used to force DNS redundancy was (is) for registrars to require you have two nameservers. Some TLDs require they be on separate IP#s, but all require at least two DNS servers.
And DNS checking sites all let you know if the domain you're checking uses redundant DNS, by checking not only for at least two nameserver names, two IP#s, and even if they appear to be on the same or adjacent netblocks, which usually means they're geographically close (on the same network).
To easily get around the need for two nameservers without requring you to have two separate physical nameservers, DirectAdmin will set up two different nameserver names pointing to your same physical machine. But that's not real redundancy; only a way to satisfy registration requirements.
Best practices means you should either run two separate nameservers, or buy a service somewhere to slave your DNS with various degrees of automation. (I used to offer the service but have recently stopped, since all my clients ended up hosting their own on separate machines).
DirectAdmin offers you Multi-Server Option so if you have two DirectAdmin servers you can share all your DNS zones among both. DirectSlave (search these forums) allows you to use Multi-Server Option even if you only have one server running DirectAdmin, as long as you rent another small VPS server (hopefully on another network). I also offer Master2Slavel DNS Replicator (search these forums), which was ritten before DirectAdmin includedl Multi-Server Option, which does the same thing.
No matter how you do it, best practice is to run DNS on two separate machines. If you can't do that, then yes, get a second IP# for your only DirectAdmin server, and fake it.
Jeff
microz
Verified User
In some occassion end-user using external platform to manage their mail system, but example, google apps. In this case if primary dns fails, if you have redundant dns, at least end-user may continue receiving mails. Now this type of configutarion require of at least two server (vps) for run correctly.
http://help.directadmin.com/item.php?id=97 (you need two DA licenses )
http://help.directadmin.com/item.php?id=97 (you need two DA licenses )
Thanks Jeff,
Can you guide me how to create DNS with 2 IPs in DirectAdmin or having an article mentioned about this?
