The Cloudflare DDNS script experiences delays.
The Cloudflare DDNS script experiences delays.
maddixcraft
12-19-2016, 08:06 AM #1Hello! I run a Teamspeak3 server on a Raspberry Pi 3 with a dynamic IP. I want to keep things flexible without switching to static IPs. Since my domain is hosted on Hostinger, which doesn’t offer dynamic DNS, I used a Cloudflare API script to change my IP. Now the connection to the TS3 server feels much slower—sometimes I wait over 9 seconds before it connects. What can I do to improve speed?
BareBlessed
12-19-2016, 10:08 PM #2Verify the client's main and backup DNS configurations. For testing only, add a DNS record in your HOST file to determine if the problem stems from name resolution issues.
It seems the issue lies elsewhere since the way your IP was configured doesn’t matter once DNS is set up. The speed depends on the DNS server you’re using, not local caching. Even if it isn’t cached locally, it shouldn’t be excessively slow compared to regular domains. How quickly does "nslookup yourdomain" finish in the terminal?
I believe the issue lies with DDNS. Before using Cloudflare, I manually updated my IP address in the DNS Server, and it worked quickly. Now, when I run nslookup, it resolves instantly. Check the attached screenshot from a user login on ts3 while connecting to the server.
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
These indicate the correct setup. Once configured, the script remains unchanged and handles updates automatically.
This doesn’t align with how DNS works. The DDNS script simply verifies your IP, matches it with Cloudflare’s records, and sends an update request. When the A record changes, the script isn’t involved in the resolution process or timing. Make sure your SRV records are configured correctly. Check the logs for entries like:
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
These indicate the correct setup. Once configured, the script remains unchanged and handles updates automatically.
Toodaloo_246
01-14-2017, 08:20 PM #6I didn't have that SRV record with tsdns, and the UDP TS3 server record looked a little off. I made those changes, but now the connection is failing.
.
TheWoffelMaker
01-14-2017, 10:12 PM #8Yeah, TSDNS wasn't really functioning because I missed port forwarding 41144 TCP. When I attempted to boost the connection, I adjusted settings in Cloudflare, but I just didn't have the patience for DNS updates and thought I messed it up. A few hours later it worked perfectly. Fun fact, I don't even remember why I blocked the IP address since I let DNS stay uncensored .