objecttothis
DD-WRT User
Joined: 19 Nov 2014
Posts: 86
|
 Posted: Thu Jan 12, 2023 22:37 Post subject: SOLVED: DDNS update problems |
 |
Edit: Solved by changing Use SSL to Yes (https://community.cloudflare.com/t/update-ddns-ipaddress-by-using-ddclient-but-301-received-always/29570). I'll leave this up for anyone else running into it.
Running a WRT1900ACSv2 on r51011, but the same problem was happening on the WRT1900ACv1 running r51011 that I just replaced yesterday.
DDNS won't update. I thought the issue was freedns.afraid.org so since I have a domain on cloudflare, I set that up but got a similar response. I checked to make sure that I wasn't double natted (not that it would matter). I also thought that perhaps it was my Pi-hole blocking the transaction, so I whitelisted the ddns domain and the providers. When that didn't work, I just switched the dns of the router to Cloudflare (1.1.1.1). Unfortunately none of that fixes the issue, so I don't think it's the router's DNS setting.
Enable Service: freedns.afraid.org
Username: guest
Password: guest
Hostname: subdomain.domain.tld,[freedns.afraid.org key]
Use External IP Check: No
Use SSL: No
Force Update Interval: 1
Service Status:
In-a-dyn version 2.10.0 -- Dynamic DNS update client.
Startup delay: 30 sec ...
Failed resolving hostname [domain redacted],[key redacted] Name does not resolve
Update forced for alias [domain redacted],[key redacted] new IP# [IP4 redacted]
=> ERROR: Could not authenticate.
I had been meaning to switch over to cloudflare for DDNS anyway, so I tried that. I setup the API with Zone, Zone: Read and Zone, DNS: Edit Permissions then tested the API (https://alexskra.com/blog/dynamc-dnsddns-with-openwrt-and-cloudflare/)
PS C:\Users\[redacted]> curl -X GET "https://api.cloudflare.com/client/v4/user/tokens/verify" -H "Authorization: Bearer [redacted key]" -H "Content-Type:application/json"
{"result":{"id":"[redacted result id]","status":"active"},"success":true,"errors":[],"messages":[{"code":10000,"message":"This API Token is valid and active","type":null}]}
In dd-wrt
Enable Service: Cloudflare
Username: domain.tld
Password: [cloudflare provided API key]
Hostname: subdomain.domain.tld
Use External IP Check: No
Use SSL: No <-- this was the problem
Force Update Interval: 1
The response was similar:
In-a-dyn version 2.10.0 -- Dynamic DNS update client.
Startup delay: 30 sec ...
Failed resolving hostname [redacted]: Name does not resolve
Update forced for alias [redacted], new IP# [redacted]
Received status 301, don't know what that means.
Zone '[redacted]' not found.
Error response from DDNS server, exiting!
Is ddns on r51011 broken or is there something I'm doing incorrectly? freedns.afraid.org has worked fine in the past. The fact that both freedns.afraid.org and cloudflare are giving similar responses tells me something is not likely wrong with both ddns providers.
Not likely relevant, but people get pissy when you don't tell them everything:
- I have an OpenVPN server on this router.
- I'm doing some port forwarding.
- I have no firewall rules setup.
- I have a VAP for guest wireless access.
| Description: |
| cloudflare token settings |
|
| Filesize: |
92.86 KB |
| Viewed: |
698 Time(s) |
|
| Description: |
|
| Filesize: |
37.45 KB |
| Viewed: |
698 Time(s) |
|
| Description: |
| Failed resolving hostname for freedns |
|
| Filesize: |
94.65 KB |
| Viewed: |
698 Time(s) |
|
_________________
Delivering pure fact does not mean you are rude. Ignoring social contract in the delivery of pure fact does make you rude.
Last edited by objecttothis on Thu Jan 12, 2023 23:01; edited 2 times in total |
|
