Bug #13019
closed
Setting an NTP FQDN kills DHCP Server
0%
Description
Very strange issue here. Setting a FQDN for one of the 3 NTP server options in the IPv4 DHCP server settings kills IP address assignment functions. I've started from a fresh pfSense system twice now so this issue is very reproducible.
How to reproduce:
1) Go to DHCP server setting for a VLAN (didn't test non-VLAN interface) and set reserve an IP address for a client
2) set "ca.pool.ntp.org" for NTP1
3) set "pool.ntp.org" for NTP2
4) Save settings
5) Observe that client never gets the assigned IP address. An ARP entry hangs around but is always incomplete. Sometimes letting DHCP server assign from a pool works but only after 30-60 seconds. Some clients give up quicker than other so you may get mixed results.
Updated by Kris Phillips about 2 years ago
I'm not able to reproduce this issue. I added two NTP settings under Advanced to the DHCP server, restarted the server, and pulled a DHCP lease just fine.
Updated by Viktor Gurov about 2 years ago
- Status changed from New to Feedback
- Priority changed from High to Normal
Updated by Jim Pingle about 2 years ago
- Status changed from Feedback to Rejected
I can't reproduce it either. This site is not for support or diagnostic discussion, however. Please start a post on the Netgate Forum with more details including the generated DHCP server config (/var/dhcpd/etc/dhcpd.conf) and the contents of the DHCP log. You can redact private information but try to retain as much as possible so that it will be possible to properly interpret the configuration and log contents.