[Samba] DLZ Backend DNS Hosed
L.P.H. van Belle
belle at bazuin.nl
Wed Jun 19 06:48:41 UTC 2019
For bind, please to add this for bind if you use bind_DLZ.
How : systemctl edit bind9, or create the file manualy and run systemctl daemon-reload after.
The edit command already does the reload.
But same for you. ;-) as the other list message today. ([Samba] Reverse DNS)
Can you run this for me on the DC's.
And post the output
It tells me almost all i need to know to help you fix this.
> -----Oorspronkelijk bericht-----
> Van: samba [mailto:samba-bounces at lists.samba.org] Namens
> Matthew Delfino via samba
> Verzonden: woensdag 19 juni 2019 5:00
> Aan: samba at lists.samba.org
> Onderwerp: [Samba] DLZ Backend DNS Hosed
> I'm in trouble here with what appears to be a total meltdown
> of my DNS on my Domain Controllers.
> I only have two DCs right now and I cannot resolve anything
> on either of them. I am on Ubuntu 16.04 with a compiled
> version of Samba 4.10.4.
> I also have a compiled version of BIND 9.10.3-P4-Ubuntu <id:ebd72b3>
> # service bind9 status
> ??? bind9.service - BIND Domain Name Server
> Loaded: loaded (/lib/systemd/system/bind9.service;
> enabled; vendor preset: enabled)
> Drop-In: /run/systemd/generator/bind9.service.d
> Active: failed (Result: exit-code) since Tue 2019-06-18
> 21:14:39 CDT; 27min ago
> Docs: man:named(8)
> Process: 28347 ExecStop=/usr/sbin/rndc stop (code=exited,
> Process: 28329 ExecStart=/usr/sbin/named -f $OPTIONS
> (code=exited, status=1/FAILURE)
> Main PID: 28329 (code=exited, status=1/FAILURE)
> Jun 18 21:14:39 cordelia named: samba_dlz: starting configure
> Jun 18 21:14:39 cordelia named: zone
> mydomain.com/NONE: has no NS records
> Jun 18 21:14:39 cordelia named: samba_dlz: Failed to
> configure zone 'mydomain.com'
> Jun 18 21:14:39 cordelia named: loading configuration: bad zone
> Jun 18 21:14:39 cordelia named: exiting (due to fatal error)
> Jun 18 21:14:39 cordelia systemd: bind9.service: Main
> process exited, code=exited, status=1/FAILURE
> Jun 18 21:14:39 cordelia rndc: rndc: connect failed:
> 127.0.0.1#953: connection refused
> Jun 18 21:14:39 cordelia systemd: bind9.service: Control
> process exited, code=exited status=1
> Jun 18 21:14:39 cordelia systemd: bind9.service: Unit
> entered failed state.
> Jun 18 21:14:39 cordelia systemd: bind9.service: Failed
> with result 'exit-code'.
> It appears that somehow I lost my NS records for one of my
> zones. It seems that I cannot get BIND up long enough to edit
> I've been able to delete my non-essential zones with samba-tool:
> # samba-tool dns zonedelete localhost mydomain.com
> # samba-tool dns zonedelete localhost 7.168.192.in-addr.arpa
> # samba-tool dns zonedelete localhost 3.168.192.in-addr.arpa
> # samba-tool dns zonedelete localhost 2.168.192.in-addr.arpa
> # samba-tool dns zonedelete localhost 11.168.192.in-addr.arpa
> # samba-tool dns zonedelete localhost 5.168.192.in-addr.arpa
> But now my error is "zone _msdcs.samdom.mydomain.net/NONE:
> has no NS records" and I am real nervous to delete that zone.
> Does anyone know what I can do to get my samba DC to have NS
> records that my BIND DNS server will understand and therefore load?
> © 2019 KNOCK, inc. All rights reserved. KNOCK is a registered
> trademark of KNOCK, inc. This message and any attachments
> contain information, which is confidential and/or privileged.
> If you are not the intended recipient, please refrain from
> any disclosure, copying, distribution or use of this
> information. Please be aware that such actions are
> prohibited. If you have received this transmission in error,
> kindly notify the sender by e-mail. Your cooperation is appreciated.
> To unsubscribe from this list go to the following URL and read the
> instructions: https://lists.samba.org/mailman/options/samba
More information about the samba