Another thing I forgot to mention, is the need to express these parameters in
the options clause in named.conf:
options {
// RPZ zone
// Source: https://deteque.com/m3aawg-bind-training/named.conf
response-policy {
zone "rpz.local";
};
};
My
Create a catalog zone and use that to distribute the zone configuration to all
your recursive
servers.
As for using a zone that is not delegated to you. Microsoft own
appserviceenvironment.net
and are telling you to use it this way. This is no different to the IETF
saying you can have
your
On Friday, 14 April 2023 00:28:24 CEST John Thurston wrote:
> Due to a requirement to use something Microsoft crafted, we are being
> asked to assert (internally) authority over 3rd-level names under
> appserviceenvironment.net
>
> I've pushed back on this, because I don't think it's nice to
Due to a requirement to use something Microsoft crafted, we are being
asked to assert (internally) authority over 3rd-level names under
appserviceenvironment.net
I've pushed back on this, because I don't think it's nice to publish
"authoritative" answers in domains we have not been delegated.
4 matches
Mail list logo
