Petert Grotz - Obel und Partner GbR
2014-Aug-29 20:51 UTC
[Samba] samba Digest, Vol 140, Issue 52
Hello Louis,> Datum: Fri, 29 Aug 2014 15:17:44 +0200 > Von: "L.P.H. van Belle" <belle at bazuin.nl> > An: "samba at lists.samba.org" <samba at lists.samba.org> > Betreff: Re: [Samba] Samba 4 dns-resolv-prob with different subnets> pleast post your> /etc/hostson dc-01: 127.0.0.1 localhost localhost.localdomain 192.168.0.101 dc-01 dc-01.obel.lan on dc-02: 127.0.0.1 localhost localhost.localdomain 192.168.1.100 dc-02 dc-02.obel.lan> /etc/resolv.confon dc-02 192.168.1.100 (dns-resolution works): search obel.lan nameserver 192.168.1.100 nameserver 192.168.1.102 #def gateway on subnet 192.168.1.0 on dc-01 192.168.0.101 (dns-resolution doesn?t work): search obel.lan nameserver 192.168.1.100 nameserver 192.168.0.101 nameserver 192.168.0.102 #def gateway on subnet 192.168.0.0> which OS ( debian/ubuntu/centos)centos 6.5> the output of smbd -Vsernet-samba 4.1.11> samba internal DNS or Bind9_DLZsamba internal> and what if you use the FQDN of the DC-02 and not the hostname.using FQDN on DC-02 where the first samba-dc was installed is working fine with all resolving, using FQDN on DC-01 gives me the described errors> and you can add in the /etc/resolv.conf and extra search like> search internal.domain.tld someotherinternal.domain.tld. > nameserver ...doesn?t help :(> which nameserver is use the server on the 192.168.1.0 net > and is this net also defined on the samba 4 DC nameserver.192.168.1.0 is using the samba internal dnsserver and is working fine even for the dns-entries from the 192.168.0.0-subnet. for dc-01 at 192.168.0.0 there are only the resolv.conf-entries because joining the dc-01 into domain will only success when dns/kerberos can resolv the working dc-02 on the other subnet where the domain is working at the moment.> Greetz,> LouisThanks again! Peter