Bug 13945 - Bind DLZ missing NS records for zones added with samba-tool
Summary: Bind DLZ missing NS records for zones added with samba-tool
Status: NEW
Alias: None
Product: Samba 4.1 and newer
Classification: Unclassified
Component: DNS plugin (BIND DLZ) (show other bugs)
Version: 4.10.3
Hardware: All Linux
: P5 regression (vote)
Target Milestone: ---
Assignee: Amitay Isaacs
QA Contact: Samba QA Contact
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-05-14 14:33 UTC by Isaac Gómez
Modified: 2021-04-23 04:25 UTC (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Isaac Gómez 2019-05-14 14:33:52 UTC 
Good day,

I would like to report a regression introduced by the commit https://gitlab.com/samba-team/samba/commit/526c6d0be53d97beb38f82a3619d8710fefb4091 on the bind9_dlz plugin, after this commit the additional DNS zones added on the DNS tool from RSAT are not loaded in bind9, it crash because the zone has no NS records, I use BIND9 version 9.12.4 and Samba 4.10.2, I reversed the patch from that commit and bind9 loads again the zones but is not a writable zone as in bug  https://bugzilla.samba.org/show_bug.cgi?id=13841, at least is not crashing and serving all the zones.

For example I have the domain zone ad.domain.tld but I also have autoconfig.domain.tld, internal.domain.tld, etc zones, those zone are not loaded by Bind9.

Thank you.
Comment 1 Isaac Gómez 2019-05-24 20:07:39 UTC 
I found that only the old zones that were added with samba-tool were missing the NS record. I tested version 4.10.3 and recreated conflicted zones with DNS tool from RSAT and now it shows NS records.
Comment 2 Douglas Bagnall 2021-04-23 04:25:34 UTC 
Isaac: thanks for the analysis.

Can you still reproduce this?