Re: How to print details of dns_name_t* when hitting a gdb breakpoint in dns_name_equal

On 04. 12. 24 17:31, Kees Bakker wrote: On 03-12-2024 15:56, Petr Špaček wrote: On 03. 12. 24 11:36, Kees Bakker via bind-users wrote: I have a CentOS FreeIPA setup with with multiple named (bind9 9.16.23) servers. On two of my five servers, when I start named it fails a REQUIRE in dns_name_equ

Re: How to print details of dns_name_t* when hitting a gdb breakpoint in dns_name_equal

Kees, I would suggest to ask your supplier to fix this. 9.16.23 is not only on the 9.16 EOL branch, but it is not even latest 9.16 release[*]. That would be 9.16.50, chances are that your issue has been already fixed. Or it is caused by the dyndb-ldap plugin. Debugging 9.16.23+pile_of_patches

Re: How to print details of dns_name_t* when hitting a gdb breakpoint in dns_name_equal

On 03-12-2024 15:56, Petr Špaček wrote: On 03. 12. 24 11:36, Kees Bakker via bind-users wrote: I have a CentOS FreeIPA setup with with multiple named (bind9 9.16.23) servers. On two of my five servers, when I start named it fails a REQUIRE in dns_name_equal /*   * Either name1 is absol

Re: Zones list mask or wildcard

If nothing else works, you can always 'include' a file that contains configuration stanzas of those zones and then use a script to add new zone stanzas to the file. # Include config file with thousands of domains include "/etc/named.d/1000s_domains.conf"; The script could either recreate the