Hello I have created a ddns module for ISPConfig 3 and published it on github: https://github.com/mhofer117/ispconfig-ddns-module Unlike the other threads with scripts using the remote api, this one will: - Integrate into the existing DNS menu of ISPConfig 3 - Not require a remote-api user - Allow clients, resellers and admins to create update tokens - Perform updates using a simple URL and the generated token, compatible with many existing consumer solutions without manual cron scripts - Allow restricting a token to individual zones / records / record types - Allow updating A (IPv4) or AAAA (IPv6) In Addition, the token endpoint implements the same authentication rate-limiting as the normal login process. Feedback and suggestions are welcome. Regards
Looks really nice! I moved the post to the ISPconfig addons forum, so it can be found easier. And I'll add a link on the ISPConfig website.
Sure, if this is desired. However there are some things that will need some attention: - On ports other than 443/80, like the default ISPConfig port 8080, it doesnt work with some vendors, namely AVM / FRITZ!Boxes - Putting ISPConfig behind a reverse proxy can also lead to issues if not set up correctly (trusting X-Forwarded-For headers) and is itself a security concern. I thought about providing a proxy script that can be put on any vhost and will communicate with the module. But this will require some config values to be secure and seamless which I would have just added into a config file. If this is integrated there would probably need to be a config interface for this? What other steps would be required from my side to merge this module into the main project?
Good question. The best solution would be something working out of the box, ofcourse. Otherwise, keeping it as a separate module is better. Not sure how we can resolve this easily. Depends on the current code, haven't looked into it yet.
Hey guys, This may seem like a totally stupid question, but I have been using dyndns services for a few years. I have about three remote computers out there that I need to be able to get to without remote services attached. I use the dyndns services for this purpose. That being said I came across the dynamic dns module for ispconfig3 and I am a little confused. Is it setup to use to allow ispconfig to be run on a dynamic ip or is it to allow you to basically run a dynamic dns for what I am needing with ispconfig3? I just don't understand the terminology well enough on dns to understand clearly. If it isn't for what I am needing can you recommend any procedures to allow this? Spending $55 a year for these services isn't terrible, but I would like to do it "in-house" if it would save a little money and time. Thanks so much for any advice and insight you can offer.
Hello, a great module. It's going great for me so far! Can you recommend a client for Windows that is compatible with the module? I haven't found one yet :-(
