Skip to main content
Start a Conversation

Unsolved

SkrettingMannen

1 Rookie

 • 

8 Posts

45

October 6th, 2025 12:21

Thin Clients Failing Time Sync Due to DNS Issue – No Failover Despite Multiple DNS Servers

We’re running Dell WMS Local Cloud Version 5.2 163 with multiple sites. Recently, thin clients at one site showed this error:

Time synchronization failed for failure of resolving name, please make sure time server or DNS server is configured correctly

The clients did not connect to WMS.

After troubleshooting, we found one of the DNS servers was not working. The thin clients received four DNS servers via DHCP, and the DHCP option tags were correct, but they still didn’t fail over to the next DNS server.

Environment:

  • Wyse Management Suite Local Cloud: Version 5.2 Build 163
  • ThinOS: Version 10 Build 2505_10.0076
  • DHCP provides 4 DNS servers
  • NTP server configured by hostname in WMS policy

Questions:

  1. Why does ThinOS not try the secondary DNS when the first one fails?
  2. Is this expected behavior (No failover if the first DNS is unreachable)?
  3. Any best practices for DNS/NTP configuration in multi-site WMS setups?

Workaround:
We set a static name server on the thin client to a working DNS server, and the client connected to WMS and started working immediately. However, we’d prefer to rely on DHCP-provided DNS servers for flexibility.

Has anyone else seen this? Any tips or firmware updates that improve DNS failover?

DELL-Scott H

Moderator

 • 

914 Posts

October 6th, 2025 15:56

I am afraid nobody here will be able to answer.

Please get a support case open for feedback from engineering.  

I am curious, did the primary DNS server fail entirely (meaning it did not respond to requests) or did it respond, but respond with the improper result, or a result that said it was unresolvable?    

If it failed to respond at all I would expect T10 to roll to the secondary DNS.  If it responded with no result or an incorrect result, that is hard for the OS to overcome. 

Even with the name resolution errors, and inability to contact WMS the thin client should not care, unless it was provisioning.  Once provisioned it would cache its configuration and continue to function for the end user without error, while trying WMS in the background.

SkrettingMannen

1 Rookie

 • 

8 Posts

October 24th, 2025 08:04

@DELL-Scott H​ There was some kind of DNS forwarding issue. Don't know the details, but issue is resolved by IT.

Was this post helpful?

View All

No Events found!

Top