Failed to resolve hostname when trying to connect to a server

hello.
me and some friends we were on a certain server on teamspeak..everything worked fine…

now we moved to another server…8 of us can connect…but me i cant

it says failed to resolve hostname…please help

<23:08:39> Trying to resolve hostname wildatheart.ts3v.pw
<23:08:41> Failed to resolve hostname ‘wildatheart.ts3v.pw’

thanks

The easiest way would be to check if IP/DNS you’re trying to connect is correct. Maybe you made a mistake typing.

Other way would probably be that something (probably firewall) is blocking access to that server. But first check if the address is correct.

1 Like

check the server ip adress
check all port are open in the firewall

Hi everyone,

I have a problem with my TS when trying to connect to the “elserder.ts3v.pro” I get “Failed to resolve hostname” answer. When I connect using the vpn and choosing other countries it works fine (not all the countries tho). But I want my TS to work without the vpn, is it possible?

I tried nslookup thing, didn’t help.

here’s the log:

1/8/2022 19:11:35		Info	TeamSpeak Client 3.5.6 (2020-11-25 13:53:42)	
1/8/2022 19:11:35		Info	SystemInformation: Windows 10 (19043) x64 (AMD or Intel) Binary: 64bit	
1/8/2022 19:11:35		Info	Using hardware aes	
1/8/2022 19:11:35	Direct Sound	Debug	setting timer resolution to 1ms - 	
1/8/2022 19:11:35	ClientUI	Info	OpenGL Info: LibGLES, Vendor: Google Inc., Renderer: ANGLE (Intel(R) HD Graphics 630 Direct3D11 vs_5_0 ps_5_0), Version: OpenGL ES 2.0 (ANGLE 2.1.0.57ea533f79a7)	
1/8/2022 19:11:35	Addons	Info	Checking for addon updates...	
1/8/2022 19:11:35	Plugins	Info	Loading plugin: gamepad_joystick_win64.dll	
1/8/2022 19:11:35	Gamepad Plugin	Info	Found client raw input wnd proc	
1/8/2022 19:11:35	Gamepad Plugin	Info	Cleared device list	
1/8/2022 19:11:35	Plugins	Info	Loading plugin: clientquery_plugin_win64.dll	
1/8/2022 19:11:35	Query	Info	listening on 127.0.0.1:25639	
1/8/2022 19:11:35	Plugins	Info	Loading plugin: teamspeak_control_plugin_win64.dll	
1/8/2022 19:11:35	Gamepad Plugin	Info	Found device 	
1/8/2022 19:11:35	ControlPlugin	Info	Control Plugin started, accepting connections	
1/8/2022 19:11:35	Addon	Info	Addon up to date.	
1/8/2022 19:11:35	Windows Audio Session	Devel	DeviceDeleteList::wait_for_deletes - enter - DeviceDeleteList	
1/8/2022 19:11:35	Windows Audio Session	Devel	DeviceDeleteList::wait_for_deletes - leave - DeviceDeleteList	
1/8/2022 19:11:36	Addon	Info	Addon up to date.	
1/8/2022 19:11:36	Addon	Info	Addon up to date.	
1/8/2022 19:11:36		Info	*** Time [BUILD_GUI]: 427	
1/8/2022 19:11:36		Info	*** Time [SERVERVIEW]: 452	
1/8/2022 19:11:36		Info	*** Time [SERVERVIEWMANAGER]: 474	
1/8/2022 19:11:36		Warning	failed to initialize encryption - functionality limited	
1/8/2022 19:11:36		Info	*** Time [MAINWINDOW]: 881	
1/8/2022 19:11:36		Info	*** Time [INIT]: 881	
1/8/2022 19:11:36	ClientUI	Info	Qt version: 5.12.3	
1/8/2022 19:11:36	ClientUI	Info	Using configuration location: C:\Users\Kristina\AppData\Roaming\TS3Client\settings.db	
1/8/2022 19:11:36		Info	current mytsid data is invalid - blocked to request new	
1/8/2022 19:11:36		Warning	failed to initialize encryption - functionality limited	
1/8/2022 19:11:36	SyncImpl	Error	Failed to resume syncing: not_initialized	
1/8/2022 19:11:37	ClientUI	Info	Last update check was: Sat Jan 8 18:11:36 2022	
1/8/2022 19:11:37		Info	Statistics report: User previously denied participation	
1/8/2022 19:11:37	Bookmarks	Info	Collecting autoconnect bookmarks	
1/8/2022 19:11:37	Newsticker	Info	Newsticker next check: Sun Jan 9 18:11:36 2022 GMT	
1/8/2022 19:11:49		Info	current mytsid data is invalid - blocked to request new	
1/8/2022 19:11:49		Warning	failed to initialize encryption - functionality limited	
1/8/2022 19:11:49	SyncImpl	Error	Failed to resume syncing: not_initialized	
1/8/2022 19:12:31	ClientUI	Info	Connect to server: elserder.ts3v.pro	
1/8/2022 19:12:31	ClientUI	Info	Trying to resolve elserder.ts3v.pro	
1/8/2022 19:12:31	TSDNS	Info	A/AAAA DNS resolve for possible TSDNS successful, "elserder.ts3v.pro" =(h: 51.75.46.120 p:0)	
1/8/2022 19:12:31	TSDNS	Info	A/AAAA DNS resolve for possible TSDNS successful, "ts3v.pro" =(h: 51.75.46.120 p:0)	
1/8/2022 19:12:31	TSDNS	Info	A/AAAA DNS resolve successful, "elserder.ts3v.pro" =(h: 51.75.46.120 p:0)	
1/8/2022 19:12:31	TSDNS	Info	SRV DNS resolve successful, "_tsdns._tcp.ts3v.pro" =(h: ts3v.pro p:41144)	
1/8/2022 19:12:31	TSDNS	Info	SRV DNS resolve unsuccessful, "_ts3._udp.elserder.ts3v.pro" DNS server returned answer with no data	
1/8/2022 19:12:32	TSDNS	Info	A/AAAA DNS resolve successful, "ts3v.pro" =(h: 51.75.46.120 p:0)	
1/8/2022 19:12:33	TSDNS	Info	TSDNS queried unsuccessfully 51.75.46.120:41144	
1/8/2022 19:12:33	TSDNS	Info	No TSDNS found	
1/8/2022 19:12:33	TSDNS	Info	TSDNS queried unsuccessfully 51.75.46.120:41144	
1/8/2022 19:12:33	TSDNS	Info	No TSDNS found	
1/8/2022 19:12:34	TSDNS	Info	TSDNS queried unsuccessfully 51.75.46.120:41144	
1/8/2022 19:12:34	TSDNS	Info	No TSDNS found	
1/8/2022 19:12:34	ClientUI	Info	Lookup finished: query= error=2	
1/8/2022 19:12:34	ClientUI	Info	Failed to resolve elserder.ts3v.pro

