Feature #10322: Force ipv4/ipv6 DNS resolution for NTP servers - pfSense - pfSense bugtracker

Custom queries

2.4.5-p1 - Resolved/Closed
2.5.0 - Resolved/Closed
2.5.1 - Resolved/Closed
2.5.2 - Resolved/Closed
2.6.0 - Resolved/Closed
2.7.0 - Resolved/Closed
2.7.1 - All Open Issues
2.7.1 - Resolved/Closed
2.7.2 - Resolved/Closed
2.8.0 - All Open Bugs
2.8.0 - All Open Features
2.8.0 - All Open Issues
2.8.0 - All Open Regressions
2.8.0 - Feedback
2.8.0 - Needs Attention
2.8.0 - New/Confirmed
2.8.0 - Pull Requests
2.8.0 - Regressions affecting 2.7.0
2.8.0 - Resolved/Closed
21.02.2/2.5.1 - Resolved/Closed
21.05 Plus - All Closed Issues
21.05.1 Plus Target - All Closed Issues
21.05.1 Target - All Closed Issues
22.01 Plus - All Closed Issues
22.01 Target - All Closed Issues
22.05 Plus - All Closed Issues
22.05 Target - All Closed Issues
23.01 Plus - All Closed Issues
23.01 Target - All Closed Issues
23.05 Plus - All Closed Issues
23.05 Target - All Closed Issues
23.05.1 Plus - All Closed Issues
23.05.1 Target - All Closed Issues
23.09 Plus - All Closed Issues
23.09 Target - All Closed Issues
23.09.1 Plus - All Closed Issues
23.09.1 Target - All Closed Issues
24.03 Plus - All Closed Issues
24.03 Target - All Closed Issues
24.11 Plus - All Closed Issues
24.11 Plus - All Open Issues
24.11 Plus - Feedback Issues
24.11 Plus - Needs Attention/Work
24.11 Plus - New/Confirmed/In Progress Issues
24.11 Target - All Closed Issues
24.11 Target - All Open Issues
25.01 Plus - All Closed Issues
25.01 Plus - All Open Issues
25.01 Plus - Feedback Issues
25.01 Plus - Needs Attention/Work
25.01 Plus - New/Confirmed/In Progress Issues
25.01 Plus - Pull Request Review
25.01 Plus - Waiting on Merge
25.01 Target - All Closed Issues
25.01 Target - All Open Issues
All Open Issues assigned to Me
All Open Pull Requests
Any Target - All Open Regressions
Any Target - Feedback Issues
CE-Next - All Closed Issues (Move to specific target)
CE-Next - All Open Issues
CE-Next - Feedback (Likely needs target changed)
New Issues by Category - Future Target
New Issues by Category - No Target
New Issues by Category - No Target+Future
No Target - All Open Issues (Base Only)
No Target - New Issues (Base Only)
No Target - New Issues (Base and Packages)
Release Notes - Plus Target Version (DO NOT EDIT)
Release Notes - Target Version (DO NOT EDIT)

Actions

Copy link

Feature #10322

closed

Force ipv4/ipv6 DNS resolution for NTP servers

Added by Christian Borchert over 4 years ago. Updated about 4 years ago.

Status:

Resolved

Priority:

Very Low

Assignee:

Viktor Gurov

Category:

NTPD

Target version:

2.5.0

Start date:

03/08/2020

Due date:

% Done:

100%

Estimated time:

Plus Target Version:

Release Notes:

Description

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.

Files

ipv6 resolution.PNG (47.1 KB) ipv6 resolution.PNG

ipv6 resolution on a system with ipv6 disabled

Christian Borchert, 03/10/2020 03:07 PM

History
Notes
Property changes
Associated revisions

Actions

Copy link

Updated by Jim Pingle over 4 years 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.

Actions

Copy link

Updated by Christian Borchert over 4 years ago

Jim,

For an unknown reason - even though my setup is configured for only ipv4, sometimes NTP will randomly resolve servers to ipv6 addresses and try to connect....

This option would fix that bug

Actions

Copy link

Updated by Christian Borchert over 4 years ago

File ipv6 resolution.PNG ipv6 resolution.PNG added

Actions

Copy link

Updated by Monseigneur Phelypeaux about 4 years 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.

Actions

Copy link