Setting Up Dynamic DNS For Your Domain

sandy

Administrator
Staff member
you only have a DYN record for the wildcard *.mywebservice.it
You would need to add another where the host is the @ sign to denote the root domain of mywebservice.it
 

wwinter2

New Member
Already done, I deleted the record with @ for myservice.it days ago because it did not work! I try again and see what happens ...
Thank you
 

wwinter2

New Member
I modified zonedit ddns with @ mywebservice.it but it does not work.
I also modified the ddns command of Cisco to update the mysebservice.it domain
Before it was configured like this:
zoneedit method -
add http: // wwinter2: Authentication Token@dynamic.zoneedit.com/auth/dynamic.html?host= <h> & dnsto = <a>
Dialer -
ip ddns update hostname * .mywebservice.it
ip ddns update zoneedit
and only * .mywebservice.it worked, not i can ping domain...

changing the dialer to:
ip ddns update hostname mywebservice.it (without asterisk)
only the domain works but I can not ping the hosts
 

kenwiens

New Member
Hi

My domain wiensville.com is registered with easydns. I am trying to use your free dynamic dns to point this to my home router. I was using dynamic dns through dyndns for the last few years, but have now cancelled that service.


To my (confused) view, I have tried to set this up at zoneedit. On the dns information screen (zone panel: dynamic records) it reports that home.wiensville.com has an IP. I have confirmed that this IP is correct (so I assume that the client on my asus router is properly communicating with you). However, attempts to ping home.wiensville.com fail (although attempts to ping the IP address directly do work). I set this up over 48 hours ago so I don't think that propogation should be the issue. What have I missed?

Also, would things be easier if I transferred the domain registration to you (or does that not matter as you and easydns appear to be associated companies?)

I also tried to set up www. wiensville. com but it shows as offline.



thanks,
Ken
 

rberber

New Member
Hi

My domain wiensville.com is registered with easydns. I am trying to use your free dynamic dns to point this to my home router. I was using dynamic dns through dyndns for the last few years, but have now cancelled that service.


To my (confused) view, I have tried to set this up at zoneedit. On the dns information screen (zone panel: dynamic records) it reports that home.wiensville.com has an IP. I have confirmed that this IP is correct (so I assume that the client on my asus router is properly communicating with you). However, attempts to ping home.wiensville.com fail (although attempts to ping the IP address directly do work). I set this up over 48 hours ago so I don't think that propogation should be the issue. What have I missed?

Also, would things be easier if I transferred the domain registration to you (or does that not matter as you and easydns appear to be associated companies?)

  1. Your domain (and hosts) are not visible right now. No idea about what are you seeing in your control panel.
  2. Assuming you followed the instructions on the first message (video) or help article, you should have no A records, and your DYN records (could be one, or more) would show the current IP (WAN) address; perhaps that is what you refer.
  3. ZoneEdit uses its own way to manage information, in your case, from your router. Its different that dyndns.
  4. Yes ZoneEdit and EasyDNS are the same for practical purposes.
For reference this is what I see trying to resolve your domain:
Code:
$ host -vr wiensville.com
Trying "wiensville.com"
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 37676
;; flags: qr ra; QUERY: 1, ANSWER: 0, AUTHORITY: 4, ADDITIONAL: 4

;; QUESTION SECTION:
;wiensville.com.                        IN      A

;; AUTHORITY SECTION:
wiensville.com.         85272   IN      NS      ns3134.dns.dyn.com.
wiensville.com.         85272   IN      NS      ns4155.dns.dyn.com.
wiensville.com.         85272   IN      NS      ns1186.dns.dyn.com.
wiensville.com.         85272   IN      NS      ns2134.dns.dyn.com.

;; ADDITIONAL SECTION:
ns1186.dns.dyn.com.     85272   IN      A       208.76.58.186
ns2134.dns.dyn.com.     85272   IN      A       208.76.59.134
ns3134.dns.dyn.com.     85272   IN      A       208.76.60.134
ns4155.dns.dyn.com.     85272   IN      A       208.76.61.155

Received 188 bytes from 192.168.10.4#53 in 1 ms
Trying "wiensville.com"
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 31801
;; flags: qr ra; QUERY: 1, ANSWER: 0, AUTHORITY: 4, ADDITIONAL: 4

;; QUESTION SECTION:
;wiensville.com.                        IN      AAAA

;; AUTHORITY SECTION:
wiensville.com.         85272   IN      NS      ns3134.dns.dyn.com.
wiensville.com.         85272   IN      NS      ns4155.dns.dyn.com.
wiensville.com.         85272   IN      NS      ns1186.dns.dyn.com.
wiensville.com.         85272   IN      NS      ns2134.dns.dyn.com.

