> I don't know about NIS, but using DHCP will allow you to configure which
> DNS servers your clients are supposed to use. This requires you to set-up
> a DHCP server but it's quite easy.
I played a bit with DHCP these days but, as far as I understood, it
doesn't allow you to share '/etc/resolv.conf' file over your network
but it allows you to give directions about how to set
'/etc/resolv.conf' (and '/etc/yp.conf' and '/etc/ntp.conf') file(s) on
the client machines.
This is interesting as a last resort but it isn't what I was looking
for that is to share the file itself the way I share '/etc/ethers' and
'/etc/hosts' files over the network with NIS.
I'm still wondering whether does NIS provide any way to share
information about DNS servers or not and if not why?
I don't mean that NIS should, I'd just like to know why, the reason
and what's the problem with it.
Multiple Sites - DNS Client configuration ...DHCP is handled by the local DC. ... There are some 100 users at the HQ and there are some 20-45 users at each Remote Site.... For the Remote Sites - should only the 'local' DNS Server IP Address be handed out by DHCP or should the 'local' DNS Server IP Address as well as the two 'HQ' DNS Servers be handed out via DHCP? ...clients at the HQ will - via DHCP - have two DNS Servers while all the clients at the Remote Sites will have three. ... (microsoft.public.windows.server.active_directory)
Re: Mac OS X Clients not added to DNS ... dynamically added to DNS as they get their DHCP addresses. ... OS X clients do get DHCP addresses and are listed in the DHCP server ... but they are not added to the DNS servers.... (microsoft.public.windows.server.dns)
Re: DNS entries on client after updating new dns servers ... use DHCP to hand out IP addresses to our clients....correct DNS Servers show for a little while but always reverts back ... Are you sure you have only one DHCP server on your network? ... and that they don't have an alternate configuration set (if ... (microsoft.public.windows.server.dns)
Re: Multiple Sites - DNS Client configuration ... Configure at least all site DNS and one from the main office, so in case that the site DC/DNS is down, the clients are able to connect to the domain, even it can take longer. ... VPN between the HQ and each remote Site (so, HQ-rem1, HQ-rem2, ... In the HQ there are two DCs that are also GCs and DNS Servers.... HQ both being DHCP Servers with a 60/40 split). ... (microsoft.public.windows.server.active_directory)
Re: Multiple Sites - DNS Client configuration ... Configure at least all site DNS and one from the main office, so in case that the site DC/DNS is down, the clients are able to connect to the domain, even it can take longer. ... VPN between the HQ and each remote Site (so, HQ-rem1, HQ-rem2, ... In the HQ there are two DCs that are also GCs and DNS Servers.... HQ both being DHCP Servers with a 60/40 split). ... (microsoft.public.windows.server.active_directory)
