|
|
|
|
| Re: Slave's DNS [message #65692 is a reply to message #65587] |
Fri, 22 May 2009 19:12   |
|
kochen:
As long as your client uses that as their nameservers and you set the DNS server for your client as being localhost (master), you can do that.
For our servers (we run Kloxo), I set it up as DNS servers being the master server and a server we set up to handle DNS only. Kloxo handles the rest of transferring the files. This ensures that we will keep our DNS up at all times.
My Site
|
|
|
|
| Re: Slave's DNS [message #65698 is a reply to message #65693] |
Fri, 22 May 2009 19:24   |
|
If you mean tracert/traceroute, then it will show the slave IP as that is the A record for the domain.
To do that, though, you would need to make a new DNS template for each slave (has to be done anyway). Something like:
master-dns:
_base_: 1.2.3.4
slave1-dns:
_base_: 2.3.4.5
slave2-dns:
_base_: 3.4.5.6
My Site
|
|
|
|
| Re: Slave's DNS [message #65704 is a reply to message #65701] |
Fri, 22 May 2009 19:39   |
|
Yes, as long as company2 on the slave uses its own nameservers (such as ns1.slave.com and ns2.slave.com), and you set the A records for both ns1 and ns2 to the slave AND you set the DNS server pool for them to be the slave they're hosted on ONLY, then it would work 100%.
My Site
|
|
|
|
|