;; ADDITIONAL SECTION:
ns1186.dns.dyn.com.     85272   IN      A       208.76.58.186
ns2134.dns.dyn.com.     85272   IN      A       208.76.59.134
ns3134.dns.dyn.com.     85272   IN      A       208.76.60.134
ns4155.dns.dyn.com.     85272   IN      A       208.76.61.155

Received 188 bytes from 192.168.10.4#53 in 2 ms
Trying "wiensville.com"
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 52801
;; flags: qr ra; QUERY: 1, ANSWER: 0, AUTHORITY: 4, ADDITIONAL: 4

;; QUESTION SECTION:
;wiensville.com.                        IN      MX

;; AUTHORITY SECTION:
wiensville.com.         85272   IN      NS      ns1186.dns.dyn.com.
wiensville.com.         85272   IN      NS      ns4155.dns.dyn.com.
wiensville.com.         85272   IN      NS      ns2134.dns.dyn.com.
wiensville.com.         85272   IN      NS      ns3134.dns.dyn.com.

;; ADDITIONAL SECTION:
ns1186.dns.dyn.com.     85272   IN      A       208.76.58.186
ns2134.dns.dyn.com.     85272   IN      A       208.76.59.134
ns3134.dns.dyn.com.     85272   IN      A       208.76.60.134
ns4155.dns.dyn.com.     85272   IN      A       208.76.61.155

Received 188 bytes from 192.168.10.4#53 in 1 ms

Which means the query goes to the wrong place: dynDNS, and their servers give no answer about your domain.

Reference: Changes to Dynamic DNS
 

Chris Cherry

Zoneedit Support
Hi Ken,


rberber is correct. Your domain is delegated to DYNDNS' nameservers still:

Domain Name: WIENSVILLE.COM
Registry Domain ID: 88164141_DOMAIN_COM-VRSN
Registrar WHOIS Server: whois.easydns.com
Registrar URL: http://www.easydns.com
Updated Date: 2019-06-20T12:19:32Z
Creation Date: 2002-07-05T23:31:39Z
Registry Expiry Date: 2020-07-05T23:37:11Z
Registrar: easyDNS Technologies Inc.
Registrar IANA ID: 469
Registrar Abuse Contact Email:
Registrar Abuse Contact Phone:
Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
Domain Status: clientUpdateProhibited https://icann.org/epp#clientUpdateProhibited
Name Server: NS1186.DNS.DYN.COM
Name Server: NS2134.DNS.DYN.COM
Name Server: NS3134.DNS.DYN.COM
Name Server: NS4155.DNS.DYN.COM
DNSSEC: unsigned
URL of the ICANN Whois Inaccuracy Complaint Form: https://www.icann.org/wicf/
>>> Last update of whois database: 2020-02-06T20:07:33Z <<<


Anything you set up in the Zoneedit zone for wiensville.com is not seen until you log into your EasyDNS account and change the Nameservers to dns1.zoneedit.com and dns2.zoneedit.com (and let them propagate)

Instructions can be found here:




