Re: Forwarded lookup failing on no valid RRSIG

2020-12-23 Thread Nicolas Bock
On Sun, Dec 20 2020, Mark Andrews wrote: >> On 21 Dec 2020, at 06:04, Matthew Pounsett wrote: >> >> >> >> On Fri, 18 Dec 2020 at 18:08, Nicolas Bock >> wrote: >> Thanks Mark. Am I correct then that I need to either convince the >> administra

Re: Forwarded lookup failing on no valid RRSIG

2020-12-18 Thread Nicolas Bock
SES aware. It > will need to be updated for you to validate through it. > > -- > Mark Andrews > > > On 19 Dec 2020, at 05:07, Nicolas Bock > wrote: > > > > Hi Mark, > > > > Thanks so much for the reply. I ran this command and am > > gett

Re: BIND through COPR after CentOS

2020-12-18 Thread Nicolas Bock
On Fri, Dec 18 2020, John Thurston wrote: > We have been using the ISC COPR packages for BIND on CentOS. With the > demise of CentOS, we (along with a few other people on the planet) need > to consider where we will move our applications. > > We have been completely happy with the packages provi

Re: Forwarded lookup failing on no valid RRSIG

2020-12-18 Thread Nicolas Bock
kQWXaBcBo//NUX2asBLus8S7sJ9BDxpGUAsS9o+TdRlq YkIHBA== > > ;; Query time: 0 msec > ;; SERVER: 127.0.0.1#53(127.0.0.1) > ;; WHEN: Fri Dec 18 12:38:34 AEDT 2020 > ;; MSG SIZE rcvd: 395 > > [beetle:~] marka% > > >> On 18 Dec 2020, at 11:36, Nicolas Bock wrote: >

Forwarded lookup failing on no valid RRSIG

2020-12-17 Thread Nicolas Bock
Hi, When I configure my named to forward to our corporate DNS servers (10.0.0.2 and 10.0.0.3), I end up getting error messages such as Dec 17 20:58:06 dns-server named[843946]: fetch: www.canonical.com/A Dec 17 20:58:06 dns-server named[843946]: fetch: com/DS Dec 17 20:58:06