ddclient VS docker-swag

You can find an example of the full config file here: https://github.com/ddclient/ddclient/blob/master/ddclient.conf.in

Check your distribution's repos first, but Ddclient doesn’t have an automatic installation procedure. Get the tar-file from https://github.com/ddclient/ddclient/releases and untar it. Copy the perl script to your favorite location (ex. /usr/sbin) and create a

ddclient has support for Google DNS. It is available as a package on Ubuntu/Debian.

As I recall ddclient is a perl script or some such. It should be relatively easy to just download and build it. https://github.com/ddclient/ddclient/releases

Which version of OPNSense are you running at the moment? There were changes to the os-ddclient package in the 23.1.6 patch in order to fix the config generation in response to changes in ddclient 3.10.0 when enabling IPv6 updates (ipv6=yes was disabled, and replaced with usev4/usev6. If a reboot doesn't help, I'd be happy to give you a hand with debugging the ddclient config.

FROM alpine:3.17.3 RUN apk update && apk upgrade RUN apk add git make autoconf automake perl-io-socket-inet6 perl-io-socket-ssl WORKDIR /opt RUN git clone https://github.com/ddclient/ddclient.git WORKDIR /opt/ddclient RUN ./autogen && ./configure --prefix=/usr --sysconfdir=/etc/ddclient --localstatedir=/var RUN make && make VERBOSE=1 check && make install RUN rm /etc/ddclient/ddclient.conf && touch /opt/ddclient.config && ln -s /opt/ddclient.config /etc/ddclient/ddclient.conf RUN chmod 600 /etc/ddclient/ddclient.conf ENTRYPOINT ["/bin/sh"] CMD ["-c", "ddclient; while true; do sleep 3600; done"]

So a came accros Inadyn which compared to the current state of DDclient, is being actively maintained. More info here from what i am talking about.

You can use ddclient, it supports a lot of DNS providers: https://github.com/ddclient/ddclient

I have a NAS on .0.181 and a swag container (on a different port than nginx) on .0.180 that points to my public facing services. For obvious reasons, I don't want my public domain to point to any other ports/addresses on my home network. Additionally, as elegant as swag is, it requires authentication and so won't work for simple local DNS. I now have one local domain for each server and an nginx instance on each that resolves to my different services on each.

OP is even linking the Github... https://github.com/linuxserver/docker-swag

I have an UnRAID server with a few services (Jellyfin, Nextcloud, etc.) running on it behind Linux Servers' SWAG reverse proxy container, which is built on Nginx and Let's Encrypt. This is pointed to a DuckDNS link, which is then pointed at my domain with a CNAME. So I can access Jellyfin, for example, at jellyfin.mydomain.com. A few weeks ago, due to seemingly unrelated issues, I got a new modem/router, an Arris SURFboard G34. For the first few weeks, everything was working as before. But now, when on my LAN, I can't get to my services at the proxied domain. It times out every time. There are no errors in SWAG's logs, nothing seems amiss in the router's web interface, and the services are available both at their IP:port address and, when not on my LAN, I can access them at the domain no problem.

Reverse proxy, probably? I use Docker SWAG, setup here, with DuckDNS and it works really well for me. There are of course many ways to reverse proxy, as I linked to earlier.