HELP! Sites don't resolve after WHM v96.0.14 upgrade partially failed! BIND service pending?

[Benjamin D.]

Please help urgently, all websites on this server are unreachable after a WHM v96.0.14 update seemingly failed. BIND does not restart now, see the log below, and upcp is stuck also on the same error. Tried to gracefully reboot the server and after it reboots, it's still the same. What can I do now to bring it back to how it was before and have BIND work again like it was an hour ago?

Restarting DNS Server
Waiting for “named” to start …………failed.

Cpanel::Exception::Services::StartError Service Status
undefined status from Cpanel::ServiceManager::Services::Bind

Service Error
(XID 33q57f) The “named” service failed to start.

Startup Log
Aug 01 17:58:30 xxxxxx.com named[15421]: none:104: 'max-cache-size 90%' - setting to 28712MB (out of 31902MB)
Aug 01 17:58:30 xxxxxx.com named[15421]: command channel listening on 127.0.0.1#953
Aug 01 17:58:30 xxxxxx.com named[15421]: isc_stdio_open '/var/log/named/named.log' failed: file not found
Aug 01 17:58:30 xxxxxx.com named[15421]: configuring logging: file not found
Aug 01 17:58:30 xxxxxx.com named[15421]: loading configuration: file not found
Aug 01 17:58:30 xxxxxx.com named[15421]: exiting (due to fatal error)
Aug 01 17:58:30 xxxxxx.com systemd[1]: named.service: control process exited, code=exited status=1
Aug 01 17:58:30 xxxxxx.com systemd[1]: Failed to start Berkeley Internet Name Domain (DNS).
Aug 01 17:58:30 xxxxxx.com systemd[1]: Unit named.service entered failed state.
Aug 01 17:58:30 xxxxxx.com systemd[1]: named.service failed.

Log Messages
Aug 1 17:58:30 secure named[15421]: exiting (due to fatal error)
named has failed. Contact your system administrator if the service does not automagically recover.

-------------

Service status lists BIND like this: bind 9.11.4-26.P2 pending

 

[Benjamin D.]

OK, I have no freaking idea why and how this happened, but I just tried these commands and it fixed the whole issue, everything works as normal now. Hope it helps the next fellow. This is extremely panicking, WTF happened during v96.0.14 update?!

Login using SSH as root, then run these 2 commands:

1) mv /etc/named.conf /etc/named.conf.BACKUP
2) /usr/local/cpanel/scripts/rebuilddnsconfig

Now go to WHM and restart your DNS server.

Thank god it all fixed itself!

 

[kodeslogic]

Glad to know you were able to figure it out.

 

[cPRex]

I'm glad you were able to get that resolved. While I can't say for sure what the initial cause was, it does seem that there was an issue with the DNS configuration on the server, and those commands would have backed up the file and rebuilt it.

If you wanted to do some more research you could compare the backup file you created to the current /etc/named.conf to see if you can spot any differences.

 

[Benjamin D.]

Ah, crap... well I can't do that now After double checking that everything was working correctly, I deleted the .BACKUP but in hindsight it would have been a great idea, indeed. Now I'm curious AF. DAMN! ;-)