Re: Chroot Bind failed to start

2022-03-15 Thread Reindl Harald
hroot Bind failed to start Am 15.03.22 um 14:37 schrieb Paul Amaral via bind-users: Neverminded, I was able to traceback my steps and realize a fat fingered a DNS entry in one of the zones, added two periods to an authoritative zone’s DNS record, causing bind to fail to start. The concerning issu

RE: Chroot Bind failed to start

2022-03-15 Thread Paul Amaral via bind-users
Subject: Re: Chroot Bind failed to start Am 15.03.22 um 14:37 schrieb Paul Amaral via bind-users: > Neverminded, I was able to traceback my steps and realize a fat > fingered a DNS entry in one of the zones, added two periods to an > authoritative zone’s DNS record, causing bind to fail

Re: Chroot Bind failed to start

2022-03-15 Thread Reindl Harald
Am 15.03.22 um 14:37 schrieb Paul Amaral via bind-users: Neverminded, I was able to traceback my steps and realize a fat fingered a DNS entry in one of the zones,  added two periods to an authoritative zone’s DNS record, causing bind to fail to start. The concerning issue was there was no err

RE: Chroot Bind failed to start

2022-03-15 Thread Paul Amaral via bind-users
Neverminded, I was able to traceback my steps and realize a fat fingered a DNS entry in one of the zones, added two periods to an authoritative zone’ s DNS record, causing bind to fail to start. The concerning issue was there was no error on the logs at all, making it hard to figure out the issue.

Re: Chroot Bind failed to start

2022-03-15 Thread Reindl Harald
Am 15.03.22 um 14:08 schrieb Paul Amaral via bind-users: Hi, I realize this is related to Centos, but all the sudden chroot bind failed to start up with any meaningful errors. you need to debug this terrible "ExecStartPre" where the package maintainer was too lazy to include a script file in