Bug #14991
closed
Kea does not allow FQDNs for NTP servers but input validation does not prevent them from being added
Added by Chris Linstruth 6 months ago.
Updated about 1 month ago.
Plus Target Version:
24.03
Description
It looks like kea does not allow FQDNs for NTP servers.
ntp-servers 42 ipv4-address true false
Apparently ISC DHCPD did. If a user has an FQDN there kea will not start.
- Subject changed from Kea does not allow FQDNs for ntp-servers - pfSense allows one to be entered. to Kea does not allow FQDNs for NTP servers but input validation does not prevent them from being added
- Target version set to 2.8.0
- Plus Target Version set to 24.03
- Status changed from New to Confirmed
I can confirm this behavior on 23.09.
- Has duplicate Bug #15012: NTP assigned to KEA DHCP Clients causes service to fail added
- Has duplicate Bug #15023: KEA DHCP and ERROR [kea-dhcp4.dhcp4.0x545c1212000] DHCP4_PARSER_FAIL failed to create or run parser for configuration element subnet4: option data does not match option definition (space: dhcp4, code: 42) added
Brilliant pfSense DevTeam!
Just confirm the same bug.
I reproduce the same environment and receive the same bug/behavior.
This even MAKE IMPOSSIBLE TIME SYNC inside all infrastructure behind pfSenseif. (Or You need entering FQDN / IP of internal time server MANUALLY ON EACH DEVICE in infrastructure).
Please fix.
- Assignee set to Jim Pingle
- Status changed from Confirmed to Feedback
- % Done changed from 0 to 100
- Status changed from Feedback to Resolved
Validation is working, as is the backend filtering. Kea starts properly every time now.
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by