similar to: DNS Problems with Samba4.0.5

OK here's our setup, we're running pfSense as our firewall/router. We have a dual-WAN with a Comcast Business Gateway and another local ISP. We're running Samba 4.7.6 as the AD DC & Bind 9.9.4. Here's the issue, we just upgraded our Comcast service to a higher speed & they replaced the modem/gateway. Everything was working fine, before the modem swap. Once they did

Hello, I am trying to setup a samba4 AD dc in my network using smb-tool. Everything seems to work except DNS forwarding. If I query for the dc root at dc:~# nslookup dc.local.domain.it I get the correct answer: root at dc:~# nslookup dc Server:???????? aaa.bbb.ccc.ddd Address:??????? aaa.bbb.ccc.ddd#53 Name:?? dc.xxxx.yyyy.it Address: aaa.bbb.ccc.ddd but if I query for an external domain: root

Hi all, I'm new to samba : I've just installed it (version 4.0.5) on a 'fresh' Ubuntu 12.10 server (32 bit version), following the HOWTO we can find on the sambawiki. Everything is OK, up to the $ /usr/local/samba/bin/smbclient -L localhost -U% command (running as root) I get the following errors : NT_STATUS_CONNECTION_REFUSED, even if I replace % by Administrator... What am I

This is the configuration of smb.conf of  the DC is  Global parameters[global]        workgroup = DOMAINNAME        realm = domainamet.lan        netbios name = SMBSERVERREP2        server role = active directory domain controller       dns forwarder = 8.8.8.8        idmap_ldb:use rfc2307 = yes[netlogon]        path = /var/lib/samba/sysvol/domainname.lan/scripts        read only = No [sysvol]     

Hosts: 127.0.0.1 localhost localhost.localdomain localhost4 localhost4.localdomain4 ::1 localhost localhost.localdomain localhost6 localhost6.localdomain6 192.168.1.235 bus-ny-dc-01.domain.domain.com bus-ny-dc-01 Resolv: # Generated by NetworkManager search domain.domain.com nameserver 192.168.1.236 nameserver 192.168.1.235 Smb.conf: # Global parameters [global] workgroup =

from both DC: dig google.com dig @8.8.8.8 google.com First dig will use resolvers declared into /etc/resolv.conf. Second dig forces usage of 8.8.8.8. Both commands should reply the same things, on all DC. 2016-06-30 15:58 GMT+02:00 lingpanda101 at gmail.com <lingpanda101 at gmail.com>: > On 6/30/2016 9:57 AM, Garland McAlexander wrote: > >> nslookup google.com

nslookup google.com ;; Got recursion not available from 192.168.1.236, trying next server Server: 192.168.1.235 Address: 192.168.1.235#53 Non-authoritative answer: Name: google.com Address: 172.217.4.78 Interesting little bit about the "Recursion not available" On Thu, Jun 30, 2016 at 9:52 AM, lingpanda101 at gmail.com < lingpanda101 at gmail.com> wrote: >

Yes, it's set up with 8.8.8.8 I'm able to ping it without issues, jut not able to resolve anything externally. On Thu, Jun 30, 2016 at 9:09 AM, mathias dufresne <infractory at gmail.com> wrote: > To get recursion working with internal DNS you only need to set up: > dns forwarder = <IP of your main DNS> > > Is it configured? > > If yes and packets can go

Yes, i believe you hitted "not" having the "root zone" in internal DNS. If i recall correctly its somewhere in 4.4. or 4.5 fix. But as Rowland said, i suggest also upgrading. ps other fix is, switch to bind9_DLZ But again i still advice to upgrade. Greetz, Louis > -----Oorspronkelijk bericht----- > Van: samba [mailto:samba-bounces at lists.samba.org] Namens

Hello List, I am facing a probelm whereby my Samba4 internal DNS does not resolve external addresses: # host www.google.com Host www.google.com not found: 3(NXDOMAIN) The answer is immediate - so there's no timeout issue here. Internal resolution as described in the wiki to test the Samba AD DNS functions like host -t SRV _kerberos._udp.samba.mydomain.com host -t SRV

