NTP through DNS?
mayer at pdmconsulting.net
Fri Sep 21 19:14:41 UTC 2018
On 9/21/2018 7:56 AM, Ray Bellis wrote:
> On 21/09/2018 12:47, Danny Mayer wrote:
>> Putting on both my BIND9 and NTP hats for a moment:
>> This answer makes no sense. NTP uses standard DNS FQDN's for all of its
>> references to NTP servers whether it's using pool, server or peer. I
>> have no idea where the reverse zone comes in though I haven't read the
>> whole thread. the NTP service all belong to domains, whether internal or
>> external. There is a DHCP option that we have seen but it seems to cause
>> more confusion that anything.
>> You can create a DNS A or AAAA or even a CNAME in your local DNS that
>> the NTP server can use and it all works.
>> Let me know if I misunderstood what this is really about.
> I believe you have.
> The discussion was about automated _discovery_ of the DNS name of your
> NTP server using an additional level of indirection so that it can be
> automatically configured without using DHCP.
That's easy. Create a FQDN called ntp in your domain and have it be a
set of CNAMES pointing to the ntp servers you want to use. The ntpd pool
option will take care of setting the multiple servers. You don't need
the complexity of SRV records.
More information about the bind-users