Created Date: January 29,2020

Created by: DSandelman

Are there any plans to actively use a qualified domain name (such as pool.ntp.org), via a DNS to lookup a time server?

While the DNS lookup in the Nettime block is a great feature, I have run into what was once a good IP a year ago+ for a time server, is no longer a reliable time server, or non functional at all.

If Nettime can use a domain name like pool.ntp.org, we can be sure over time, a valid IP address will always come back for a good time server.

We can add a variable for the IP address of a time server, but would prefer not having end users doing an update, when a DNS lookup, can do the job automatically.

Thanks

David

Created Date: January 29,2020

Created by: franji1

We later added a DNSLOOKUP instruction, hence you can use THAT instruction with a domain name, stick it in a variable IP Address, then use the variable IP Address in the NETTIME instruction.

We call that our "Tinker Toy " approach. DNSLOOKUP is a tool. NETTIME is a tool. However, we realize that not everyone knows about all the various "Tinker Toys ", so we may address this at some point in the future. :eek:

Created Date: January 29,2020

Created by: franji1

Daaaa....

Use the DNSLOOKUP for the timer server domain (pool.ntp.org), then use the result, passed via a variable for the IP in the NETTIME.

How simple....

Thanks!

The DNSLOOKUP should fail if that SNTP server is down or your PLC cannot access the Internet (On Error...).