Suddenly: "Failed to resolve A for HOSTNAME.nohost.me"

Hi all!

My yunohost-server is telling me that my dns-settings are wrong. I tried some things but nothing changed. I’m out of ideas. Can somebody help or point me in the right direction?

Cheers!

My YunoHost server

Hardware: Old laptop
YunoHost version: Server is running YunoHost 11.0.9.15 (stable)
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 ? : yes, I made some changes to the sshd-config

Description of my issue

My Yunohost-server ran without problems for a long time. Around the end of September I started to get emails from Cron Daemon:

Subject:

Cron <root@HOSTNAME> : YunoHost DynDNS update; sleep $((RANDOM%60)); ! ping -q -W5 -c1 ip.yunohost.org >/dev/null 2>&1 || test -e /var/run/moulinette_yunohost.lock || yunohost dyndns update >> /dev/null

Body:

Failed to resolve A for HOSTNAME.nohost.me

Sometimes also:

Failed to resolve AAAA for HOSTNAME.nohost.me

The interesting thing is that everything is still working. The server is reachable from WAN and from LAN.

I also checked the dyndns-config which seemed fine.

Nevertheless I tried if updating the dyndns config would help: sudo yunohost dyndns update --force.

sudo yunohost domain config get HOSTNAME.nohost.me
dns.registrar.registrar: 
  ask: This domain is a nohost.me / nohost.st / ynh.fr and its DNS configuration is therefore automatically handled by YunoHost without any further configuration. (see the 'yunohost dyndns update' command)
  value: yunohost
feature.app.default_app: 
  ask: Default app
  value: _none
feature.mail.features_disclaimer: 
  ask: So far, enabling/disabling mail or XMPP features only impact the recommended and automatic DNS configuration, not system configurations!
feature.mail.mail_in: 
  ask: Incoming emails
  value: yes
feature.mail.mail_out: 
  ask: Outgoing emails
  value: yes
feature.xmpp.xmpp: 
  ask: Instant messaging (XMPP)
  value: yes
sudo yunohost domain cert status HOSTNAME.nohost.me
certificates: 
  HOSTNAME.nohost.me: 
    CA_type: Let's Encrypt
    summary: Great!
    validity: 23

Diagnoses outcome:

https://paste.yunohost.org/raw/xafovemuki

I also upgraded the server to the latest Yunohost version. Then I rechecked everything and reconfigured everything but nothing changed.

1 Like

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.