Timeout when querying tplinkdns.com domains
See below:
$ time host elilla.tplinkdns.com
elilla.tplinkdns.com has address 94.220.93.30
;; connection timed out; no servers could be reached
;; connection timed out; no servers could be reached
0.01user 0.01system 0:22.56elapsed 0%CPU (0avgtext+0avgdata 12372maxresident)k
0inputs+0outputs (0major+787minor)pagefaults 0swaps
This delay generates problems when e.g. trying to use certbot to create a certificate:
Failed authorization procedure. elillla.tplinkdns.com (http-01): urn:ietf:params:acme:error:dns :: DNS problem: query timed out looking up A for elilla.tplinkdns.com
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
Hello,
You may try to change the WAN DNS server on your C7 to 8.8.8.8 and 8.8.4.4 to give it a shot.
BTW, are you still able to remotely access the server via the WAN IP address? Please ensure the DDNS service is still enabled.
Last but not least, please ensure the firmware of your C7 is up-to-date.
Good day.
- Copy Link
- Report Inappropriate Content
Hello,
You may try to change the WAN DNS server on your C7 to 8.8.8.8 and 8.8.4.4 to give it a shot.
BTW, are you still able to remotely access the server via the WAN IP address? Please ensure the DDNS service is still enabled.
Last but not least, please ensure the firmware of your C7 is up-to-date.
Good day.
- Copy Link
- Report Inappropriate Content
My DNS servers are already Google’s. I can update my .tplinkdns.com hostname just fine. It updates, pings, and it’s accessible, by IP or by DNS.
I’m not reporting an issue with my network or my router. I’m reporting an issue with tplinkdns.com. It doesn’t happen just on my computer. It happens on any server I tried, including in other countries. You can test it yourself with host(1) on your machine.
It might be related to the absence of SOA and NS records in tplinkdns.com:
$ dig -t NS tplinkdns.com
; <<>> DiG 9.11.5-P4-5.1+deb10u1-Debian <<>> -t NS tplinkdns.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 62745
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 512
;; QUESTION SECTION:
;tplinkdns.com. IN NS
;; Query time: 1003 msec
;; SERVER: 8.8.8.8#53(8.8.8.8)
;; WHEN: Mi Aug 19 11:19:07 CEST 2020
;; MSG SIZE rcvd: 42
# same results for SOA
Or it might be unrelated to that. In any case, from any network I try, it resolves the host but has a delay, and gets SERVFAIL errors.
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
@Diver15 I could not solve it, sorry.
I am pretty sure by now that the issue is that the root domain for tplinkdns.com doesn't have the mandatory NS and SOA records. I've contacted tplink over this, but they didn't want to act on it. In the end I just used another DNS provider.
- Copy Link
- Report Inappropriate Content
Hi,
I can confirm this issue. Tp-Link should not offer DDNS service if it useless in the current state. It is just really unprofessional.
- Copy Link
- Report Inappropriate Content
Information
Helpful: 0
Views: 2689
Replies: 5
Voters 0
No one has voted for it yet.