Re: Accidentally ran rndc-confgen on a working BIND box

>From the ARM, when "rndc-confgen -a" is run:: > This option sets automatic rndc configuration, which creates a file rndc.key in /etc (or a different sysconfdir specified when BIND was built) that is read by both rndc and named on startup. The rndc.key file defines a default command channel and auth

RE: Accidentally ran rndc-confgen on a working BIND box

Thanks for the quick response! I ran “sudo rndc status” on the box in question and on a test VM that’s configured almost identically to the box in question. Both had very similar output. Here’s the output from the box in question: version: BIND 9.18.28-0ubuntu0.22.04.1-Ubuntu (Extende

Re: Accidentally ran rndc-confgen on a working BIND box

Trying using rndc to see if it's broke. rndc status You may need to add a path to the rndc binary if it's not in your $PATH env vars. Or maybe -c to the location of your rndc config. In your named.conf you should have a rndc statement with the key name and value. You can recreate your rndc co

Accidentally ran rndc-confgen on a working BIND box

I've been running BIND on Ubuntu 22.04 for over a year and it has been running perfectly as my primary DNS server. I'm currently using BIND 9.18.28. I'm currently setting up BIND on another box (as a secondary DNS server) and accidentally just ran "sudo rndc-confgen -a" on the first box. From

Re: notify IPv6

> On 24. 11. 2024, at 13:10, James wrote: > > Is this my mistake or bind's? Hard to tell since you have provided virtually no information in your email. You need to share the configuration and the logs for the start if you want the community help. Ondrej -- Ondřej Surý — ISC (He/Him) My work

Re: notify IPv6

On 24/11/2024 13:43, Marco Moock wrote: If a name server has only an IPv6 address (no IPv4) I do not see the transfer and the data are not updated on the secondary. The documentation says "NOTIFY messages are sent to the name servers defined in the NS records for the zone" Try a zone transfer m

Re: notify IPv6

Am 24.11.2024 um 12:10:42 Uhr schrieb James: > If a name server has only an IPv6 address (no IPv4) I do not see the > transfer and the data are not updated on the secondary. The > documentation says "NOTIFY messages are sent to the name servers > defined in the NS records for the zone" Try a z

notify IPv6

Good afternoon, I am logging all zone transfers. I can see it transferring on IPv4 addresses. I can check the SOA index on the primary and secondaries to check for updates. If a name server has only an IPv6 address (no IPv4) I do not see the transfer and the data are not updated on the sec

Re: How do I make my bind recursively support edns

Hi again. In that case, Mark's guess was correct: ECS is only available in the subscription edition. To get this you must be a paying support customer of ISC. See this page for details: https://www.isc.org/support/ I hope that helps. Cheers, Greg On Sun, 24 Nov 2024 at 07:25, Duan Duan <1422807..