1 |
On Wed, Dec 16, 2015 at 4:26 AM, Alan McKinnon <alan.mckinnon@×××××.com> wrote: |
2 |
> |
3 |
> Solution: obey best practice. Never run auth and cache on the same |
4 |
> address. On the same machine is fine, they are different daemons. |
5 |
> |
6 |
|
7 |
Which one listens on port 53? Also, how do you point the caching |
8 |
daemon at the authoritative daemon for internal servers/domains/etc? |
9 |
My authoritative server for doubleclick.net is not the same as the one |
10 |
you'll find in the .net servers. Also, for the domains I use |
11 |
internally the DNS server and resolution is different within my LAN |
12 |
from what you'd see on the internet. I know that at my employer |
13 |
internal DNS resolution is not the same as what you'd find outside the |
14 |
organization, so this isn't an issue unique to small setups. |
15 |
|
16 |
One of the reasons I run auth and cache on the same host is that it |
17 |
greatly simplifies dependencies. If I want to run them on separate |
18 |
containers then they'll either need static addresses, or need to use |
19 |
DHCP, which means the DHCP server has a potential circular dependency |
20 |
with the DNS servers. Plus most of my containers are going to need |
21 |
DNS so these containers need to be running before other containers get |
22 |
started. |
23 |
|
24 |
For a large-scale datacenter the separated approach makes a lot of |
25 |
sense. If you're running 5000 hosts having two (or likely 10 counting |
26 |
various backups/etc) that you start first isn't a big deal, and |
27 |
neither is dedicating a bit of hardware to DNS/DHCP. If you're |
28 |
running all your services on one host, it can get a bit messy when you |
29 |
start having multiple DNS servers all running on different IPs on the |
30 |
same host. It can of course still be done. |
31 |
|
32 |
I just use BIND for both. It isn't the best solution, but it is adequate. |
33 |
|
34 |
-- |
35 |
Rich |