Crist Clark writes:
> Note that is all Linux-specific behavior. BSD-derived stacks are generally
> different, e.g. FreeBSD and MacOS. They do not respond to addresses that
> aren’t explicitly assigned to an interface. You cannot bind an address not
> assigned to an interface.
I know nothing abou
Bagas Sanjaya writes:
> Yet, the change **does not** persist on reboot (IOW, that 127.0.0.53 address
> is gone or back to defaults). Hence, I have to add dummy interface.
No network configuration is persistent unless you make it so. I assumed
that was obvious.
Bjørn
--
Visit https://lists.is
Bagas Sanjaya writes:
> Here in my case, I was expecting BIND to listen to 127.0.0.53 as
> separate address, just like in similar applications (systemd-resolved,
> dnsdist, etc).
You do need to add the address to an interface, but you don't need to
add a new dummy interface. This will make your
Greg Choules via bind-users writes:
> What's a "primary master" as opposed to (presumably?) a "secondary master"?
Some servers will be both masters and slaves when using hierarchical
replication. It is useful to define the root of the tree as "primary
master" and refer to any upstream from a "s
4 matches
Mail list logo
