dnssec not automatically updating on 1 server

Anybody have any ideas on why my dnssec records don't always automatically update on my NS2 authoritative server? On my NS1 authoritative server the records update without issue. NS2 is an exact copy of NS1. We SCP all of the config files from the first server to the second server and do "rndc

9.18 BIND not iterated over all authoritative nameservers

Hello, At this point I am hoping that somebody might have a workaround so that we can exclude domains from this behavior if they are broken on the far end. Does anybody have a workaround for this? We are a small ISP and run BIND compiled from source. We currently run 9.16.x Every time we try to

RE: 9.18 BIND not iterated over all authoritative nameservers

to be IDENTICAL. This is not a new requirement. It has been this way since the very beginning. The bank needs to fix what they publish. Mark On 28 Oct 2023, at 02:36, Michael Martinell via bind-users mailto:bind-users@lists.isc.org>> wrote: Hello, At this point I am hoping that somebod

dnnsec ipv6 reverse zone configuration

Hello, hoping somebody might have some insight into the errors I am seeing on ipv6 dnssec records. I am just starting to roll out dnssec on my reverse zones and have started with IPv6 on the record that contains just our ns2.itctel.com and dns2.itctel.com records. Our IPv4 forward zones are wor

RE: dnnsec ipv6 reverse zone configuration

With DNSSEC or QNAME minimisation you cannot miss intermediate zones. Mark > On 31 Oct 2024, at 00:31, Michael Martinell via bind-users > wrote: > > Hello, hoping somebody might have some insight into the errors I am seeing on > ipv6 dnssec records. > I am just starting to rol