RE: Chroot Bind failed to start

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

PKG itself. Just wondering why that mistake down bind down and how I can get more meaningful logs on the logs even those a prepackaged bind version. TIA Paul From: bind-users On Behalf Of Paul Amaral via bind-users Sent: Tuesday, March 15, 2022 9:08 AM To: 'bind-users@lists.is

Chroot Bind failed to start

Hi, I realize this is related to Centos, but all the sudden chroot bind failed to start up with any meaningful errors. Anyone know what might be the issue here? I have no clues on that the issue is. Paul Job for named-chroot.service failed because the control process exited with error code.

RE: named-checkzone

I was thinking more instantaneous without moving things around. I looked at vim vimrc autocmd but I couldn’t get named-checkzone to execute and I would still have to somehow have named-checkzone look at the last zone that was edited. Good suggestion though. From: Taylor, Gord [mailto:gor

RE: KAMINSKY vulnerability !!

Thanks to Tatuya Jinmei. 2408. [bug] A duplicate TCP dispatch event could be sent, which could then trigger an assertion failure in resquery_response(). [RT #18275] -Original Message- From: Stephane Bortzmeyer [mailto:bortzme..