similar to: specify alternative port for samba internal dns server

Whoops - sorry for responding to you directly rather than via the list -- I only use gmail for extremely high-volume mailing lists, and usually that's just to skim-read them -- so I don't know the gmail web-ui very well (and it seems to change all the time) -- apologies. (Also i have no idea how to not top-post with gmail ... I'll figure that out for next time) You seem to have

My goal is for the samba dns server to be authoritative for 'ad.mydomain.com' but not for mydomain.com. The dns server that the clients in my domain use is statically configured to resolve all requests for ad.mydomain.com via the samba internal dns -- I believe this is exactly what is required for samba to function ... Is this incorrect somehow? A whole bunch of other samba services can

I need helping again implementing samba4 ad and dns: Actually we have a dnsmasq server with dhcp/dns services for users on the lan, if we start to using the internal samba4 dns server to resolv names on the zone of DC server example mydomain.test.com we can use the actual dnsmasq to server another domains that we need ?, for example otherdomain.testing.com.ar If that is correct we need to

On Thu, 27 Aug 2015 18:54:09 +0100 Rowland Penny <rowlandpenny241155 at gmail.com> wrote: [snip] > > Well, there are couple of things I can see wrong, one on the howto > and one in your smb.conf, first the howto: > > 127.0.0.1 localhost > 127.0.1.1 pdc.mydomain.local pdc > > 10.0.0.5 pdc.mydomain.local pdc > > Change it to this: > > 127.0.0.1

Hi There, I've searched and searched. Then searched some more. Came up with nothing. So here I am. I installed Samba as a PDC as per the HowTo, here: http://www.tiltingatlinux.com/2014/04/basic-samba4-domain-controler-on-ubuntu.html Thing is: The workgroup isn't coming out right: $ smbclient -L localhost -U% Domain=[MYDOMAIN] OS=[Unix] Server=[Samba 4.1.6-Ubuntu]

Correct we have the dnsmasq server dns+dhcp on other ip server. So if I understand well, we will use the samba DC as a "authoritative nameserver" and the dnsmasq as a forwarder dns for resolve outside our zone ? And we set on the dnsmasq (when deliver ip to the client as a dhcp server) the primary dns is a samba DC server, and too we can set the dnsmasq a secondary dns server or is not

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

On 26/02/15 23:39, Ben Cohen wrote: > Please stop making the assumption that I don't have different problems > than you... > > I support IT environments that are connected via incredibly slow > internet links -- user clients CANNOT use something other than my dns > server as their dns resolver -- I have to implement logic which > controls all internet access, including

On 02/09/2020 16:28, Rowland penny via samba wrote: > > On 02/09/2020 16:15, jmpatagonia via samba wrote: >> That mean for example if my domain resolve >> >> ???????????????? xxxxx.testing.mydomain.com >> >> the dnsmasq should NOT resolv? xxxxxx.mydomain.com this is in >> ascending way >> ? >> >> Another way to expose: >> We set

On 02/26/2015 04:10 PM, Ben Cohen wrote: > Whoops - sorry for responding to you directly rather than via the list -- I > only use gmail for extremely high-volume mailing lists, and usually that's > just to skim-read them -- so I don't know the gmail web-ui very well (and > it seems to change all the time) -- apologies. (Also i have no idea how to > not top-post with gmail

I read that page -- but I'm not seeing anything that makes me think my dns strategy is inappropriate ... The article does describe the possible deployment strategies in what I believe to be an overly constrained manner: >From the wiki: --- You can use either the internal DNS server that is built into the samba4 binary, or an external bind DNS server. Default is to use the internal

I found with my Windows clients it was extremely important to point them to the Samba AD only. No other ip_address for DNS, and as Rowland indicates, anything they need outside the domain is resolved by Samba forwarding the request (in my case, it's our gateway device which in turn forwards outside) On 02/26/2015 06:06 PM, Rowland Penny wrote: > On 26/02/15 22:58, Ben Cohen wrote:

I add some additional information I didn't give in my previous email, specifically how I tried to force DC1 and DC2 to contact each other only with their VPN IPs. I did so using dnsmasq as a DNS proxy. # DC1 configuration IP NIC1: 172.16.0.2 IP NIC2: 172.20.0.1 IP VPN: 172.19.1.173 --- /etc/resolv.conf: search domain.local domain domain.local nameserver 172.19.1.173 --- I configured dnsmasq

That mean for example if my domain resolve xxxxx.testing.mydomain.com the dnsmasq should NOT resolv xxxxxx.mydomain.com this is in ascending way ? Another way to expose: We set dnsmasq+dhcp to set clients that the only DNS server is samba DC on the domain name mysubdomain.mydomain.com DC for example resolv server1.mysubdomain.mydomain.com right, now if a client as for a

Rowland, Seeing as BIND_DLZ uses the same info in AD as SAMBA_INTERNAL does, > then no, using the internal dns server will not make any difference. Ok. Which ever dns server you use, it must be authoritative for the AD > domain and if required it should be a subdomain of your registered > domain, see here: > > https://wiki.samba.org/index.php/Active_Directory_Naming_FAQ >

> > 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.

hi: my company has two dns servers, but samba4 internal dns forward can only forward to 1 server. to workarround it i run dnsmasq as dns cache at 127.0.0.1 and let samba4 dns forward to 127.0.0.1. my smb.conf looks like: dns forwarder = 127.0.0.1 interfaces = 10.1.1.1 bind interfaces only = Yes with the setting samba won't bind to 127.0.0.1, so dnsmasq can use 127.0.0.1 to do the work.

On 02/09/2020 15:42, Nick Howitt via samba wrote: > Or set dnsmasq as the primary DNS server, but include a line in your > dnsmasq config: > server=/your.dc.domain/your.dc.ip Don't do that. To be honest, I wouldn't use dnsmasq at all, but if I had to, I wouldn't do that ;-) Rowland

On 7/25/19 6:48 AM, rainer at ultra-secure.de wrote: > Am 2019-07-25 15:41, schrieb hw: >> On 7/25/19 2:53 PM, rainer at ultra-secure.de wrote: >>> Am 2019-07-25 14:51, schrieb hw: >>>> Hi, >>>> >>>> how can DNS reliability, as experienced by clients on the LAN who are >>>> sending queries, be increased? >>>>

Hello Rowland 1) I update samba4 to Version 4.11.2, the error " /usr/sbin/samba_dnsupdate: > ERROR(runtime): uncaught exception - (9711" disappear. 2) Now have a question to configure a external dns: There is a docu or guide for that ? I found that --> https://lists.samba.org/archive/samba/2010-January/152913.html 3) The parameters dns forwarder is required ? # Global