On 2/05/2022 8:13 pm, Reindl Harald wrote:
you want 127.0.0.1 act as your resolver no matter what
Well, not always... If your local BIND service isn't a recursive
resolver
irrelevant in context of this topic and worth exactly the same as
saying "if you don't use bind at all" and honestly i
> On 2 May 2022, at 18:13, Reindl Harald wrote:
>
>
>
> Am 01.05.22 um 23:54 schrieb Nick Tait via bind-users:
>> On 1/05/2022 9:13 pm, Reindl Harald wrote:
>>> Am 01.05.22 um 06:38 schrieb Nick Tait via bind-users:
I'm not 100% sure, but I wonder if disabling systemd-resolved may
Am 01.05.22 um 23:54 schrieb Nick Tait via bind-users:
On 1/05/2022 9:13 pm, Reindl Harald wrote:
Am 01.05.22 um 06:38 schrieb Nick Tait via bind-users:
I'm not 100% sure, but I wonder if disabling systemd-resolved may
create issues if, for example, you are using netplan with
On 1/05/2022 9:13 pm, Reindl Harald wrote:
Am 01.05.22 um 06:38 schrieb Nick Tait via bind-users:
I'm not 100% sure, but I wonder if disabling systemd-resolved may
create issues if, for example, you are using netplan with
systemd-networkd as the renderer? E.g. Will it still be possible to
Am 01.05.22 um 06:38 schrieb Nick Tait via bind-users:
I'm not 100% sure, but I wonder if disabling systemd-resolved may create
issues if, for example, you are using netplan with systemd-networkd as
the renderer? E.g. Will it still be possible to pick up DNS servers from
IPv6 router
Hi list.
I'm not 100% sure, but I wonder if disabling systemd-resolved may create
issues if, for example, you are using netplan with systemd-networkd as
the renderer? E.g. Will it still be possible to pick up DNS servers from
IPv6 router advertisements?
A lower impact (and IMHO more
I think you also might want to mask the service:
https://fedoramagazine.org/systemd-masking-units/
--
Ondřej Surý — ISC (He/Him)
My working hours and your working hours may be different. Please do not feel
obligated to reply outside your normal working hours.
> On 22. 4. 2022, at 17:20, Randy
sudo systemctl disable systemd-resolved.service
sudo service systemd-resolved stop
--
Visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from
this list
ISC funds the development of this software with paid support subscriptions.
Contact us at
systemd-resolved is broken in many ways. I doubt it can forward
correctly TSIG or SIG(0). If you have a proper DNS server running on
your machine, there is not many reasons to run also systemd-resolved. If
you need it, I suggest to write fixed /etc/resolv.conf pointing to
127.0.0.1 or ::1.
Good points, thanks.
-Original Message-
From: Reindl Harald
To: bind-users@lists.isc.org
Sent: Mon, Apr 18, 2022 12:41 am
Subject: Re: Bind and systemd-resolved
Am 18.04.22 um 07:26 schrieb Leroy Tennison via bind-users:
> When I attempt “dig -t AXFR office.example.com
@lists.isc.org
Sent: Mon, Apr 18, 2022 1:14 am
Subject: Re: Bind and systemd-resolved
Leroy,
here `man dig` is your friend:
Unless it is told to query a specific name server, dig will try each of the
servers listed in /etc/resolv.conf.When no command line arguments or options
are given, dig
There are a lot of extraneous details in here. This is not a BIND problem.
On Mon, 18 Apr 2022, Leroy Tennison via bind-users wrote:
When I attempt “dig -t AXFR office.example.com -k Kexample_dns.+157+18424.key”
on the DNS server (Bind 9.11) sudoed to root I get:
Why do you need to be root?
Leroy,
here `man dig` is your friend:
Unless it is told to query a specific name server, dig will try each of the
servers listed in /etc/resolv.conf.
When no command line arguments or options are given, dig will perform an NS
query for "." (the root).
It is possible to set per-user defaults
Am 18.04.22 um 07:26 schrieb Leroy Tennison via bind-users:
When I attempt “dig -t AXFR office.example.com -k
Kexample_dns.+157+18424.key” on the DNS server (Bind 9.11) sudoed to
root I get:
;; Couldn't verify signature: expected a TSIG or SIG(0)
; Transfer failed.
This is an Ubuntu 18.04
14 matches
Mail list logo