Host not found means your computer can’t resolve the IP for this address. This happens when ip has been changed and the DNS service isn’t updated yet. Sometimes it needs minutes or days :confused:

Use the IP instead the DNS address.

Please try the IP instead: 51.38.140.227:10631

1 Like

Omg, this just worked with the IP you gave me! Thank you so much, how did you do it?

Also regarding your answer, there was a short period of time few months ago when I was able to connect to this TS server without vpn (same provider, same laptop, same everything), it lasted for about a 30-40days and then it came back to the fail. I hope if I will keep using the IP you gave me it will keep working normally.

Thank you!

1 Like

You could try to set a different DNS server for your system. A guide for the Cloudflare DNS e.g. can be found here: Set up Cloudflare 1.1.1.1 resolver · Cloudflare 1.1.1.1 docs

3 Likes

Thank you, will keep it in mind as well. Although I tried using 8.8.8.8 8.8.4.4 before, did not help :frowning:

Maybe you have the wrong information stored on your computer. Try flushing your dns.

Open a command prompt as an administrator or the equivalent on your computertype “ipconfig /flushdns” without the “”

This will completely reset the DNS in your computer. Most ISPs in the world hold a cached DNS on their servers as well and the reset can take between a few hours to a week. It all depends.

1 Like

I have configured Teamspeak server on windows server. I have a client on another desktop running Windows 11. I can use IP address to connect to server okay. But cannot use the hostname of the server to connect.

I am getting the following error message: “Failed to resolve hostname ”

On the server I have all required ports configured through windows firewall.
On my DC I have DNS entries configured for the Teamspeak Server, both forward and reverse lookups as well as a SRV record.

What am I doing wrong? Why can’t I connect using a hostname instead of an IP address?

Any assistance will be greatly appreciated.

Can you try to make a nslookup up to your hostname?

2 Likes

Yes, nslookup works fine. I am able to resolve the name to an IP address.

It might be possible that a myTS nickname is running under the same name.

If that is the case the nickname would be prioritised.
You can create a myTS nickname on the myTS website and set the IP as the target.

If you need a hostname however please provide your client logs.

2 Likes

