Re: Using nsupdate in scripts

> On Mar 14, 2022, at 5:11 PM, Philip Prindeville > wrote: > > > >> On Mar 14, 2022, at 4:25 PM, Tony Finch wrote: >> >> Philip Prindeville wrote: >>> >>> But I've noticed that since I added the following to my options { }: >>> >>> allow-transfer { none; }; >>> dnssec-valid

Re: Using nsupdate in scripts

> On Mar 14, 2022, at 4:25 PM, Tony Finch wrote: > > Philip Prindeville wrote: >> >> But I've noticed that since I added the following to my options { }: >> >>allow-transfer { none; }; >>dnssec-validation auto; >>listen-on-v6 { none; }; >> >> That I get a *lot* of l

RE: [EXTERNAL] Re: NOTAUTH on dynamic update followed by approved update

Tony, Thank you for your detailed and thoughtfuly analysis. I think you are spot-on. I'm looking into the app that is sending those updates. And wahoo, I won a prize! That's awesome. -Original Message- From: Tony Finch Sent: Monday, March 14, 2022 4:23 PM To: Hellige, Charles D Cc: b

Re: Using nsupdate in scripts

Philip Prindeville wrote: > > But I've noticed that since I added the following to my options { }: > > allow-transfer { none; }; > dnssec-validation auto; > listen-on-v6 { none; } ; > > That I get a *lot* of lines like: > > ; Communication with ::1#53 failed: connection ref

Re: NOTAUTH on dynamic update followed by approved update

Hellige, Charles D wrote: > We have been using nsupdate for some time without issue. We recently > started seeing NOTAUTH failures in the named logs followed by successful > adding/deleting messages. The records are getting created but there are > times when we see several (NOTAUTH) errors befo