September 2, 2016 at 7:10 pm #44633
will be fine to have a custom dyndns to connect to the dyndns service we like. It is a big pity that zeroshell has not a dyndns customizable like other routers. Thank you Fulvio Ricciardi. Your is a very good project.September 6, 2016 at 11:05 pm #54246
I have a working patch for this. https://github.com/jb68/zeroshell-ui/tree/dyn-dns
This will allow you to specify a template url + username and password. Works well for me with joker.com
You can test here https://www.zeroshell.org/forum/viewtopic.php?p=15266#15266
I didn’t publish it yet because there are a few things that needs to be tied in:
1) Design – Current ZS version is basically an iteration from the very first one that supported dyndns and store only limited data. I had to rewrite how data are kept to be more general. This was bigger that I initially thought: https://github.com/jb68/zeroshell-ui/compare/dyn-dns
While is working great on custom mode it need to be checked on legacy modes.
2) Not all providers will have a check url so I had to piggyback on dyndns. This is also a major issue when using net balancer.
3) Split DNS – this happens if you have ZS to host a local authoritative zone. A simple example is having a home.domain.com as a dyn dns and having home.domain.com as an SOA on ZS. In this way nas.home.domain.com will be your NAS. 😉
The original ZS script will use the ZS resolver so if this happens then you will need to update the internal pointer on ZS resolver which is in LDAP.
This is one way to implement this, the other is to use the DNS server from a forwarder. I did it in the first way (updating LDAP) but my feeling is that the other way is more elegant.
4) DynDNS and Net Balancer in balancing mode. Currently there is no way of associating a DynDNS with a connection defined in Net Balancer. Unfortunately the process does the change by accessing a checkIP url in order to get the router IP. Basically in this scenario DynDNS will randomly update to one of the connection.
5) DynDNS and multiple independent GW. Let say we have LAN1, LAN2, WAN1, WAN2 and WAN1 and WAN2 are 2 different IFs without netbalance or failover each having its own dyndns. (personally I don’t see this as a likely setup but is possible).
My current version deal with point 1 and 2, I also have some code that address point 3 and nothing for point 4 or 5.February 27, 2017 at 1:12 am #54247
After several fixes and some tests I created a patch:
I think a patch is more flexible.
In order to use it, download and save the patch on
Then add this line in preboot script:
cd /root/kerbynet.cgi && patch -p0 </DB/opt/patch/ddns-ZS-3.7.1_1.patch
June 1, 2017 at 3:06 am #54248
Like under line 79
now my update URL can look like:
And if possible remove this line:
logger -t DDNS “WAN IP=$IP $HOST=$RESOLUTION (no update)”
as it writes an entry in the DDNS log every 30secs or so 😉
This was easy.. I did this changes.
However we cannot merge this branch into master cause I am not using the master to generate a release. Master is used to have an image to current release.
I will also generate a new patch and post it. Also
__USERNAME__:__PASSWORD__@ .. from your url should not be necessary the username and pass are added anyway in the header.
You must be logged in to reply to this topic.