similar to: Recurrent DNS issues after DC loss

On 05.06.2018 20:39, lingpanda101 wrote: > On 6/5/2018 2:11 PM, Ole Traupe via samba wrote: >> Hi list, >> >> I have a domain in production on two sites (subnets, via "Sites and >> Services") with originally two DCs. One went down due to HDD (-> old >> hardware) error. Now, occasionally, clients cant access/find the file >> server (domain

On 6/6/2018 4:54 AM, Ole Traupe via samba wrote: > > > On 05.06.2018 20:39, lingpanda101 wrote: >> On 6/5/2018 2:11 PM, Ole Traupe via samba wrote: >>> Hi list, >>> >>> I have a domain in production on two sites (subnets, via "Sites and >>> Services") with originally two DCs. One went down due to HDD (-> old >>> hardware)

On 06.06.2018 16:02, Rowland Penny via samba wrote: > >> I seem to remember having read here on the list, that it is no good >> idea to mix samba versions in a domain. If there is sound advice to >> do it anyways, I would be up for trying it. However, as I have >> written above, I messed up the uid/gid ranges. To my understanding, >> later versions of Samba (like

On 06.06.2018 14:44, lingpanda101 wrote: > >> ** SNIP ** >> >> Actually, the DCs (resolv.conf) were pointing to each other >> initially, and I think that was at least one root of the evil. I >> think this advice in the Samba wiki actually is rather bad (and >> unnecessary with Samba, as has been pointed out, before?). > Using Bind I find it's

On 06.06.2018 21:54, lingpanda101 wrote: > On 6/6/2018 11:02 AM, Ole Traupe via samba wrote: >> >> >> On 06.06.2018 16:02, Rowland Penny via samba wrote: >>> >>>> I seem to remember having read here on the list, that it is no good >>>> idea to mix samba versions in a domain. If there is sound advice to >>>> do it anyways, I would be

On 06.06.2018 16:48, Rowland Penny via samba wrote: > It doesn't say that any more ;-) > > This is from my DCs > > root at dc4:~# cat /etc/resolv.conf > search samdom.example.com > nameserver 192.168.0.6 > root at dc4:~# hostname -i > 192.168.0.6 > > root at dc3:~# cat /etc/resolv.conf > search samdom.example.com > nameserver 192.168.0.7 > root at

On 06.06.2018 16:02, Rowland Penny via samba wrote: > > On your DC, set the AD DNS domain in the domain and the IP of your DC in the nameserver parameter of the /etc/resolv.conf file. For example: > > domain samdom.example.com > nameserver 10.99.0.1 So "domain" and not "search"? I had "search" set due to the result of some discussion on the list.

On 6/5/2018 2:11 PM, Ole Traupe via samba wrote: > Hi list, > > I have a domain in production on two sites (subnets, via "Sites and > Services") with originally two DCs. One went down due to HDD (-> old > hardware) error. Now, occasionally, clients cant access/find the file > server (domain member). This does not occur on all clients at the same > time,

On 6/6/2018 10:02 AM, Rowland Penny via samba wrote: > On Wed, 6 Jun 2018 15:40:48 +0200 > Ole Traupe via samba <samba at lists.samba.org> wrote: > >> >> On 06.06.2018 14:44, lingpanda101 wrote: >>>> ** SNIP ** >>>> >>>> Actually, the DCs (resolv.conf) were pointing to each other >>>> initially, and I think that was at

On 6/6/2018 11:02 AM, Ole Traupe via samba wrote: > > > On 06.06.2018 16:02, Rowland Penny via samba wrote: >> >>> I seem to remember having read here on the list, that it is no good >>> idea to mix samba versions in a domain. If there is sound advice to >>> do it anyways, I would be up for trying it. However, as I have >>> written above, I messed

On 6/6/2018 10:26 AM, Ole Traupe via samba wrote: > > > On 06.06.2018 16:02, Rowland Penny via samba wrote: >> >> On your DC, set the AD DNS domain in the domain and the IP of your DC >> in the nameserver parameter of the /etc/resolv.conf file. For example: >> >> domain samdom.example.com >> nameserver 10.99.0.1 > > So "domain" and not

On 6/6/2018 10:55 AM, Ole Traupe via samba wrote: > > > On 06.06.2018 16:48, Rowland Penny via samba wrote: >> It doesn't say that any more ;-) >> >> This is from my DCs >> >> root at dc4:~# cat /etc/resolv.conf >> search samdom.example.com >> nameserver 192.168.0.6 >> root at dc4:~# hostname -i >> 192.168.0.6 >> >>

On Wed, 6 Jun 2018 15:40:48 +0200 Ole Traupe via samba <samba at lists.samba.org> wrote: > > > On 06.06.2018 14:44, lingpanda101 wrote: > > > >> ** SNIP ** > >> > >> Actually, the DCs (resolv.conf) were pointing to each other > >> initially, and I think that was at least one root of the evil. I > >> think this advice in the

On Wed, 6 Jun 2018 10:25:43 -0400 lingpanda101 <lingpanda101 at gmail.com> wrote: > On 6/6/2018 10:02 AM, Rowland Penny via samba wrote: > > On Wed, 6 Jun 2018 15:40:48 +0200 > > Ole Traupe via samba <samba at lists.samba.org> wrote: > > > >> > >> On 06.06.2018 14:44, lingpanda101 wrote: > >>>> ** SNIP ** > >>>> >

On Wed, 6 Jun 2018 16:26:53 +0200 Ole Traupe via samba <samba at lists.samba.org> wrote: > > > On 06.06.2018 16:02, Rowland Penny via samba wrote: > > > > On your DC, set the AD DNS domain in the domain and the IP of your > > DC in the nameserver parameter of the /etc/resolv.conf file. For > > example: > > > > domain samdom.example.com >

On Thu, 7 Jun 2018 13:51:16 +0200 Ole Traupe via samba <samba at lists.samba.org> wrote: > > I will try to find that section again. At first glance, I did not > find this information in patch notes 4.3-4.5. But I seem to remember > having read that, and I also remember a conversion with Rowland a > while ago leaving me with the impression that having different > (lower)

Thank you for hint to this VBS script. In fact I alraedy saw it but I'm not too confident in my VB knowledge, so I didn't use that script, prefering rely on Samba command and shell scripts to work around issues. You spoke about SOA record which wasn't changed, same here. There is another DNS record I had to change: _ldap._tcp.pdc._msdcs.samba.domain.tld. I spoke about removing

On 10/30/2015 9:19 AM, Ole Traupe wrote: > > > Am 30.10.2015 um 13:33 schrieb James: >> On 10/29/2015 9:56 AM, Ole Traupe wrote: >>> >>> >>> Am 29.10.2015 um 14:37 schrieb James: >>>> On 10/29/2015 9:15 AM, Ole Traupe wrote: >>>>> >>>>> >>>>> Am 29.10.2015 um 13:54 schrieb mathias dufresne:

Hi, I played with demote recently on a test AD domain composed with Samba version 4.3.0 and 4.3.1. I demoted all version 4.3.0. I was facing same issue as you. I written long mails here to explain how I managed that. My DNS looks clear now. Today I played with AD sites and I found in default sites all demoted DC. They weren't removed from DNS DB nor here. For now I have no idea how to get

On 10/29/2015 9:56 AM, Ole Traupe wrote: > > > Am 29.10.2015 um 14:37 schrieb James: >> On 10/29/2015 9:15 AM, Ole Traupe wrote: >>> >>> >>> Am 29.10.2015 um 13:54 schrieb mathias dufresne: >>>> Thank you for hint to this VBS script. In fact I alraedy saw it but >>>> I'm not >>>> too confident in my VB knowledge, so