Cloudflare DDNS script is slow.

[m1hN_]

Hello guys! I host a Teamspeak3 server on a Raspberry Pi 3. I have dynamic IP and I dont want to move to static and I bought the domain and managed it on Hostinger which doesnt provide a dynamic dns service. I searched it up and used the cloudflare API script to update my IP address. After I setup it the connection to the TS3 server is much much slower than directly introducing the IP, e.g. I am waiting at least 9 seconds for the connection to be made. What can I do for it to be faster?

[StDragon]

Check your client's primary and secondary DNS settings. As a temporary measure for testing purposes only, place a DNS entry in your HOST file to see if that isolate's the issue to being a name resolution problem.

[Alex Atkin UK]

13 hours ago, m1hN_ said:

Hello guys! I host a Teamspeak3 server on a Raspberry Pi 3. I have dynamic IP and I dont want to move to static and I bought the domain and managed it on Hostinger which doesnt provide a dynamic dns service. I searched it up and used the cloudflare API script to update my IP address. After I setup it the connection to the TS3 server is much much slower than directly introducing the IP, e.g. I am waiting at least 9 seconds for the connection to be made. What can I do for it to be faster?

I'd suggest the problem is something else, as once your IP has been set on DNS how it was set is irrelevant, its entirely down to how fast the DNS lookup occurs and that will vary based on what DNS server is being used to resolve it.

 

Even as it likely wont be cached on a local server it wont be as fast as mainstream domains, but it certainly shouldn't be THAT slow.  How quickly does "nslookup yourdomain" resolve from the console?

[m1hN_]

1 hour ago, Alex Atkin UK said:

I'd suggest the problem is something else, as once your IP has been set on DNS how it was set is irrelevant, its entirely down to how fast the DNS lookup occurs and that will vary based on what DNS server is being used to resolve it.

 

Even as it likely wont be cached on a local server it wont be as fast as mainstream domains, but it certainly shouldn't be THAT slow.  How quickly does "nslookup yourdomain" resolve from the console?

Im thinking that the problem is the DDNS because before I started using Cloudflare I would manually update my IP in DNS Server and it was connecting fast. When I try nslookup it instantly resolve it. 

Look at the attach, I am not really into networking and I dont really understand what is the problem here. The screenshot is from a user log in ts3 when connecting to the server.

 

[Jarsky]

39 minutes ago, m1hN_ said:

Im thinking that the problem is the DDNS because before I started using Cloudflare I would manually update my IP in DNS Server and it was connecting fast. When I try nslookup it instantly resolve it. 

 

This doesn't make sense. The DDNS Script has absolutely nothing to do with the speed of your DNS resolution.

All the script is doing is checking your current IP address, comparing it to the existing DNS record in Cloudflare, and using the API to submit an update request. 

After the A record has been changed, the DDNS script has absolutely nothing to do with your DNS resolution, let alone the time to resolve. 

 

Have you setup your SRV records properly? It looks like there is an issue lokoing at those logs in the screenshot. 

 

You should have entries something like this:

SRV _ts3._udp.ts.utlr.xyz 0 5 9987 ts.utlr.xyz 3600

SRV _tsdns._tcp.ts.utlr.xyz 0 5 9988 ts.utlr.xyz 3600

 

 

Broken down that is:
Record Type: SRV

Service: _ts3 / _tsdns

Protocol: _udp / _tcp

Priority: 0

Weight: 5

Port: 9987 / custom port for tsdns

Target domain: ts.utlr.xyz

TTL: Default is 30minutes...3600s is 1hr

 

So in Cloudflare, creating your SRV's should look like this.

Once setup they don't need to be touched. Your Cloudflare DDNS script will keep the A record updated. 

 

 

[m1hN_]

6 hours ago, Jarsky said:

 

This doesn't make sense. The DDNS Script has absolutely nothing to do with the speed of your DNS resolution.

All the script is doing is checking your current IP address, comparing it to the existing DNS record in Cloudflare, and using the API to submit an update request. 

After the A record has been changed, the DDNS script has absolutely nothing to do with your DNS resolution, let alone the time to resolve. 

 

Have you setup your SRV records properly? It looks like there is an issue lokoing at those logs in the screenshot. 

 

You should have entries something like this:

SRV _ts3._udp.ts.utlr.xyz 0 5 9987 ts.utlr.xyz 3600

SRV _tsdns._tcp.ts.utlr.xyz 0 5 9988 ts.utlr.xyz 3600

 

 

Broken down that is:
Record Type: SRV

Service: _ts3 / _tsdns

Protocol: _udp / _tcp

Priority: 0

Weight: 5

Port: 9987 / custom port for tsdns

Target domain: ts.utlr.xyz

TTL: Default is 30minutes...3600s is 1hr

 

So in Cloudflare, creating your SRV's should look like this.

Once setup they don't need to be touched. Your Cloudflare DDNS script will keep the A record updated. 

 

 

I didnt had that SRV Record with tsdns and the udp ts3 srv record was a bit different. I did that and now is failing connecting. 

[Jarsky]

On 6/14/2023 at 3:25 PM, m1hN_ said:

I didnt had that SRV Record with tsdns and the udp ts3 srv record was a bit different. I did that and now is failing connecting. 

 

 

turns out the tsdns port is 41144, which you can set in your screenshot above

_tsdns._tcp.utlr.xyz. 86400 IN SRV 0 5 41144 ts.utlr.xyz.

 

But youve got it working? I just ran a quick test and it connected just fine. 

[m1hN_]

3 hours ago, Jarsky said:

 

turns out the tsdns port is 41144, which you can set in your screenshot above

_tsdns._tcp.utlr.xyz. 86400 IN SRV 0 5 41144 ts.utlr.xyz.

 

But youve got it working? I just ran a quick test and it connected just fine. 

Yeah, TSDNS wasnt really working because I forgot to port forward 41144 TCP..When I tried to speed up the connection I changed the settings in Cloudflare, but I didnt have enough patience for the DNS to propagate and tought I fucked it up. Several hours later it was working fine. Fun fact, i dont even know why I censored the IP adress since I let the DNS uncensored :).

[Alex Atkin UK]

13 hours ago, m1hN_ said:

Yeah, TSDNS wasnt really working because I forgot to port forward 41144 TCP..When I tried to speed up the connection I changed the settings in Cloudflare, but I didnt have enough patience for the DNS to propagate and tought I fucked it up. Several hours later it was working fine. Fun fact, i dont even know why I censored the IP adress since I let the DNS uncensored :).

Yeah I tend to not have that problem as my router uses Cloudflare for DNS, I just check over 5G later to make sure everything works.