With regard to using chroot, hasn't named/BIND long had the "-u" (user)
and "-t" (directory) options to accomplish the same thing more easily?
On Fri, 16 Oct 2020 12:47:35 -0500
Chuck Aurora wrote:
> /me catching up on earlier parts of this thread,
>
> On 2020-10-15 11:42, alcol alcol wrote:
>
/me catching up on earlier parts of this thread,
On 2020-10-15 11:42, alcol alcol wrote:
A DNS server can exist if you follow NIC instractions.
Mainly have you a leased line ever on? primary DNS can't be down or
NIC could down your domain.
Then you have to install and configure it. Better a fe
On 2020-10-16 06:05, Sami Ait Ali Oulahcen via bind-users wrote:
I've been looking for a way to implement this on nft or through
firewalld, but couldn't find anything comprehensive.
So if it does get updated, please let us know :)
It won't be by me, for more than one reason (I am no longer at
On 2020-10-16 04:34, Michael De Roover wrote:
Interesting article, thanks for sharing this! I'm slightly confused
YW!
about some things in it though. Does this mean that any traffic will be
put on the connection tracker and be treated as stateful unless we use
CT --notrack, or can the kernel
On Fri, Oct 16, 2020 at 10:22 AM Matus UHLAR - fantomas
wrote:
>> On 16.10.20 09:56, Bob Harold wrote:
> >The BIND ARM (9.16.2) says:
> >"There may be one or more forwarders, and they are queried in turn until
> >the list is exhausted or an answer is found."
> >
> >But [an old mailinglist post] sa
That is certainly not obvious. How do I request improving the manual?
"in turn" would seem to imply "in order", and the order would logically be
the order I listed them.
--
Bob Harold
DNS and DHCP Hostmaster - UMNet
Information and Technology Services (ITS)
rharo...@umich.edu 734-512-7038
O
On 16.10.20 09:56, Bob Harold wrote:
The BIND ARM (9.16.2) says:
"There may be one or more forwarders, and they are queried in turn until
the list is exhausted
or an answer is found."
But
https://lists.isc.org/pipermail/bind-users/2015-August/095544.html
says:
"Forwarders are selected based on a
The BIND ARM (9.16.2) says:
"There may be one or more forwarders, and they are queried in turn until
the list is exhausted
or an answer is found."
But
https://lists.isc.org/pipermail/bind-users/2015-August/095544.html
says:
"Forwarders are selected based on an RTT(round-trip-time)-based algorithm"
I've been looking for a way to implement this on nft or through
firewalld, but couldn't find anything comprehensive.
So if it does get updated, please let us know :)
On 10/16/20 10:34 AM, Michael De Roover wrote:
Interesting article, thanks for sharing this! I'm slightly confused
about some th
Interesting article, thanks for sharing this! I'm slightly confused
about some things in it though. Does this mean that any traffic will be
put on the connection tracker and be treated as stateful unless we use
CT --notrack, or can the kernel make a heuristic based on what's in the
iptables rule (i
Hi all,
related parts from my named.conf:
- - -
include "/usr/local/etc/namedb/dns-keys/Kns4-he.net.conf";
// slave.dns.he.net pulls zones from us, ns1.he.net receives notify from us
server 216.218.133.2 {
keys { ns4-he.net. ; };
};
server 2001:470:600::2 {
keys { ns4-he.net. ; }
11 matches
Mail list logo
