search for: ip_of_dc2

...t this, by setting the ip of dc, it really helps in the long run. So in my optinion, dont use localhost, use the ip of the DC itself for any regular DC of Member setup. I like to do it as followed. At install time, 2+ DC.s DC1 nameserver IP_OF_DC_FSMO. DC2 nameserver IP_OF_DC_FSMO. nameserver IP_OF_DC2 DC3 nameserver IP_OF_DC_FSMO. nameserver IP_OF_D3 When finished installing/configuring the DC, reboot 1-2 times, if everthing is still ok, think here in tests with dbcheck replications etc, now change the resolv.conf again ( see below), reboot and check again. DC1 nameserver IP_OF_DC_FSMO....

...lv.conf search ADDC.domain.TLD externaldomain.tld nameserver IP_OF_DC1 and not localhost/127.0.0.1 Nameserver IP_of_your_gateway Nameserver IP_of_anyother_dns. Now adding a second DC. DC1 changes a bit. /etc/resolv.conf search ADDC.domain.TLD externaldomain.tld nameserver IP_OF_DC1 nameserver IP_OF_DC2 Nameserver IP_of_anyother_dns. DC2. /etc/resolv.conf search ADDC.domain.TLD externaldomain.tld nameserver IP_OF_DC2 nameserver IP_OF_DC1 Nameserver IP_of_anyother_dns. And set you client PC's DNS to the DC.s Results in. 1) if DC1 is down, DC2 is used. 2) if DC2 is down, DC1 is used. 3)...

Mandi! Rowland Penny via samba In chel di` si favelave... > Try reading this: > http://www.itgeared.com/articles/1046-dns-client-settings-for-active/ I try to summarize. ''To be a DC'', servers have to add/update some DNS record. If you have a single DC, there's no choice. ;-) If you have more than a DC, you have to pay attention to have as DNS not the DC itself

...this is a server which is doing a client resolving request through dns services. ( port 53 ) In case of 2 DCs. Before the join of second DC, point the resolv.conf to DC1. After the join of the second DC, and after the reboot of the server, this changes a bit. Change resolve.conf to Nameserver IP_OF_DC2 ( NOT LOCALHOST ) ! Nameserver IP_OF_DC1 (optional add a internet DNS server, if both DC's fail you server can still use the internet ) DC1 should now have Nameserver IP_OF_DC1 ( NOT LOCALHOST ) ! Nameserver IP_OF_DC2 (optional add a internet DNS server, if both DC's fail you s...

hi! Query, I have 3 DCs, in each of the servers should have configured the other two DCs in the resolv.conf? or with only the primary is enough? Maybe that's my problem that does not replicate the dc3 with the dc2 thanks to all!

...any server should always resolv first to the ADDC dns which contains domain controller locator CNAME record for all the other domain controllers in the root.   Second ADDC Server. search ad-dc-subdom.domain.tld ( and maybe others to search.) nameserver IP_OF_DC1_AND_NOT_127.0.0.1 nameserver IP_OF_DC2_AND_NOT_127.0.0.1   --------------------- In a 3 DC server setup, or more. First Server. ( primary with fsmo roles ) search ad-dc-subdom.domain.tld ( and maybe others to search.) nameserver IP_OF_DC1_AND_NOT_127.0.0.1 ( optional add DC2 and/or DC3 IP)   Second ADDC Server. search ad-dc...

...ins > > domain controller locator CNAME record for all the other domain > controllers in the root. > >   > > Second ADDC Server. > > search ad-dc-subdom.domain.tld ( and maybe others to search.) > > nameserver IP_OF_DC1_AND_NOT_127.0.0.1 > > nameserver IP_OF_DC2_AND_NOT_127.0.0.1 > >   > > --------------------- > > In a 3 DC server setup, or more. > > First Server. ( primary with fsmo roles ) > > search ad-dc-subdom.domain.tld ( and maybe others to search.) > > nameserver IP_OF_DC1_AND_NOT_127.0.0.1 > > (...

Hi Rowland, many thanks for your help, On Wed, Nov 08, 2017 at 11:00:59AM +0000, Rowland Penny wrote: > > On Wed, 8 Nov 2017 11:18:10 +0100 > Ervin Hegedüs <airween at gmail.com> wrote: > > > > ======== > > open-ldap: ... > > -------- > > /etc/resolv.conf > > search core.mydomain.hu > > nameserver 127.0.0.1 > > nameserver

On Mon, 15 Aug 2016 16:02:38 +0100 Rowland Penny via samba <samba at lists.samba.org> wrote: > > OK, this has nothing to do with the classicupgrade, I have setup a > couple of VMs and provisioned a test DC in one and joined another DC > in the other. > > I am now at the point the OP is at, samba_dnsupdate cannot add the > required records, all I get in log.samba is