Author Topic: DNS stopped, but starting the service disables the gui  (Read 3291 times)

foeke

  • Zen Apprentice
  • *
  • Posts: 25
  • Karma: +0/-0
    • View Profile
DNS stopped, but starting the service disables the gui
« on: July 24, 2024, 09:44:51 am »
Hi,
Since this morning both paid servers stopped the DNS service. As soon as I tries to restart them, the webservice stopped (504 Gateway Time-out).

I tried to restart one server but that failed to reboot

[FAILED] Failed to start Bind Domain name server

And booting stops after [OK] Started time and date service.

The other server is still running but not working since you can’t restart the DNS and without DNS you can’t even access your fileshares.

restarting the dns using the command line didn’t work (it just halts indefinitely after the sudo zs dns restart ) same with restarting the firewall or webgui.

I've opened a ticket but I now have two customers down, so all help is appreciated.

fabio.soggia

  • Zen Apprentice
  • *
  • Posts: 2
  • Karma: +0/-0
    • View Profile
Re: DNS stopped, but starting the service disables the gui
« Reply #1 on: July 24, 2024, 09:53:17 am »
Same problem here, paid server
From log, automatic update at 3:47am (bind9-dnsutils bind9-host python3-zipp bind9-utils bind9 bind9-libs)
Now bind doens't start

Daniel Joven

  • Zentyal Staff
  • Zen Monk
  • *****
  • Posts: 70
  • Karma: +21/-0
    • View Profile
Re: DNS stopped, but starting the service disables the gui
« Reply #2 on: July 24, 2024, 10:55:46 am »
Hi guys,

This issue is reported in the following link, we will update it as soon as possible.

- https://github.com/zentyal/zentyal/issues/2173

fabio.soggia

  • Zen Apprentice
  • *
  • Posts: 2
  • Karma: +0/-0
    • View Profile
Re: DNS stopped, but starting the service disables the gui
« Reply #3 on: July 24, 2024, 11:56:15 am »
Thanks, workaround works, but had to reboot

foeke

  • Zen Apprentice
  • *
  • Posts: 25
  • Karma: +0/-0
    • View Profile
Re: DNS stopped, but starting the service disables the gui
« Reply #4 on: July 25, 2024, 02:52:08 pm »
Thanks, workaround works, but had to reboot
Thanks. That was what was needed in the end in our case also.