Hello, thanks for your response. I'm using samba_internal as DNS because I don't want to add bind to only relay the internal DNS. The hosts file is clean on srv2 DC (default localhost), and this is the srv1 hosts: 192.168.0.251 srv1.domain.com srv1 resolv.conf srv1: domain domain search domain.com nameserver 192.168.0.251 nameserver 8.8.8.8 resolv.conf srv2: nameserver

On 28.07.2016 16:20, Rowland penny wrote: > On 28/07/16 14:57, Tim Dittler wrote: >> So no one has an idea what I can try additionally? >> >> Thanks, >> Tim >> >> >> > > OK, lets start with the obvious: > > What OS # lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 14.04.4 LTS Release: 14.04

On 29/07/16 15:12, Rowland penny wrote: > > Does the DC have a fixed ip and if not, why not. > If it does have a fixed ip, what is it > > Once you answer these, I will advise you how to fix your set up > > Rowland > > OK, this is what I would change on your setup, but I would also make backups before changing anything. smb.conf: [global] workgroup =

----- Mensagem original ----- De: "Rowland Penny" <rowlandpenny241155 at gmail.com> Para: samba at lists.samba.org Enviadas: Terça-feira, 1 de Setembro de 2015 12:05:20 Assunto: Re: [Samba] Samba AD - Issue with winbindd: Could not write result On 01/09/15 15:33, Rafael Domiciano wrote: > Hi Rowland, thanks for your response. > > Both samba is self compiled. >

Hi Rowland, thanks for your response. Both samba is self compiled . DC 1: [root at wdc samba]# uname -a Linux wdc 2.6.32-504.23.4.el6.x86_64 #1 SMP Tue Jun 9 20:57:37 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux [root at wdc samba]# cat /etc/redhat-release CentOS release 6.6 (Final) [root at wdc samba]# cat /etc/resolv.conf search DOMAIN nameserver 172.16.5.22 nameserver 172.16.5.1

> > Sorry, must have missed that. No problem! :D OK, your dns domain is 'mydomain.edu' and your AD dns domain is 'addc.mydomain.edu', so far so good, but is the AD REALM set to 'ADDC.MYDOMAIN.EDU <http://addc.mydomain.edu/>' ? Yes, my AD REALM is ADDC.MYDOMAIN.EDU Yes, your AD DC should be the authoritative dns server for the AD dns > domain. ok.

Good afternoon, I have installed a fileserver with samba4 environment. This is configured to works as AD-DC even if I only use it as a fileserver (at the moment). All seems to works fine but, every 10 minutes, the log print these messages: Mar 22 11:53:17 fileserver samba[1946]: [2016/03/22 11:53:17.557554, 0] ../lib/util/util_runcmd.c:324(samba_runcmd_io_handler) Mar 22 11:53:17 fileserver

Thanks for you answer. My OS are Debian 7u8 as server, and Windows 7 as client. I'm doing the test on virtual machines and the dhcp server is a simple router. Anyway i'm using a static IP: iface eth0 inet static address 192.168.1.100 netmask 255.255.255.0 network 192.168.1.0 broadcast 192.168.1.255 gateway 192.168.1.1 dns-nameservers

> > Is anything else listening on port 53 ? I don't think so. # netstat -npl |grep 53 tcp 0 0 0.0.0.0:53 0.0.0.0:* LISTEN 27882/samba tcp6 0 0 :::53 :::* LISTEN 27882/samba udp 0 0 0.0.0.0:53 0.0.0.0:* 27882/samba udp6 0 0 :::53

Hello, I provisioned an samba AD with the bind_dlz option. So far so good. Followed the samba wiki. I have a DNS for our external access services (website, moodle, etc) and I'm using it as a forwarder to AD but it is not working. In a win7 I configured the AD IP as primary DNS and put it in the domain. When I try to access, for example, "wiki.samba.org" it opens normally, but when