Re:Duck DNS – About
by supersparrow on Friday October 28, 2022 @07:41AM
(#33370135)
I use 1984 DNS to simplify updating my domains with my dynamic broadband IP. They have quite a nice API, so you can do this:
curl "https://api.1984.is/1.0/freedns/?apikey=xxxxxxxxxxxx&domain=..."
If you don't define an IP in the endpoint, it'll automatically look at the IP the request came from.
Duck DNS is able to do the same thing. Pretty neat not needing to specify the IP.
Yeah most routers come with a fixed list of services, when they really mean is a list of protocols.
I have a Huawei Fibre ONT, that only listed DynDNS, NoIP, and a few others. I could get away by using a NextDNS DNS override, and hosting my own script that forwarded the API call to the actual DDNS provider.
Re:Duck DNS – About
by vorticalbox on Friday October 28, 2022 @08:40AM
(#33370628)
Wouldn't something like ngrok[0] work for this?
The problem was that I had dynamic IP and my isp shit router did not suport DNS services. So I made a simple script that would log in and acess the router information page, get the public IP and update in the DUCK dns with a curl.
Worked Like a charm.