Bug? Can't give host name as NTP server in DHCPv6 Server page



  • I was looking up some public NTP server with AAAA records, 2.pool.ntp.org is supposed to be one, since I guess they have AAAA records for most/all 2.*.ntp.org servers.

    (Side question: is there also a 2.pfsense.pool.ntp.org with AAAA records?)

    So when I go to the Services:DHCPv6server page, click on the NTP Servers Advanced button, and enter
    2.pool.ntp.org, and save, then I get this error message:

    The following input errors were detected:

    A valid IPv6 address must be specified for the primary/secondary NTP servers.

    Am I not allowed to enter a host name there? Why not? Or what's the problem?



  • Per RFC, DHCP transfers NTP servers as IPs and cannot as hostname.

    @rcfa:

    (Side question: is there also a 2.pfsense.pool.ntp.org with AAAA records?)

    2 resolves as v6 for me, the rest as v4.



  • @cmb:

    Per RFC, DHCP transfers NTP servers as IPs and cannot as hostname.

    Well, transfer is one thing, set is another.

    My point is, over the course of days or months that IP address may change, while the hostname does not. Since DHCP leases are relatively short-lived, if I can enter a host name, which is resolved by the DHCP server before transmitting the IP address to the client, we'd still be complying with the RFC, yet wouldn't have to potentially keep manually tracking IP addresses.

    In other words, the server can resolve before it transmits the value.



  • What's set there goes straight into dhcpd.conf and it refuses hostnames. We could work around it, though that's a good deal of work to get right and keep up to date. Better as a feature request to ISC.



  • @cmb:

    Better as a feature request to ISC.

    ISC?




Locked