similar to: resolv.conf setup and DNS issue

So if i did read right . .. In my case.. I have 2 DC ( with bind9 dns DLZ ) and i have 2 proxy servers with DNS (bind9) slaves for the DC's. I should point my /etc/resolv.conf of the DC's also to the slave dns servers? and in case of just 2 dc's without slave dns servers, point the DC1 to DC2 dns and DC2 to DC1 dns ? If thats the case i have to change my scripts ;-) Greetz,

On 30/01/15 19:05, Tim wrote: > I'm happy to see that our "samba pros" do not share the same point of view. :-) > > In Marcs link, as far as I can see, number 3 points to Rowlands solution while number 2 seems to be Marcs preferred solution. > > Today I changed DNS settings on my DCs to Rowlands solution (127.0.0.1) and an issue I had with sysvolcheck seems to gone.

On 11/03/15 18:01, James wrote: > Bob, > > Take a look at the following two links. > > http://retrohack.com/a-word-or-two-about-dns-islanding/ > > http://blogs.technet.com/b/askds/archive/2010/07/17/friday-mail-sack-saturday-edition.aspx#dnsbest > > I have more than two DC's but generally I would have each one point at > the other. > > I tried that,

When running two DC's is the recommended practice for the first DC to resolve to itself, like this: first DC /etc/resolv.conf file: search samdom.tld nameserver [DC1 ip address] nameserver 127.0.0.1 And on second DC to both DC1 and DC2, like this: search samdom.tld nameserver [DC1 ip address] nameserver [DC2 ip address] nameserver 127.0.0.1 Or is the incorrect? --

I'm happy to see that our "samba pros" do not share the same point of view. :-) In Marcs link, as far as I can see, number 3 points to Rowlands solution while number 2 seems to be Marcs preferred solution. Today I changed DNS settings on my DCs to Rowlands solution (127.0.0.1) and an issue I had with sysvolcheck seems to gone. So what best practise does the samba team have?

Hi! I have a question about order in dcs is /etc/resolv.conf , my configuration: DC01: /etc/resolv.conf IP DC02 IP DC01 DC02 /etc/resolv.conf IP DC01 IP DC02 https://wiki.samba.org/index.php/Joining_a_Samba_DC_to_an_Existing_Active_Directory#DNS_Configuration_on_Domain_Controllers --- However this setting causes the error: samba_dnsupdate --verbose --all-names dns_tkey_negotiategss:

Mandi! Rowland Penny via samba In chel di` si favelave... > If the first IP in /etc/resolv.conf isn't the DCs own, samba_dnsupdate > will connect to the other DC and use its kerberos key and, > surprise,surprise, it doesn't work. The wiki page was written to > prevent 'islanding', the only problem with that is, you don't get > 'islanding' on an AD DC.

a nice example about dns islanding. http://retrohack.com/a-word-or-two-about-dns-islanding/ and with only 2 dc's setup the resolv.confs like : DC01 Primary DNS 10.1.1.2 Secondary DNS 127.0.0.1 DC02 Primary DNS 10.1.1.1 Secondary DNS 127.0.0.1 http://technet.microsoft.com/en-us/library/ff807362%28v=ws.10%29.aspx says: If the loopback IP address is the first entry in the list of

Hai eveyone.   I know about the dns "things" in the past. DNS Islanding problems etc. This one is a bit hijacking the subject : “Horrible BIND9_DLZ DNS breakage after DC replaced and samba-tool domain demote --remove-other-dead-server”     I would like to suggest a smale change in how we suggest to setup samba ADDC dns things, and i do think this help in the setup of the AD

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

Hi, Following DNS configuration of multiple DCs recommended on the wiki https://wiki.samba.org/index.php/Joining_a_Samba_DC_to_an_Existing_Active_Di rectory#DNS_Configuration_on_Domain_Controllers , clients are unable to open windows shares based on the server IP, for example \\133.1.1.24 . However they work fine opening either the netbios name or the DNS name, for example \\FILESERVER1 or

Hi Marc, I appreciate that you reply, but I got it resolved by following the advice of Mathias. I was aware of the links below, however the first is about using the BIND9_DLZ backend, and at the time I experienced the issue I was using the internal one. Marc & Mathias, The 2nd link that Marc references is about a DC should not use itself for DNS queries is exactly the opposite of your

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

On 11/30/2016 8:09 AM, Rowland Penny via samba wrote: > On Wed, 30 Nov 2016 13:17:18 +0100 > Izan Díez Sánchez via samba <samba at lists.samba.org> wrote: > >> Hi, >> >> Following DNS configuration of multiple DCs recommended on the wiki >> https://wiki.samba.org/index.php/Joining_a_Samba_DC_to_an_Existing_Active_Di >>

All, I configured two DCs (Samba version 4.5.5) replicating ad.corp.com in two sites ( https://wiki.samba.org/index.php/Active_Directory_Sites) Following 'DNS configuration on Domain Controllers' section from this wiki https://wiki.samba.org/index.php/Joining_a_Samba_DC_to_an_Existing_Active_Directory If I configure nameserver DC1 to be the first resolver for DC2, samba_dnsupdate

Hello you all, this is a bit OT but I think I'll find some people here that can help. We have 4 DCs all on the same site. This is working fine. 3 Are VMs one is a physical server. They are the only DNS servers in that network. On a member server running our icinga2 installation I have this in the resolv.conf: options rotate timeout:2 retries:1 search example.com nameserver x.x.x.x (ip dc1)

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!

On 2016-12-01 10:00, Rowland Penny via samba wrote: > On Thu, 01 Dec 2016 09:20:15 -0600 > Bob of Donelson Trophy via samba <samba at lists.samba.org> wrote: > >> From: Bob of Donelson Trophy via samba <samba at lists.samba.org> >> To: SAMBA MailList <samba at lists.samba.org> >> Subject: [Samba] member server resolv.conf question >> Date: Thu,

How many supported DNS IP addresses maybe configured in /etc/resolv.conf ? Is it only 3, or can I configure more? -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.centos.org/pipermail/centos/attachments/20050602/ccaa18ee/attachment-0004.html>

I dont understand whats the question here. But what i can say about the resolv.conf settings if you have multiple dc's. You have to think in 2 DNS resolving settings. 1) on the server as client resolving ( resolv.conf ) 2) clients resolving ( DNS Services ) The difference explained. If i do : ping hostname this is a server which is doing a client dns request through resolve.conf