I am running Yunohost 2.7.5 in a local VM on my virtualization server, and since 25th of December new IPs (I receive a new one every day) are not updated anymore at my XYZ.nohost.me subdomain.
I restarted the Yunohost VM, and from the command line I tried
yunohost dyndns update
but it terminates with an “communication with server failed …” error.
Is there a general problem with the nohost.me server or is it more likely a local problem with my Yunohost installation?
I have the same problem. yunohost dyndns update -d klimek.noho.st --verbose results in the following error message:
Updated needed, going on…
Now pushing new conf to DynDNS host…
Outgoing update query:
;; ->>HEADER<<- opcode: UPDATE, status: NOERROR, id: 0
;; flags:; ZONE: 0, PREREQ: 0, UPDATE: 0, ADDITIONAL: 0
;; ZONE SECTION:
;noho.st. IN SOA
;; UPDATE SECTION:
_xmpp-client._tcp.klimek.noho.st. 0 ANY ANY
_xmpp-server._tcp.klimek.noho.st. 0 ANY ANY muc.klimek.noho.st. 0 ANY ANY pubsub.klimek.noho.st. 0 ANY ANY vjud.klimek.noho.st. 0 ANY ANY klimek.noho.st. 0 ANY ANY klimek.noho.st. 0 ANY ANY
mail._domainkey.klimek.noho.st. 0 ANY ANY
_dmarc.klimek.noho.st. 0 ANY ANY klimek.noho.st. 0 ANY ANY
*.klimek.noho.st. 0 ANY ANY klimek.noho.st. 0 ANY ANY
*.klimek.noho.st. 0 ANY ANY
_xmpp-client._tcp.klimek.noho.st. 3600 IN SRV 0 5 5222 klimek.noho.st.
_xmpp-server._tcp.klimek.noho.st. 3600 IN SRV 0 5 5269 klimek.noho.st. muc.klimek.noho.st. 3600 IN CNAME klimek.noho.st. pubsub.klimek.noho.st. 3600 IN CNAME klimek.noho.st. vjud.klimek.noho.st. 3600 IN CNAME klimek.noho.st. klimek.noho.st. 3600 IN MX 10 klimek.noho.st. klimek.noho.st. 3600 IN TXT “v=spf1 a mx ip4:87.123.165.245 ip6:2001:16b8:282:300:3d72:74e9:83be:5c5a -all”
mail._domainkey.klimek.noho.st. 3600 IN TXT “v=DKIM1; k=rsa; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDMQdb7x380iqD0jit+jZVqxbFYFRZK6SLNQ71QGOhe4rAaE6MZ3cjbLpHXP9hOEcweuF9b6pXuA3lb7qw5yXUAk+Sd5hmmR7Vzsw+jY9QxNN6U8+ezN3aqiCRKHyeAtM6g1RADgwb7ScFkWmpQDik0hKhzpcakf+za7eoBpmRlrwIDAQAB”
_dmarc.klimek.noho.st. 3600 IN TXT “v=DMARC1; p=none” klimek.noho.st. 3600 IN A 87.123.165.245
*.klimek.noho.st. 3600 IN A 87.123.165.245 klimek.noho.st. 3600 IN AAAA 2001:16b8:282:300:3d72:74e9:83be:5c5a
*.klimek.noho.st. 3600 IN AAAA 2001:16b8:282:300:3d72:74e9:83be:5c5a
; Communication with server failed: operation canceled
Error: Unable to update IP address on DynDNS
I would really appreciate feedback on that matter.
somewhere you should see Connecting to dyndns.yunohost.org followed by an IP address. Do you see an IPv4 (91.224.148.92) or an IPv6 (2a03:7220:8080:5c00::1) ?
So I redid yunohost dyndns update -d klimek.noho.st --verbose and it was successful. But I still cannot reach my yunohost instance using that domain. Do I have to take more steps?
This morning my Yunohost Server was not reachable again. After updating the dyndns with yunohost dyndns update -d klimek.noho.st --verbose it is working again at the moment. Is there a way to let Yunohost do that automatically again?
Yes, actually it should do it automatically every 2 minutes… There should be a cron job named /etc/cron.d/yunohost-dyndns (or something alike) that precisely does a yunohost dyndns update.
I’m not sure why you have a -d klimek.noho.st in your command line ? Does that work without it ?
I don’t actually know. I think I have the command from somewhere in this forum. yunohost dyndns update --verbose tells me No updated needed. I believe because I’ve already updated it today.
The content of /etc/cron.d/yunohost-dyndns is: