[Server]Teamspeak accounting ip is hard-coded

[ehthe]

Just a word of caution . Don't just redirect the domain name to localhost ! You should also blackhole the ip.
dig of the domain :

accounting.teamspeak.com -> 128.65.210.118

hardcoded string :

ddlocpimbkicgmpoggncecmgldde -> 128.65.210.118

 

[Supervisor]

Can you give a further explanation please? I have my firewall enabled on the ports anyway, but why isn't it enough to redirect?

 

[ehthe]

If you just redirect the domain name, the server won't be able to resolve the ip behind the domain name. But, as you can see the ip of the domain name is hard-coded, so in theory the server could access it anyway.

 

[Asphyxia]

What ehthe is saying is that:
The TeamSpeak server is not only trying to connect to accounting.teamspeak.com, but it could also make an attempt to directly connect to the TeamSpeak 3 accounting server via IP address, which is 128.65.210.118. I think that this would only happen if the domain were to not resolve, perhaps this was put in place in case of DNS issues, but as long as accounting.teamspeak.com resolves, it should NOT try connecting to 128.65.210.118. It is still a good idea to blacklist the IP address 128.65.210.118 or modify the server binary to break that IP address (if possible).

 

[p0tassium]

hmm

 

[Asphyxia]

I think they refuse connections which aren't encoded and sent on the right port(s).