Why ntpd is not updating DNS resolution after initial start - Red Hat Customer Portal

Log in to Your Red Hat Account

Your Red Hat account gives you access to your profile, preferences, and services, depending on your status.

If you are a new customer, register now for access to product evaluations and purchasing capabilities.

Need access to an account?

If your company has an existing Red Hat account, your organization administrator can grant you access.

If you have any questions, please contact customer service.

Red Hat Account Number:

Red Hat Account

Customer Portal

For your security, if you’re on a public computer and have finished using your Red Hat services, please be sure to log out.

Select Your Language

Issue

The ntpd (NTP Daemon) is configured to connect to servers via a DNS alias (CNAME). There was a change of time server and the CNAME was updated to point to the new server, but ntpd is not resolving the new IP at runtime it keeps its association to the original IP despite it is no longer reachable, until the ntpd is restarted.
It appears that ntp development branch 4.2.7 has implemented an async DNS resolver which can be called any time, instead of calling getaddrinfo() only once at start up.
Is there any workaround for ntp4.2.6 ?

Environment

Red Hat Enterprise Linux 6.4
ntp4.2.6

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.

Here are the common uses of Markdown.

Code blocks

~~~
Code surrounded in tildes is easier to read
~~~

Links/URLs

[Red Hat Customer Portal](https://access.redhat.com)