People can not go to the server
- Thread starter SashaHard
- Start date
FaintpanTV
Member
- Apr 20, 2016
- 2
- 0
- 33
If you have a port for your Teampseak 3 server it won't work with just an A record, the SRV record makes the port configured (tested with my own website), I have vpn's and stuff so if you need me to fix it or even try to remotely connect to your server (join with the vpns' of Ukraine, Belarus, Russia) just message me. Personally I have not faced this problem because with my vps I disabled my Firewall and enabled every port (I know I'm an idiot for doing this, but I'm too lazy to do each individual port)
Last edited:
- Thread starter
- #5
Yes, and А record do not work!
What should be done to work A record?
A record points to Teamspeak IP (WITHOUT port) and srv will specify port
- Thread starter
- #7
Understood nothing (
Make the A record point to Teamspeak server Ip but without port. And then create an SRV record with the Teamspeak server port
FaintpanTV
Member
- Apr 20, 2016
- 2
- 0
- 33
When all the information is said in my post but yet you still don't understand? This is why a adverage person can't use a computer/network or anything else alike. Not to hate but I can't help you sorry.
- Thread starter
- #10
That's exactly what I did)
I'm not sure about you guys but the latest client versions broke the ability to connect to my TS SRV records so I had to fall back to using A records for now.
@OP A records should work fine making sure to specify the port at the end if its different from the default. Allowing 24hrs for DNS to refresh is also good practise.
@OP A records should work fine making sure to specify the port at the end if its different from the default. Allowing 24hrs for DNS to refresh is also good practise.
I can still connect in latest version to my SRV records
Hope I'm not hijacking by responding here, happy to open a new thread if I am but could be relevant.. I've changed the real domain and IPs for my peace of mind but as you can see it clearly resolves and finds the IP and port of the server but instead of going through with the connection it rejects the clients unlike the previous versions. Happens on latest version on Windows and iOS. Previous versions on both operating systems would connect without any issues. Any ideas?
23/01/2017 09:38:17 ClientUI Info Trying to resolve ts.domain.net
23/01/2017 09:38:17 TSDNS Info A/AAAA DNS resolve for possible TSDNS successful, "domain.net" =(h: 100.100.100.100 p:0)
23/01/2017 09:38:17 TSDNS Info SRV DNS resolve unsuccessful, "_tsdns._tcp.domain.net" Domain name not found
23/01/2017 09:38:17 TSDNS Info SRV DNS resolve successful, "_ts3._udp.ts.domain.net" =(h: 100.100.100.100 p:9987)
23/01/2017 09:38:17 TSDNS Info A/AAAA DNS resolve unsuccessful, "100.100.100.100" Domain name not found
23/01/2017 09:38:17 ClientUI Info Lookup finished: query= wasTSDNS=0 error=2
23/01/2017 09:38:17 ClientUI Info Failed to resolve ts.domain.net
23/01/2017 09:38:17 TSDNS Info A/AAAA DNS resolve unsuccessful, "ts.domain.net" Domain name not found
23/01/2017 09:38:17 TSDNS Info A/AAAA DNS resolve unsuccessful, "ts.domain.net" Domain name not found
23/01/2017 09:38:18 TSDNS Info TSDNS queried unsuccessfully 100.100.100.100:41144
23/01/2017 09:38:18 TSDNS Info No TSDNS found
