Re: consolidating Reverse Zones

2021-10-28 Thread Edwardo Garcia
I have looked twice, there is no whitespace in the zone file. If I change the conf file to present as a /16 it works fine, but we dont have the /16 so we cant use it this way in production. OK, we could, but that would be wrong because we are claiming dns of other parts of /16 we have no rights to.

Re: consolidating Reverse Zones

2021-10-28 Thread Edwardo Garcia
Wow, looks a right mess to be honest, might just have to leave it as is, less aggravation. Hard to understand why in 2021 almost 2022, we can't do something so simple in dns On Thu, Oct 21, 2021 at 9:49 PM Tony Finch wrote: > Edwardo Garcia wrote: > > > > I guess bind can not consolidate like

RHEL, Centos, Fedora rpm 9.16.22

2021-10-28 Thread Carl Byington via bind-users
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 https://www.five-ten-sg.com/mapper/bind contains links to the source rpm, and build instructions. This .src.rpm contains a .tar.gz file with the ARM documentation, so the rpm rebuild process does not need sphinx- build and associated dependencies.

Re: DNSSEC questions

2021-10-28 Thread Alessandro Vesely
On Thu 28/Oct/2021 09:34:42 +0200 Matthijs Mekking wrote: On 27-10-2021 18:48, Alessandro Vesely wrote: 3. The server produces new .signed and .signed.jnl files every day, which is inconvenient as the zone files directory is checked by tripwire.  Is that timing determined by the dnskey-ttl?  Wo

Re: DNSSEC questions

2021-10-28 Thread Matthijs Mekking
On 27-10-2021 18:48, Alessandro Vesely wrote: 3. The server produces new .signed and .signed.jnl files every day, which is inconvenient as the zone files directory is checked by tripwire.  Is that timing determined by the dnskey-ttl?  Would it be okay to set it to one month? The zone is sig