Force ipv4/ipv6 DNS resolution for NTP servers
Per http://doc.ntp.org/current-stable/confopt.html one should be able to prefix an NTP server hostname with either '-4' or '-6' to force DNS resolution in either ipv4 or ipv6.
"_Note that in contexts where a host name is expected, a -4 qualifier preceding the host name forces DNS resolution to the IPv4 namespace, while a -6 qualifier forces DNS resolution to the IPv6 namespace._"
This does not currently work in the pfsense GUI - attempting to do so corrupts the confirguration.
#1 Updated by Jim Pingle about 1 year ago
- Tracker changed from Bug to Feature
- Subject changed from Force ipv4/ipv6 DNS resolution for NTP servers fails to Force ipv4/ipv6 DNS resolution for NTP servers
- Category set to NTPD
- Priority changed from Normal to Very Low
- Target version set to Future
It's not a bug, it's just not supported.
It could be added. For example, with an option for each server in the NTP settings.
But for most people it isn't necessary.
#4 Updated by Monseigneur Phelypeaux 6 months ago
I'm facing the same bug. I have an IPv4-only network with IPv6 disabled in pfSense, but my DNS servers reply with both an IPv4 and IPv6 address. When I set ntp.ripe.net, NTPd will consistently pick the IPv6 over the IPv4 address. This then becomes 'unreach/pending' (same as in Christian's screenshot) and will not get a time. My only 'workaround' is to use an NTP server/pool for which the DNS lookup only replies with an IPv4 address.
I consider this a bug, the feature proposed by Christian would work, but would require user interaction.