Slow DNS resolution with SRV record.

[Hoptional]

I am having a problem with the DNS resolution to my server. When using my domain name ts.DOMAIN.com, my clients always need about 3-5 seconds to connect, whereas they connect almost instantly when using the ipv4 or ipv6 address directly.

I have set up my SRV records as follows:

$ nslookup -q=SRV _ts3._udp.ts.DOMAIN.com.
Server:         192.168.178.1
Address:        192.168.178.1#53

Non-authoritative answer:
_ts3._udp.ts.DOMAIN.com      service = 0 5 9987 ts.DOMAIN.com.

Authoritative answers can be found from:

The client seems to be able to resolve the hostname, but it is slow. Here's the log (domain and ip addresses redacted):

07.12.2019 19:02:46	ClientUI	Info	Connect status: Disconnected	
07.12.2019 19:02:46	ClientUI	Info	Disconnected or forced to leave, want autoreconnect = 0	
07.12.2019 19:02:49	ClientUI	Info	Connect to server: ts.DOMAIN.com	
07.12.2019 19:02:49	ClientUI	Info	Trying to resolve ts.DOMAIN.com	
07.12.2019 19:02:51	TSDNS	Info	SRV DNS resolve successful, "_ts3._udp.ts.DOMAIN.com" =(h: ts.DOMAIN.com p:9987)	
07.12.2019 19:02:51	TSDNS	Info	A/AAAA DNS resolve for possible TSDNS successful, "DOMAIN.com" =(h: IPV6 p:0), (h: IPV4 p:0)	
07.12.2019 19:02:51	TSDNS	Info	A/AAAA DNS resolve for possible TSDNS successful, "ts.DOMAIN.com" =(h: IPV6 p:0), (h: IPV4 p:0)	
07.12.2019 19:02:51	TSDNS	Info	A/AAAA DNS resolve successful, "ts.DOMAIN.com" =(h: IPV6 p:0), (h: IPV4 p:0)	
07.12.2019 19:02:51	TSDNS	Info	SRV DNS resolve unsuccessful, "_tsdns._tcp.DOMAIN.com" Domain name not found	
07.12.2019 19:02:52	TSDNS	Info	A/AAAA DNS resolve successful, "ts.DOMAIN.com" =(h: IPV6 p:0), (h: IPV4 p:0)	
07.12.2019 19:02:52	ClientUI	Info	Lookup finished: ip=IPV6 port=9987 query=ts.DOMAIN.com error=0	
07.12.2019 19:02:52	ClientUI	Info	Resolve successful: [IPV6]:9987IPV4:9987	
07.12.2019 19:02:52	ClientUI	Info	Initiating connection: [IPV6]:9987	
07.12.2019 19:02:52	ClientUI	Info	Connect status: Connecting	
07.12.2019 19:02:52	PktHandler	Devel	Puzzle solve time: 4	
07.12.2019 19:02:52	ClientUI	Info	Connect status: Connected	
07.12.2019 19:02:52	ClientUI	Info	Connect status: Establishing connection	
07.12.2019 19:02:52	ClientUI	Info	Connect status: Connection established	
07.12.2019 19:02:53	UIHelpers	Info	setClientVolumeModifier: 8 -3	
07.12.2019 19:02:53	UIHelpers	Info	setClientVolumeModifier: 5 -8	
07.12.2019 19:02:53	UIHelpers	Info	setClientVolumeModifier: 6 0	
07.12.2019 19:02:53	TSDNS	Info	TSDNS queried unsuccessfully IPV6:41144	
07.12.2019 19:02:53	TSDNS	Info	TSDNS queried unsuccessfully IPV6:41144	
07.12.2019 19:02:55	TSDNS	Info	TSDNS queried unsuccessfully IPV4:41144	
07.12.2019 19:02:55	TSDNS	Info	No TSDNS found	
07.12.2019 19:02:55	TSDNS	Info	TSDNS queried unsuccessfully IPV4:41144	
07.12.2019 19:02:55	TSDNS	Info	No TSDNS found

Does anyone have an idea why it could be so slow?

[bialy]

Did you add tsdns srv record as well?

SRV DNS resolve unsuccessful, "_tsdns._tcp.DOMAIN.com" Domain name not found

It looks like in the domain settings tsdns record appear, but either is wrong or tsdns server is not runnning. Maybe try to remove tsdns srv record and chech again after domain refresh on dns servers.

[Hoptional]

Thanks for the reply!

I do not have the tsdns record set on my domain and I do not have a tsdns server running. I don't understand why the client is even trying to look that up after it has successfully resolved the _ts3 record, but the delay does indeed seem to come from that.

[bialy]

It's strange. Is your domain is top level domain? ie. "domain.com"?
What is important - Teamspeak is looking for ts3_udp and tsdns record only there.
For example: if you have domain name like "ts.subdomain.domain.com" than ts3 is only looking for tsdns for "domain.com"

What is more important: ts3_udp is intended to be used if you willing to use your domain name for website and TS3 at the same time.
Example: website "domain.com" and teamspeak on another server (IP) also available via "domain.com"
In such scenario, you shouldn't use ts3.domain.com to connect to teamspeak server.

Try to connect via "domain.com" and check if dealy still exist. If yes, and you not afraid, you can PM me your real domain name, maybe I can advise.
If you willing to use "ts.domain.com" anyway, just remove SRV records. You don't need them.

[Hoptional]

I moved my domain to cloudflare this week and the issue seems to be resolved now. Not sure what was wrong with the old nameserver. The domain is indeed ts.domain.com. I don't know if it connected faster via domain.com, as I have never tried that.

Thank you for the help!