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