IPv6 not resolving

[florian2833z]

Hello,

If I connect my windows to a vpn server via ipv4, windows thinks that there is no ipv6 connection

(I guess) TeamSpeak somehow checks the ipv6 connectivity by looking at what windows says -> TeamSpeak thinks there is no working ipv6 connection. Because of that, teamspeak refuses to look up AAAA-Records of domains

I need to manually enter the ipv6 address to connect to a server that actually has a working domain


Please implement other checks to see if IPv6 works instead of looking at what windows says. Windows is buggy regarding this and should not be considered as reliable source of information.

My proposal:
Prefer IPv6, no matter what windows says and if it doesnt work, use ipv4 OR TRY ipv6 if the domain has no A-Record although windows says ipv6 is not operational.

[florian2833z]

Why was this moved to client support? It is clearly a bug.

[dante696]

Can you offer us a client log?

Why was this moved to client support? It is clearly a bug.

Not everything that user expect to work but result differs is automatically a bug.

[florian2833z]

This is what teamspeak says. Don't worry about the date. I was too lazy to create a thread back then, but it is the same problem.

[numma_cway]

I hereby certify this as a bug.

[florian2833z]

@dante696 can you forward this to the devs?

[Chris]

1/23/2019 12:15:20	ClientUI	Info	Connect to server: florian2833z.de	
1/23/2019 12:15:20	ClientUI	Info	Trying to resolve florian2833z.de	
1/23/2019 12:15:20	TSDNS	Info	A/AAAA DNS resolve for possible TSDNS successful, "florian2833z.de" =(h: 2a03:4000:29:1f1::1 p:0)	
1/23/2019 12:15:20	TSDNS	Info	A/AAAA DNS resolve successful, "florian2833z.de" =(h: 2a03:4000:29:1f1::1 p:0)	
1/23/2019 12:15:20	TSDNS	Info	SRV DNS resolve unsuccessful, "_tsdns._tcp.florian2833z.de" Domain name not found	
1/23/2019 12:15:20	TSDNS	Info	SRV DNS resolve unsuccessful, "_ts3._udp.florian2833z.de" Domain name not found	
1/23/2019 12:15:22	TSDNS	Info	TSDNS queried unsuccessfully 2a03:4000:29:1f1::1:41144	
1/23/2019 12:15:22	TSDNS	Info	No TSDNS found	
1/23/2019 12:15:22	ClientUI	Info	Lookup finished: ip=2a03:4000:29:1f1::1 port=9987 query=florian2833z.de error=0	
1/23/2019 12:15:22	ClientUI	Info	Resolve successful: [2a03:4000:29:1f1::1]:9987	
1/23/2019 12:15:22	ClientUI	Info	Initiating connection: [2a03:4000:29:1f1::1]:9987

resolves just fine when connected to an IPv4 VPN since the domain seems to be IPv6 only.

Are DNS lookups working for you using nslookup, without explicitly specifying the DNS server to use? Maybe the DNS server you're using only checks for IPv4 addresses on the domain.

[dante696]

We re-re-checked this and yes you are right.
We use our own check and in this check we only ask A/AAAA for the detected network and do not ask for both protocols in that case.

I create a ticket for this.
Edit
Moved ticket to new location. (Not directly a bug. More an important improvement).

[florian2833z]

We re-re-checked this and yes you are right.
Moved ticket to new location. (Not directly a bug. More an important improvement).

Nice to hear, thank you.

[florian2833z]

When will this be changed?

[florian2833z]

Any updates ??

[dante696]

At this moment nobody can promise any date or client version for this.