Error: Could not update IP address to DynDNS

My YunoHost server

Hardware: LXC Container on Proxmox (Intel NUC)
YunoHost version:
I have access to my server : Through SSH | through the webadmin | direct access via keyboard / screen
Are you in a special context or did you perform some particular tweaking on your YunoHost instance ? : no
If yes, please explain:

Description of my issue

Hi folks!
I have a problem with my domain since a few days. I can’t exactly pinpoint a time, but it seems the server is not able to update it anymore.

The output of

yunohost dyndns update  --force

is available here:
As the last line only says “ERROR -” I can’t make any sense of it.
So far, I tried rebooting the yuno container, the host system, all routers/switches involved as well as reconnecting explicitly to get a new IPv4.

Anyone able to help me out? Thanks in advance! :slight_smile:

What the diagnosis is saying?

That was fast!

Some DNS records are missing or incorrect for domain (category basic)

    This domain's DNS configuration should automatically be managed by YunoHost. If that's not the case, you can try to force an update using yunohost dyndns update --force.
    The following DNS record does not seem to follow the recommended configuration:
    Type: A
    Name: @
    Current value: 84.(some old ip)
    Expected value: 84.(actual ip)

Only ports reachable are 80 and 443 (that’s a config I’m using for quite some time)

Also I’m using a custom /etc/resolv.conf, but the diagnosis says it works. I pointed it to both the local routers I have in my home network.

Now that I wrote all that, here’s the log :smiley:

Are you looking for sth specific?

edit: reverted the resolv.conf to the recommended symlink - as expected, that sadly wasn’t a problem.

Hey ho!
Anybody an idea what I can do to further get to the cause of this?
Any help is appreciated :slight_smile:

Found the --debug flag, which seems to not give any more details about the actual error, but it provides an id that changes with every try.

I have a workaround for now by using local DNS entries, but this will become interesting once my SSL certificates expire.
Does anybody have an idea what I can try to debug and/or solve this problem?

Good morning everyone,
the problem still persists.
The slightest hint that might help prevent me from setting up a new yuno instance or migrate the apps to individual containers is appreciated.