Displaying 3 results from an estimated 3 matches for "ip_ad".
Did you mean:
ip_a
2019 Jun 21
0
DLZ Backend DNS Hosed
No, this is not needed.
Solution here in this is simple.
search primary.domain.tld # optional extra search domains after the primary.
nameserver IP_AD-DC_OF_THIS_SERVER_FIRST
nameserver IP_AD-DC_others
Run : samba_upgradedns --dns-backend=BIND9_DLZ
And your done, all needed records are fixed/updated.
This goes wrong if the IP of the running server isnt the first and/or if search is setup wrong.
So always keep ip of the server itself as firs...
2019 Jun 21
1
DLZ Backend DNS Hosed
..."samba at lists.samba.org" <samba at lists.samba.org>
Sent: 6/21/2019 5:15 AM
Subject: Re: [Samba] DLZ Backend DNS Hosed
No, this is not needed.
Solution here in this is simple.
search primary.domain.tld # optional extra search domains after the primary.
nameserver IP_AD-DC_OF_THIS_SERVER_FIRST
nameserver IP_AD-DC_others
Run : samba_upgradedns --dns-backend=BIND9_DLZ ?
And your done, all needed records are fixed/updated.
This goes wrong if the IP of the running server isnt the first and/or if search is setup wrong.
So always keep ip of the server itself...
2019 Jun 20
4
DLZ Backend DNS Hosed
I've been working on this problem for a few hours. Here are some updates:
Many of the domains I listed are duplicates of domains managed by other DNS servers on my network. There was no point in having them in Samba AD, so I deleted the zones in Windows DNS Manager and created slaves in my named.conf.local folder, so that they'd pull the records from my authoritative BIND DNS server,