Forced IP resolution during the configuration commit for NTP Servers with FQDN

Unable to save NTP servers as FQDN (DNS names) when NTP server is configured using a hostname (e.g., 0-3.pool.ntp.org), the CLI immediately resolves it and saves the specific IP address into the configuration. 

The configuration can't store the FQDN (domain name) to handle dynamic IP changes in the NTP pool.

Configuration used:

set system ntp server 0.pool.ntp.org
set system ntp server 1.pool.ntp.org
set system ntp server 2.pool.ntp.org
set system ntp server 3.pool.ntp.org


eg:

[edit]
root@NTP-FQDN# set system ntp server 0.pool.ntp.org 
Feb 06 10:58:48 >>>>>Timestamps

[edit]
root@NTP-FQDN# show | compare 
Feb 06 10:58:52 >>>>>Timestamps
[edit system]
+   ntp {
+       server 198.137.202.56;
+   }

root@NTP-FQDN> show host 0.pool.ntp.org 
Feb 06 11:00:23
0.pool.ntp.org has address 23.186.168.131
0.pool.ntp.org has address 66.118.231.14
0.pool.ntp.org has address 72.14.186.59
0.pool.ntp.org has address 104.167.215.195
0.pool.ntp.org mail is handled by 0 .


root@NTP-FQDN> show configuration | display set | match ntp 
Feb 06 11:00:34
set system ntp server 198.137.202.56



root@NTP-FQDN> show host 0.pool.ntp.org                        
Feb 06 11:03:09
0.pool.ntp.org has address 209.177.158.85
0.pool.ntp.org has address 44.190.5.123
0.pool.ntp.org has address 66.118.230.14
0.pool.ntp.org has address 198.12.95.197
0.pool.ntp.org mail is handled by 0 .

root@NTP-FQDN> show configuration | display set | match "ntp server" 
Feb 06 11:03:28
set system ntp server 198.137.202.56

When hostnames (FQDNs) are configured for system services such as:

• NTP
• TACACS
• RADIUS
• SNMP

The device performs a DNS lookup during the commit process and resolves the configured hostname to its corresponding IP address.

After the commit is completed:

• The running configuration retains only the resolved IP address
• The original FQDN/hostname is not preserved
• This behavior is consistent across all supported components and is not specific to NTP

Currently no mechanism available in Junos OS to maintain dynamic DNS-based resolution after commit or to keep the hostname in the active configuration.