Network error when attempting to use dynamic DNS
If I am attempting to configure DDNS and enter my hostname of xyz.synology.me (not my actual hostname, just putting xyz to anonymize it), I get the attached error.
How can I resolve this?
In another nextdns profile I use, I have been able to do this same thing without issue, with another synology.me DDNS hostname. So it's just happening in one of my profiles.
17 replies
-
The issue has been fixed. Thanks for the heads up.
-
I have the same problem with one profile but not the others. I double checked my domain name, I even used the x.x.x.x.nip.io resolver and I still get an HTTP 500 error with this response body :
{"errors":[{"code":"internalServerError "}]} -
You can check to see if it's working, do you get as answer your IP?
Replace YourID (the one from setup) and YourDDNS (xyz.synology.me) with yours
-
yes, here's a screenshot. The IP it reports back is accurate and current.
-
In previous cases it was human error, now it is a problem on NextDNS end. I tried again to add the same working DDNS on another configuration and it gives me the same error.
-
thanks for your help, I appreciate it
-
-
Same error, any update to fix this?
-
I am experiencing the same issue.
-
Are we reporting this in the right place? Seems like it has been several days and still not resolved?
-
I'm having the same issue, have tried with multiple domains and still getting the exact same error.
-
Same problem here.
-
Same problem here, I have been 'pulling my hair out' trying to sort it out. No matter what I do, I get the same network error as shown in the 1st post.
-
Works now
-
Yep. Confirmed, works for me too.
-
It works!
Content aside
- Status Fixed
-
3
Votes
- 1 yr agoLast active
- 17Replies
- 731Views
-
7
Following