|
|
Post by Lee Sharp on Oct 23, 2015 14:21:48 GMT
I am working on updating EZ-IPupdate to support modern providers. (Like no-ip which I use) So what is everyone using? And what custom settings are you using to do it, or how are you doing it if not with SmallWall?
Something like...
No-IP
Service Type = DynDNS (Custpom)
Server = dynupdate.no-ip.com
Or,
DNSomatic
/usr/bin/fetch --no-verify-peer "https://username:password@updates.dnsomatic.com/nic/update?hostname=dyndnsname" > /tmp/error.log
|
|
sami
New Member
Posts: 9 
|
Post by sami on Oct 23, 2015 18:52:26 GMT
I'm having dynamic dns on Cisco router using service from Namecheap. Pending to migrate smallwall until there is next beta to support Hyper-V... From Cisco (IOS 15.4(3)M4 ): ip ddns update method namecheap HTTP add dynamicdns.park-your-domain.com/update?host=##removed hostname##&domain=##removed domain##&password=##removed password##=<a> interval maximum 5 5 5 5 Has been working extremely well after I found out the correct syntax for Cisco IOS. |
|
|
|
Post by Lee Sharp on Oct 23, 2015 21:36:48 GMT
That should be easy. dynamicdns.park-your-domain.com/update?host=%hostname%&domain=%domain%&password=%pass%=<a> Does that look right? |
|
sami
New Member
Posts: 9
|
Post by sami on Oct 24, 2015 13:50:08 GMT
Almost, except I believe that Cisco will replace that trailing =<a> with the IP address of the device. I.E. ...=192.168.1.1
|
|
|
|
Post by mikael on Nov 1, 2015 11:47:58 GMT
It would be nice to be able to have a completely custom URL. This way smallwall does not need to support every possible dyndns provider.
|
|
|
|
Post by Lee Sharp on Nov 1, 2015 13:38:14 GMT
Well, "custom" is quite custom. That said, I am using Andrew White's idea, and putting "fetch" in the next beta. That will allow some versatility in the scheduler.
|
|
|
|
Post by mikael on Nov 2, 2015 16:36:09 GMT
Yes, you are right. The "DynDNS (custom)" option is very handy in most cases, since it's possible to specify a server address.
But it is bound to a specific URL format. It may not be a problem. I just brought it up because I've seen other open source firewalls having an option where you can supply a customized URL for updating the dynamic DNS.
This is IMO a low priority feature since we already have a "custom" option which work well in most cases.
|
|
|
|
Post by mikael on Nov 2, 2015 16:41:43 GMT
To answer your question:
We host a DynDNS service for our clients. It's compatible with the URL format used in the "DynDNS (custom)" option in smallwall. Therefore we always use that option.
|
|
|
|
Post by Lee Sharp on Nov 2, 2015 18:18:32 GMT
Very cool! Would love to know more about the back end you use for that.  |
|
|
|
Post by mikael on Nov 3, 2015 16:39:26 GMT
It's custom developed by us (mainly me). The front facing IP address updating script is a no brainer. It's a small php script running on nginx web server. The big thing is to set up a stable DNS foundation that stores records in an sql database. We had that already, because our clients modifies their DNS record in the web browser. We just hooked our DDNS script into this system. Basically what you need is a web application that is protected by a .htaccess file and a script that executes the update like this: http://<username>:<password>@<server>/nic/update?hostname=<thehostname>&myip=<theipaddress> It's the same format DynDNS.com uses and it's the format that smallwall's "DynDNS (custom)" option produces. |
|
|
|
Post by jrronimo on Nov 6, 2015 6:32:09 GMT
Mine is currently handled through Microsoft's "Windows Home Server" -- it's handled in their software and talks to their provider thing, so it's sort of irrelevant to this discussion... haha.
I've thought about switching to no-ip or something similar for ages, though. I'll be paying attention to see what sort of options are out there. I'd love to have a 'proper' DNS name someday... soon as I think of one.
|
|
|
|
Post by jrronimo on Nov 26, 2015 17:04:21 GMT
So, of course, just a few weeks after posting that, my Home Server is dead. I'm rebuilding the box as a Linux machine so I won't have to worry about WHS' support going away in the future, but now that means I need a new dynamic ip provider.
I tried setting up hn.org through SmallWall, but I'm seeing notes in the logs about failing to update. Is this a product of ez-ipupdate needing to be updated?
|
|
|
|
Post by Lee Sharp on Nov 26, 2015 20:48:36 GMT
There are a number of problems with ezipupdate right now. It does not have a number of popular providers. It has old providers not in business or not doing DYNdns anymore. And it is misconfigured for some that do offer service. So, more details on your problem would help. Perhaps the DYNdns custom setting to get it working and then I can fix the defaults.
|
|
dennis
Junior Member
Posts: 23
|
Post by dennis on Dec 9, 2015 5:56:28 GMT
Do not remove support for RFC 2136 Dynamic DNS, thank you.
|
|
|
|
Post by Lee Sharp on Dec 9, 2015 15:48:51 GMT
Do not remove support for RFC 2136 Dynamic DNS, thank you. No worries there. I am only removing things that have left the business. |
|
