check-names conflicts with SPF macro definition

2021-01-04 Thread Daniel Stirnimann
Hello all, I changed SPF for switch.ch to use SPF macros (RFC 7208). I wanted to use the "_spf" label but bind9 check-names complained with a "bad owner name (check-names)" message. I have now used "spf" instead of "_spf", e.g. exists:%{ir}.spf.switch.ch I didn't want to disable check-names for

Re: check-names conflicts with SPF macro definition

2021-01-04 Thread Mark Andrews
SPF records are TXT record which are NOT subject to check-names processing. If you created a seperate zone use nameservers that DO NOT live within the zone. ns1._spf.switch.ch is NOT a legal hostname as it is not LDH. > On 4 Jan 2021, at 20:01, Daniel Stirnimann > wrote: > > Hello all, > > I

Re: check-names conflicts with SPF macro definition

2021-01-04 Thread Daniel Stirnimann
Hello Mark, the "exists" [1] macro results in A queries and the zone contains A records. That's why the check-names processing applied. Thanks for the hint regarding the nameserver hostnames. Daniel [1] https://tools.ietf.org/html/rfc7208#section-5.7 On 04.01.21 10:33, Mark Andrews wrote: > SP

Re: BIND through COPR after CentOS

2021-01-04 Thread Petr Menšík
Hello Bruce. Since this version is exactly the same piece what I am working on for RHEL, what would be advantage of using Oracle Linux for it? The same version would land to CentOS Stream and into Red Hat Enterprise Linux later. We try hard to make no regressions on any update. ISC's maintained t