| I have a slightly different need, which a twist of this technology may
address. We have two LANs in our building. We're deploying NTP, and
will set up two NTP servers on each LAN. For obvious network
performance reasons, we'd like all the NTP clients on LAN A to sync
with the two LAN A servers, and the LAN B NTP clients to sync with the
LAN B NTP server. But, this is proving difficult to deploy. We'd like
to use SMS to automate the installation of the NTP client on hundreds
of Windows systems, and I can't think of any clean way to.
So I'm wondering if DNS could come to the rescue. It would be very
neat to use the same two NTP server names across our site, but have
them translate to the correct servers, based on the LAN the client is
in. Each client is configured with the same two site DNS servers,
though (I hope) the LAN A DNS server is listed first on LAN A clients.
Hmm. Is there an opportunity here?
Thanks!
tl
|
| Terry,
I don't think you can have the same name resolve
to 2 different pointers, depending on the client
address - that would violate the rules of DNS, which
is basically trying to provide a consistent view
of name to address translation.
I'm not sure this is even worth worrying about, if
your concern is traffic - NTP is not going to cause
much overhead in the routers.
Some alternative possibilities:
- different SMS profiles for each LAN, so you could
specify the local DNS & NTP servers (and any other
things which need to change based on network address -
how is the default router set?)
- all the hosts use the same name for the NTP server, but
it's defined (differently for each subnet) in a local
HOSTS file.
|