similar to: reslov.conf on two DC's

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,

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

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,

Hello, what IP(s) should be set for each domain controller? If there are two should both have their own IP set in resolv.conf or should they have the IPs of both DCs? Or possibly just 127.0.0.1 on each DC? Second thing I had was that clients with DNS set to both DCs could not resolve a special host in the internet while the DNS forwarder can. I needed to restart DCs to get it work again. Thanks

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.

So in my ears it makes sense to add this to the wiki for joining a domain as a DC. I will add it soon. Am 12. M?rz 2015 11:00:21 MEZ, schrieb "L.P.H. van Belle" <belle at bazuin.nl>: > >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

It would be nice to know what IPs the DCs have. BTW: I updated the wiki: https://wiki.samba.org/index.php/Join_a_domain_as_a_DC#Follow-Up_on_.2Fetc.2Fresolv.conf Am 12. M?rz 2015 14:30:34 MEZ, schrieb James <lingpanda101 at gmail.com>: >I have six. Three sites across wan links > >DC01 >nameserver 172.16.232.39 >nameserver 172.16.232.29 > >DC02 >nameserver

At one point, I thought the same. Tried a "sleep 5" and still got some failures. (That was before I started counting the fails.) This is a P4 3.2Ghz with 1Gb RAM. Could it be that sluggish (at that moment) and need a "sleep 10" or "sleep 15" or more? It worked on my VM (of course it is running on a multi-core Xeon processor so maybe a sleep?) I'm going to try

No. What I did was change the first few to see what happens. And still the first 13 (this time, last time 17) failed. I am baffled why the first 11 to 17 fail (randomly) and the remainder receive "Successfully granted rights." --- ------------------------- Bob Wooden of Donelson Trophy 615.885.2846 (main) www.donelsontrophy.com [1] "Everyone deserves an award!!" On

Louis, I ran your "1-setup-sernet-samba4-ADDC-wheezy.sh" script and noticed this (during install:) ==========SE Privileges =============================== Enter administrator's password: Could not connect to server 127.0.0.1 Connection failed: NT_STATUS_CONNECTION_REFUSED This is my /etc/resolv.conf: root at dc01:~# cat /etc/resolv.conf search dts***m.dt nameserver

I upped 1.0.4 of the script.. I added checks if no DC's are found, error message and exits script, so no python errors anymore, if i did it right. ;-) on both DC's do the following. and whats the output of : cat /etc/hosts cat /etc/resolv.conf and kinit Administrator SETDNSDOMAIN=`hostname -d` SETHOSTNAME=`hostname -s` SERVER_IP_ADRESS=`hostname -i` echo "Test domainname:

Thanks Rowland but that idea did not work. I will simply grant access to those that failed manually. (Really wish I had kept the VM that the scripthad worked on so I could go back and see what happened but, too late, I have already deleted to save precious hard drive space.) If I have any issues, I'll be back. --- ------------------------- Bob Wooden of Donelson Trophy 615.885.2846

Here yau go: root at dc01:~# cat /etc/bind/named.conf.options // Defined ACL Begin acl thisserverip { 192.168.16.54; }; acl all-networks { 192.168.16.0/24; }; // Defined ACL End options { directory "/var/cache/bind"; version "0.0.7"; // If there is a firewall between you and nameservers you want // to talk to, you may need to fix the firewall to allow multiple //

On 2015-01-09 08:44, Rowland Penny wrote: > On 09/01/15 14:34, Bob of Donelson Trophy wrote: > Now, more appropriately answering after the message. SEE BELOW, please. On 2015-01-09 07:24, L.P.H. van Belle wrote: Hai, Not entiraly correct.. change : dns-nameservers 208.67.222.222 <<<<<< have always struggled to dns-search dtshrm.lan dns-nameservers IP_OF_AD_DC and use :

Moved the hdd of my DC over to nicer P4 machine. It started as expected. (I have resolved the eth0 driver issue that happens with Debian/Ubuntu servers when you move a functional hdd to a different machine.) Then I decided to change the static ip address of the DC from 192.168.**.54 to 192.168.**.51. That went as expected, except it seems my W7 client cannot connect to my domain, now. It says

Sent the following only to Rowland by mistake. Forgive me O' fearless leader of mailing list. My bad. --- ------------------------- Bob Wooden of Donelson Trophy 615.885.2846 (main) www.donelsontrophy.com [1] "Everyone deserves an award!!" -------- Original Message -------- SUBJECT: Re: [Samba] Samba_internal dns Ubuntu 14.04.1LTS DATE: 2014-11-07 09:32

On 05/01/15 14:04, Bob of Donelson Trophy wrote: > > > My shop is 10 minutes from my house. House and shop are connected by vpn > (between two IpFire firewalls.) I do a lot of configuring and testing > from home. Due to a Windows wake-on-lan issue (right now) I cannot wake > the lone DC W7 client from home. When I get to work this morning, W7 > client (thru ADUC) shows

Now, more appropriately answering after the message. SEE BELOW, please. On 2015-01-09 07:24, L.P.H. van Belle wrote: > Hai, > > Not entiraly correct.. > > change : > >> dns-nameservers 208.67.222.222 <<<<<< have always struggled > > to > dns-search dtshrm.lan > dns-nameservers IP_OF_AD_DC > > and use : > net rpc rights

Thanks Rowland. Being the novice that I am, I thought the line would 'pickup' my DOMAIN and replace the ${SAMBA_NT_DOMAIN}. So, I just tried the line correctly and it asked for my Administrator password and subsequently granted access. At least I know I can go and correct manually, if I need too. My /etc/resolv.conf is: root at dt01:~# cat /etc/resolv.conf search dts***m.dt

I did a fresh install of Debian with the desktop. I know from Ubuntu that the network is handled differently in the desktop and the server versions. So, I am assuming it is a similar situation with Debian. I could be wrong but . . . When kerberos installs via the script it (the script) suggests accepting the 'defaults on the next three screens.' The first screen included the correct