Failed to resolve time server host

• Jan 12, 2022

• #2

Albus2

Programmer

Sep 18, 2010

324

CH

Try a local source like the AD or DNS server or the firewall is also a common source.
The IPO needs correct time but not necessarily stratum 1.

Best is to just have one central device which get its time from a stratum 1 or 2 sources, and all internal devices will get it from this internal source.
It is not good if every single device requests time from the stratum 1/2 servers.

 

Upvote 0 Downvote

• Jan 12, 2022

• Thread starter
• #3

tac84

Programmer

Mar 15, 2019

454

AU

Thanks for the advice @Albus2. Will make some changes and give it a try.

Thanks, Tim
Adelaide, Australia

 

Upvote 0 Downvote

• Jan 19, 2022

• Thread starter
• #4

tac84

Programmer

Mar 15, 2019

454

AU

Hmm strangely, i'm still getting 3-6 alarms per day for 'Failed to resolve time server'.

If anyone else is experiencing this, let me know.

I've used time.google.com for as long as I can remember without issue. I've tried a few others and it still happens.

Some further background:

Small work from home network powered by Ubiquiti appliances. IPO R11.1 Feature Pack 2 (Latest release), small set up with 5 IP Handsets (J179s)...

First world problem I know but just curious if anyone else is having this problem at the moment.

Thanks, Tim
Adelaide, Australia

 

Upvote 0 Downvote

• Jan 19, 2022

• #5

IPGuru

Vendor

Jun 24, 2003

8,391

GB

I personaly recomend one of the NTP Pool's
such as uk.pool.ntp.org - they keep a current batch of operational NTP servers so should always be available.

Do things on the cheap & it will cost you dear

Avaya Remote Support Engineer (A.R.S.E)

 

Upvote 0 Downvote