Re: Using nsupdate in scripts

On 3/14/2022 3:11 PM, Philip Prindeville wrote: I was hoping that there's a trivial way to parse the named.conf file and figure out what it listens on for updates using a Bind utility, but I guess not... The utility 'rndc status' will return the full path of the configuration file: rndc

Re: Using nsupdate in scripts

Philip Prindeville wrote: > > I'm operating on a residential ILEC that hasn't deployed IPv6, so > turning off IPv6 isn't "self-harm", it's what cyber security > professionals refer to as "reducing attack surface". Sorry, that was unkind of me, and it's a topic I should not be sarcastic about. It

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: 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

Using nsupdate in scripts

Hi all, I have some scripting that generates zone files for RFC-1918 addresses for the DHCP static reservations when isc-dhcp starts up on OpenWRT: https://github.com/openwrt/packages/blob/master/net/isc-dhcp/files/dhcpd.init#L551-L583 I push the single monolithic file over here: https://githu