Dominik,
please create issue in our GitLab (https://gitlab.isc.org/) and include
full logs (preferably run named with `-d 99` to get most diagnostic
output).
Thanks,
--
Ondřej Surý (He/Him)
ond...@isc.org
> On 17. 5. 2021, at 9:13, Dominik wrote:
>
> Hello,
>
> yesterday I tried version
Hello,
yesterday I tried version 9.17.12 because of the new TLS features.
My resolv.conf only contains the local resolver 127.0.0.1 and ::1.
The problem is that the new Bind9 doesn't start without having an
alternative resolver in resolv.conf. It looks like something in the
Bind9 startup
Folks,
Thinking of using Ansible to help with standardized bind installations & auto
setup. Searched the list Archives/ISC website and didn't see much. Found a
variety of Ansible roles/playbooks on Google, but nothing seemed to be the
clear preferred favorite?Any recommendations are
> On 17. 5. 2021, at 15:10, G.W. Haywood wrote:
>
> a simple unified diff and sending a patch by email
Here’s what happens when you do that:
1. somebody has to download your patch locally
2. somebody needs to triage the patch (and the issue) and if the description
isn’t up-to-par write back
Hi,
I am sorry, but what? I would suggest to actually try the interface
before you write angry emails. There’s nothing of sorts as you
describe. The only hassle is that before forking, you need to ask
ISC to actually allow your user account to create forks.
There’s no requirement to use
Hi there,
On Sun, 16 May 2021, Ond?ej Sur? wrote:
On Sun, 16 May 2021, Chuck Aurora wrote:
> On Sun, 16 May 2021, Ond?ej Sur? wrote:
>
> > ... yes, you need ISC GitLab account to create new issues (unless
> > it's a security vulnerability then OpenPGP encrypted email is
> > accepted). We need
6 matches
Mail list logo