To avoid confusion, it might be a good idea to transfer the registration from EasyDNS to Zoneedit. However, you will lose phone support and will need to rely on Email support (as you'll be a premium Zoneedit member). You won't need to use the forums as other Free users do.

If you need help with transferring, contact us via your EasyDNS account via our Easy-Does.It contact form.
The Easy-Does.it contact form can be found as a sub-menu selection under the "HELP" menu at the top blue bar of your control panel, OR just next to the Logout button at the top right corner.
 

kenwiens

New Member
Thank you to both of you for the assistance. This is what happens when you set up dynamic dns and then don;'t touch it for 8-10 years - you forget things like changing the name servers at the registrar.

Once again - all is working now, thank you for the advice!!
 

randalthor

New Member
Not really sure what I'm doing. I'm just trying to do ddns, for a subdomain, nothing more. Can I do that here?
Site is...
Subdomain is .... pointing to an IP.

I've got the IP update part working according to zoneedit, but ... doenst ever resolve to an IP.

Edit: site removed
User name is same as forum username.
 
Last edited:

sandy

Administrator
Staff member
the domain is delegated to at its registrar:
Name Server: NS1.SERVER-CPANEL.COM
Name Server: NS2.SERVER-CPANEL.COM and not to:

dns1.zoneedit.com.
dns.zoneedit.com.

as such the zoneedit zone file is not publicly available.

regards
 

inspector71

New Member
Hello

Router profiles are limited to no-ip and DynDNS. No manual option. Fark you TP-Link!

Would rather stick with zoneedit but cannot run a client on the router either.

However, the following little BASH script works fine retreiving the WAN IP when run on a box inside the network (not the router):

Bash:
user@host:~# cat getwanip.bash
#!/usr/bin/bash

ipify=https://api.ipify.org/

WANIP=`curl --silent --url ${ipify} --connect-timeout 10`

echo ${WANIP}
user@host:~# ./getwanip.bash
121.XX.255.YYY

So all I need is to get the zoneedit update going.

After investigating the JavaScript client source code, it seems like a URL-based interface (API?) should work. But what is the syntax? The following seems to work, except I get no further than Failed login.

https://pd4:<token>@dynamic.zoneedit.com/dyn/jsclient.php?rsp_ident=zoneedit&hostname=<my.domain.name>&password=<token>&username=pd4

Also tried just this:

https://dynamic.zoneedit.com/dyn/jsclient.php?rsp_ident=zoneedit&hostname=<my.domain.name>&password=<token>&username=pd4

XML:
<ERROR CODE="708" TEXT="Failed Login: pd4" ZONE="<my.domain.name>">

I also tried HTTP Basic Auth. No luck.

Anyone have any suggestions?

Thanks
 
Last edited:

Chris Cherry

Zoneedit Support
Try this:

https://<username>:<dynamic auth token>@api.cp.zoneedit.com/dyn/generic.php?hostname=yourdomain.com&myip=1.1.1.1
 

inspector71

New Member
Try this:

https://<username>:<dynamic auth token>@api.cp.zoneedit.com/dyn/generic.php?hostname=yourdomain.com&myip=1.1.1.1
Thanks Chris, that did the trick!

(Retro update)

So, my functioning script is now:

Bash:
#!/usr/bin/bash

ipify=https://api.ipify.org/

WANIP=`curl --silent --url ${ipify} --connect-timeout 10`

zoneedit=`curl --connect-timeout 10 --silent --url https://<username>:<token>@api.cp.zoneedit.com/dyn/generic.php?hostname<my.domain.name>&myip=${WANIP}`

(/Retro update)

Do you think there might be a better way to document some of these settings? At least, I am not sure I could find the script name and variables no matter how hard I tried to filter the web.
 
Last edited:

Jeremy

New Member
Any ideas what the query URL would look like on a Synology NAS? Their DSM software used to have build in DDNS support for ZoneEdit, but they removed it. I have an older Synology NAS that's still running the older software and it still updates ZoneEdit successfully. However, I'm trying to add it manually on a newer system, and can't get it to work. I've tried all the other URL's listed in this thread, and none are working for me. For example, this is how I have the latest one above from Chris configured, using Synology's variables w/ my values entered in the provided fields (auth token for password):

Code:
https://__USERNAME__:__PASSWORD__@api.cp.zoneedit.com/dyn/generic.php?hostname=__HOSTNAME__&myip=__MYIP__
 

Jeremy

New Member
Just to follow up, Synology apparently didn't like the user/pass before the domain. When I used that format, the request would just hang. I moved those into query parameters, like below, and it did successfully update Zoneedit, although it still registers as an error on Synology...

Code:
https://api.cp.zoneedit.com/dyn/generic.php?username=__USERNAME__&password=__PASSWORD__&hostname=__HOSTNAME__&myip=__MYIP__

Code:
2021-12-02T21:41:40-06:00 boneplex ddnsd[7165]: ddnsd.c:267 DDNS hostname update error: <SUCCESS CODE="200" TEXT="<REDACTED> updated to <REDACTED>" ZONE="<REDACTED>">
2021-12-02T21:41:40-06:00 boneplex ddnsd[7165]: ddnsd.c:1938 Fail to update [<REDACTED>] with IP [<REDACTED>] at [USER_Zoneedit]
 
Last edited:

Chris Cherry

Zoneedit Support
Thanks for the update/info, Jeremy. It's good to have that here in case other Synology users run across this thread. Unfortunately, we're no experts regarding 3rd party routers or software and how they interact with our server. You figured that out, which is more than we could have accomplished since we don't have any way to troubleshoot the product.
 

jhcrisp

New Member
Seriously stuck with ddclient seeming to have backflipped into the lava since a few days back when the clients tried to update.

No matter what I try I now continue to get this:

<ERROR CODE="700" TEXT="Hostname error" ZONE="">

I started with the original dynamic.zoneedit.com/dyn/auth.html which I noticed was failing.

I have tried various formats with https://api.cp.zoneedit.com/dyn/generic.php but just get the same error when testing via a browser.

I note that the dynamic host used to be 'dnsto' - is that still correct?

Any ideas? I have three dynamic hosts at the domain - one test one I just set up and two that have been there for some while which 'should be working' and all three fail.

Thanks.
 

jhcrisp

New Member
Hmmm - I have just realised one seems to be OK using an older ddclient, but the other two with ddclient the latest are not.

The query seems the same, but different answers received.
 

inspector71

New Member
Hmmm - I have just realised one seems to be OK using an older ddclient, but the other two with ddclient the latest are not.

The query seems the same, but different answers received.
Just a tip ... I understand you are a bit frazzled so maybe forgot ... might be handy to paste your
Code:
ddclient
version and
Code:
/etc/ddclient.conf
files in here to enable people to help you out.
 
Top