If you PUT a NAME - FQDN instead of an IP address in for NTP servers KEA-DHCP will not start.
-
Example:
ERROR [kea-dhcp4.dhcp4.0x14eab5c12000] DHCP4_INIT_FAIL failed to initialize Kea server: configuration error using file '/usr/local/etc/kea/kea-dhcp4.conf': option data does not match option definition (space: dhcp4, code: 42): Failed to convert string to address '0.north-america.pool.ntp.org': Invalid argument (/usr/local/etc/kea/kea-dhcp4.conf:77:33)
-
@badjoodani see https://forum.netgate.com/topic/184226/psa-kea-dhcp-does-not-like-dns-names-breaks-isc-to-kea-migration/10
-
@badjoodani said in If you PUT a NAME - FQDN instead of an IP address in for NTP servers KEA-DHCP will not start.:
option data does not match option definition (space: dhcp4, code: 42): Failed to convert string to address '0.north-america.pool.ntp.org'
This means that 'kea' isn't doing 'DNS' for you.
It will not converting '0.north-america.pool.ntp.org' into one of these "15.204.87.223 23.143.196.199 158.51.99.19 83.147.242.172".
Btw : ISC DHCP did't do that neither.Here : the doc : https://kea.readthedocs.io/en/kea-2.5.0/arm/dhcp4-srv.html and look for "ntp-server" on that page :
That's an IPv4-address, not a host name. Or a pool name.
ISC DHCP : was the same.Maybe, in the past, the pfSense GUI converted a host name into an IP ? I can't recall.
Same question, a couple of years ago : KEA DHCP NTP server option behavior.
