Bahman Niko Verified User Joined Dec 14, 2019 Messages 16 Location Hamburg Jan 27, 2023 #21 All domains are affected.
Richard G Verified User Joined Jul 6, 2008 Messages 13,776 Location Maastricht Jan 27, 2023 #22 bahman.neekooee said: All domains are affected. Click to expand... Yes but only these 3 are causing the errors, which most likely cause named to not start. Backup your /etc/named.conf file to somewhere, then edit the /etc/named.conf and remove those 3. Then restart named and see if it works.
bahman.neekooee said: All domains are affected. Click to expand... Yes but only these 3 are causing the errors, which most likely cause named to not start. Backup your /etc/named.conf file to somewhere, then edit the /etc/named.conf and remove those 3. Then restart named and see if it works.
Bahman Niko Verified User Joined Dec 14, 2019 Messages 16 Location Hamburg Jan 27, 2023 #23 You hit the target ? But not for customer domains, Rather, the server name was wrong in the list of domains itself, which caused interference in the launch of named service. SUPER Richard G.?
You hit the target ? But not for customer domains, Rather, the server name was wrong in the list of domains itself, which caused interference in the launch of named service. SUPER Richard G.?
Richard G Verified User Joined Jul 6, 2008 Messages 13,776 Location Maastricht Jan 28, 2023 #24 Great. Nice to see it's fixed now. You're welcome.