The name on the myTS website is different from the hostname on the server.

Where do I find the log file?

I do not see the following path in my client installation. %localappdata%\TeamSpeak\Logs\Default

In TS3 you can press CTRL + L to open the logs

2 Likes
Logs
2025-03-03 17:53:18 Info TeamSpeak Client 3.6.2 (2023-09-20 09:48:13)
2025-03-03 17:53:18 Info SystemInformation: Windows 11 (26100) x64 (AMD or Intel) Binary: 64bit
2025-03-03 17:53:18 Windows Audio Session Devel Hardware agc not available - Desktop Microphone (7- Microsoft® LifeCam HD-3000)
2025-03-03 17:53:18 Windows Audio Session Devel Hardware agc not available - Microphone Array (Intel® Smart Sound Technology for Digital Microphones)
2025-03-03 17:53:18 Windows Audio Session Devel Hardware agc not available - Headset Microphone (Sennheiser SDW 3 BS - US)
2025-03-03 17:53:18 SoundDevManager Debug Loading dynamic soundbackend from C:/Users/jahven/AppData/Local/Programs/TeamSpeak 3 Client/soundbackends/directsound_win64.dll
2025-03-03 17:53:18 Direct Sound Debug setting timer resolution to 1ms -
2025-03-03 17:53:18 SoundDevManager Debug Soundbackend loaded.
2025-03-03 17:53:18 Info *** Time [SPAWN_EVENTCONVERTER]: 119
2025-03-03 17:53:18 ClientUI Info OpenGL Info: LibGLES, Vendor: Google Inc., Renderer: ANGLE (Intel(R) Iris(R) Xe Graphics Direct3D11 vs_5_0 ps_5_0), Version: OpenGL ES 2.0 (ANGLE 2.1.0.57ea533f79a7)
2025-03-03 17:53:19 Info *** Time [ICONMANGER]: 132
2025-03-03 17:53:19 Addons Info Checking for addon updates…
2025-03-03 17:53:19 Plugins Info Loading plugin: teamspeak_control_plugin_win64.dll
2025-03-03 17:53:19 ControlPlugin Info Control Plugin started, accepting connections
2025-03-03 17:53:19 Windows Audio Session Devel DeviceDeleteList::wait_for_deletes - enter - DeviceDeleteList
2025-03-03 17:53:19 Windows Audio Session Devel DeviceDeleteList::wait_for_deletes - leave - DeviceDeleteList
2025-03-03 17:53:19 Addon Info Addon up to date.
2025-03-03 17:53:19 Info *** Time [BUILD_GUI]: 501
2025-03-03 17:53:19 Info *** Time [SERVERVIEW]: 548
2025-03-03 17:53:19 Info *** Time [SERVERVIEWMANAGER]: 571
2025-03-03 17:53:19 Info *** Time [MAINWINDOW]: 1243
2025-03-03 17:53:19 Info *** Time [INIT]: 1243
2025-03-03 17:53:20 ClientUI Info Qt version: 5.15.2
2025-03-03 17:53:20 ClientUI Info Using configuration location: C:\Users\joel.galloway\AppData\Roaming\TS3Client\settings.db
2025-03-03 17:53:20 ClientUI Info Last update check was: Mon Mar 3 08:58:58 2025
2025-03-03 17:53:20 Info Statistics report: User previously denied participation
2025-03-03 17:53:20 Bookmarks Info Collecting autoconnect bookmarks
2025-03-03 17:53:20 Newsticker Info Newsticker next check: Tue Mar 4 08:58:59 2025
2025-03-03 17:53:24 ClientUI Info Connect to server: *********TMSPK
2025-03-03 17:53:24 ClientUI Info Trying to resolve *********TMSPK
2025-03-03 17:53:24 TSDNS Info Trying to resolve server name: *********TMSPK
2025-03-03 17:53:25 TSDNS Info Failed to resolve server nickname: *********TMSPK
2025-03-03 17:53:25 TSDNS Info A/AAAA DNS resolve unsuccessful, *********tmspk Domain name not found
2025-03-03 17:53:25 TSDNS Info SRV DNS resolve unsuccessful, _ts3._udp.*********tmspk Domain name not found
2025-03-03 17:53:25 ClientUI Info Lookup finished: query= error=2
2025-03-03 17:53:25 ClientUI Info Failed to resolve *********TMSPK
2025-03-03 17:53:35 ClientUI Info Connect to server: 1##...*
2025-03-03 17:53:35 ClientUI Info Initiating connection: 1##...*:9987
2025-03-03 17:53:35 Windows Audio Session Devel DeviceDeleteList::wait_for_deletes - enter - DeviceDeleteList
2025-03-03 17:53:35 Windows Audio Session Devel DeviceDeleteList::wait_for_deletes - leave - DeviceDeleteList
2025-03-03 17:53:35 Windows Audio Session Debug WAS::openDevice-enter - {0.0.0.00000000}.{ddaf4a09-b27f-4f5f-84f0-6127480d2df3}
2025-03-03 17:53:35 Windows Audio Session Devel Mix Format: SRate:48000 Bitrate: 32 Channels: 2 - Headset Earphone (Sennheiser SDW 3 BS - US)
2025-03-03 17:53:35 Windows Audio Session Devel Initializing with mix format. - Headset Earphone (Sennheiser SDW 3 BS - US)
2025-03-03 17:53:35 Windows Audio Session Info Initialized with 2 channels in 32bit, 48kHz. - Headset Earphone (Sennheiser SDW 3 BS - US)
2025-03-03 17:53:35 Windows Audio Session Devel WAS Buffer size: 1056 - Headset Earphone (Sennheiser SDW 3 BS - US)
2025-03-03 17:53:35 Windows Audio Session Debug WAS::openDevice-leave - {0.0.0.00000000}.{ddaf4a09-b27f-4f5f-84f0-6127480d2df3}
2025-03-03 17:53:35 Windows Audio Session Debug WAS::startDevice-enter - {0.0.0.00000000}.{ddaf4a09-b27f-4f5f-84f0-6127480d2df3}
2025-03-03 17:53:35 Windows Audio Session Debug WAS::startDevice-leave - {0.0.0.00000000}.{ddaf4a09-b27f-4f5f-84f0-6127480d2df3}
2025-03-03 17:53:35 Windows Audio Session Devel DeviceDeleteList::wait_for_deletes - enter - DeviceDeleteList
2025-03-03 17:53:35 Windows Audio Session Devel DeviceDeleteList::wait_for_deletes - leave - DeviceDeleteList
2025-03-03 17:53:35 Windows Audio Session Debug WAS::openDevice-enter - {0.0.1.00000000}.{8edc6d11-e16d-4e5f-b1f3-75a29a8e0ff3}
2025-03-03 17:53:35 Windows Audio Session Devel Mix Format: SRate:48000 Bitrate: 32 Channels: 2 - Headset Microphone (Sennheiser SDW 3 BS - US)
2025-03-03 17:53:35 Windows Audio Session Devel Initializing with mix format. - Headset Microphone (Sennheiser SDW 3 BS - US)
2025-03-03 17:53:35 Windows Audio Session Info Initialized with 2 channels in 32bit, 48kHz. - Headset Microphone (Sennheiser SDW 3 BS - US)
2025-03-03 17:53:35 Windows Audio Session Devel WAS Buffer size: 1056 - Headset Microphone (Sennheiser SDW 3 BS - US)
2025-03-03 17:53:35 Windows Audio Session Debug WAS::openDevice-leave - {0.0.1.00000000}.{8edc6d11-e16d-4e5f-b1f3-75a29a8e0ff3}
2025-03-03 17:53:35 Windows Audio Session Debug WAS::startDevice-enter - {0.0.1.00000000}.{8edc6d11-e16d-4e5f-b1f3-75a29a8e0ff3}
2025-03-03 17:53:35 Windows Audio Session Debug WAS::startDevice-leave - {0.0.1.00000000}.{8edc6d11-e16d-4e5f-b1f3-75a29a8e0ff3}
2025-03-03 17:53:35 PktHandler Info server sent ciphers:1
2025-03-03 17:53:35 PktHandler Info Selected cipher:0
2025-03-03 17:53:35 PktHandler Devel Puzzle solve time: 3
2025-03-03 17:53:35 ClientUI Info Connect status: Connecting
2025-03-03 17:53:35 ClientUI Info Connect status: Connected
2025-03-03 17:53:35 ClientUI Info Connect status: Establishing connection
2025-03-03 17:53:35 ClientUI Info Connect status: Connection established

I am seeing a line here that refers to TSDNS.
I will configure this and see what happens.

Are you sure the hostname is correct? When there is a valid hostname it will try to open a connection like when you try it with the IP.

2 Likes

Yes, I am sure.

And confirm, this is the hostname for the Windows Server, correct?
And NOT the Teamspeak Server.

Yeah I’ve tried the hostname of the device/computer that was shown in my router dashboard.

3 Likes

Okay, I got it working!!!

1 Like