search for: dns_configuration_on_domain_control

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: TKEY is unacceptable Failed nsupdate: 1 Failed update of 28 entries --- If you change to DC01 IP DC01 IP DC02 DC02 IP DC02 IP DC01 Problem does not exist. What would be the correc...

...o think it's unnecessary with Samba >>> however. > Just where does it say this ? > I will fix it Hi Rowland,     I'm referencing here under ' DNS Configuration on Domain Controller' https://wiki.samba.org/index.php/Joining_a_Samba_DC_to_an_Existing_Active_Directory#DNS_Configuration_on_Domain_Controllers "The following is a best practice for DNS configuration on domain controllers (DC): Set the local IP of a DC as secondary or tertiary|nameserver|entry in its|/etc/resolv.conf|file and use a different Active Directory (AD) DNS server IP from the forest as primary name server" It...

Il 29/11/2018 15:22, Rowland Penny via samba ha scritto: > On Thu, 29 Nov 2018 15:03:03 +0100 > "L.P.H. van Belle via samba" <samba at lists.samba.org> wrote: > >> You dns keytab looks strange, my be due to manual changes.. > It looks strange because there is one of these missing: > > 1 DNS/mysamba4dc.mydomain.com at MYDOMAIN.COM > > Could be cut &

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 \\FILESERVER1.domain.local Here it is what the article says: -----------------------------------...

...>>> however. > > Just where does it say this ? > > I will fix it > Hi Rowland, > >     I'm referencing here under ' DNS Configuration on Domain > Controller' > > https://wiki.samba.org/index.php/Joining_a_Samba_DC_to_an_Existing_Active_Directory#DNS_Configuration_on_Domain_Controllers > > "The following is a best practice for DNS configuration on domain > controllers (DC): > Set the local IP of a DC as secondary or tertiary|nameserver|entry in > its|/etc/resolv.conf|file and use a different Active Directory (AD) > DNS server IP from the forest as pr...

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 > 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 > \\FILESERVER1.domain.local > > Here it is what the article says: >...

...00 > 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 > > 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 > > \\FILESERVER1.domain.local > > > > Here it is w...

...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 >> 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 >> \\FILESERVER1.domain.local >> >> Here it is what th...

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