search for: 19.172

On 06/08/2019 16:21, L.P.H. van Belle via samba wrote: > Its pretty clear how in the wiki. > > https://wiki.samba.org/index.php/DNS_Administration > > samba-tool dns zonecreate <Your-AD-DNS-Server-IP-or-hostname> 0.99.10.in-addr.arpa > > ;-) And that would get you a /24 network And I also thought wrong, yes the name is wrong, but it should have been '11.0'

Hai, Ok, i did a few things on my DC and see the how/what here. First, the zone. samba-tool dns zonecreate rtd-dc1 19.172.in-addr.arpa That worked fine, in windows DNS tool that shows correct. Now i added an PTR with this line. samba-tool dns add dc1 19.172.in-addr.arpa 55.0 PTR testhost.internal.domain.tld This resulted in a subfolder "0" the 19.172.in-addr.arpa zone. Where

Yes, offcourse, the 172.19 is a "bad" example. I suggest we use the official RFC 1918 zones. 10.0.0.0/8 172.16.0.0/12 192.168.0.0/16 And for example 192.168.0.0/24 as extra, or people get confused. ;-) Greetz, Louis > -----Oorspronkelijk bericht----- > Van: samba [mailto:samba-bounces at lists.samba.org] Namens > Rowland penny via samba > Verzonden: woensdag 7

Are? dig -x <ip> or hostname <ip> find the name of the host ? Le 07/08/2019 ? 10:56, L.P.H. van Belle via samba a ?crit?: > Yes, offcourse, the 172.19 is a "bad" example. > I suggest we use the official RFC 1918 zones. > > 10.0.0.0/8 > 172.16.0.0/12 > 192.168.0.0/16 > > And for example 192.168.0.0/24 as extra, or people get confused. ;-) > >

Hai, ? Good your asking this. I should have tested it... and NO, PTR lookup is not working correctly in this case. ? I've reported it as a bug. https://bugzilla.samba.org/show_bug.cgi?id=14077? ? Greetz, ? Louis ? ? Van: H?noch Herv? [mailto:h.henoch at isc84.org] Verzonden: woensdag 7 augustus 2019 11:01 Aan: L.P.H. van Belle; samba at lists.samba.org Onderwerp: Re: [Samba] samba-tool

I have bind9 but my problem is not the tools but the syntax of samba-tool : I have created a zone 18.172.in-addre.arpa then samba-tool dns add <my ad> 19.172.in-addr.arpa 0.11 PTR server1.sc.local but this command create a zone 172.19.11.11.0 !!!!!! Must I create another zone like 0.18.172 before ? And what is the syntax for create a PTR? record with classe B network ... Regard Le

Hi, I want to create a reverse dns pointer with samba with a network /16. Suppose my network is 172.19.0.0/16 and i've a server with IP=172.19.0.11 and name server1.domain.lan What is the syntax to create the reverse dns zone and then the PTR ? Regard -- ?? *Herv?*?*H?NOCH* *Responsable projets informatique* T?l.?: 04.90.27.57.44 h.henoch at isc84.org <mailto:h.henoch at

Its pretty clear how in the wiki. https://wiki.samba.org/index.php/DNS_Administration samba-tool dns zonecreate <Your-AD-DNS-Server-IP-or-hostname> 0.99.10.in-addr.arpa ;-) Greetz, Louis > -----Oorspronkelijk bericht----- > Van: samba [mailto:samba-bounces at lists.samba.org] Namens > Rowland penny via samba > Verzonden: dinsdag 6 augustus 2019 17:16 > Aan: samba

Package: logcheck Version: 1.2.26 Severity: wishlist Please add following bind9 server messages to ignore: i.e from below, everything that includex "zone.*loaded" + the other messages. Aug 16 20:24:27 ns named[3350]: shutting down: flushing changes Aug 16 20:24:27 ns named[3350]: stopping command channel on 127.0.0.1#953 Aug 16 20:24:27 ns named[3350]: stopping command channel on

Hai James, An other question, is exchange installed in the windows environment? If not thats only good. Ok you need some rewriting some parts i see several things you need to fix. I'll comment below. Greetz, Louis > -----Oorspronkelijk bericht----- > Van: samba [mailto:samba-bounces at lists.samba.org] Namens > James Fowler via samba > Verzonden: donderdag 2 mei 2019

Hai, > -----Oorspronkelijk bericht----- > Van: samba [mailto:samba-bounces at lists.samba.org] Namens Mgr. > Peter Tuharsky via samba > Verzonden: woensdag 20 februari 2019 10:28 > Aan: samba at lists.samba.org > Onderwerp: Re: [Samba] Samba + BIND9 DLZ. DNS dosen't resolve > FQDN, only short hostname > > Well, the mystery is solved. It WAS Avahi, in a way...

> Every Samba DC should use itself for its nameserver. We configured it like this bind9 on a DC: /etc/bind/named.conf: include "/etc/bind/named.conf.options"; include "/etc/bind/named.conf.default-zones"; include "/etc/bind/named.conf.samba"; cat /etc/bind/named.conf.options options { directory "/var/cache/bind"; // If there is a firewall between

I have read that so many times. I started out with the simple, prompted 'samba-tool domain join' and built up from there. Version is: Samba 4.7.6 from Ubuntu (18.04.2) Interesting what happens when I take out --site directive (see below). root at DC2:~# samba-tool domain join DOMAIN1.DOMAIN DC --username='DOMAIN1\EnterpriseAdminUser' --realm='DOMAIN1.DOMAIN'

On Wed, 20 Nov 2024 15:45:29 +0000 Heinz H?lzl <heinz.hoelzl at gvcc.net> wrote: See inline comments: > hi, > i deleted the accounts with pdbdel. > > I did a few spot checks, none of the pc accounts had the attribute > dNSHostName there are no dns-rcords concerning the account The computer accounts should have the dNSHostName attribute set. This seems to explain why it

192.168.1.11 was from a time we tried to increase the number of available IP's by adding a virtual IP in Zentyal for the server to listen on. It never worked and now Zentyal won't let me remove it, due to not being able to save changes. We do use .local because Microsoft small business server, which we were playing with before we started down this route automatically suggested we use the

Hi i got a pdc with samba 4.5.1 with ldap backend for autentication The users can login into domain and everythings fine, after some days, the resources of the networks in this case the shares directory, can't be access by anyone, even them directory in common to everyone. i found this message with the same problem https://lists.samba.org/archive/samba/2014-March/179632.html and i applied

On 01/09/2020 00:33, Peter Pollock wrote: > I just ran? samba_dnsupdate --all-names and got this: > > itadmin at genesis:~$ sudo samba_dnsupdate --all-names > add_interface: not adding duplicate interface 192.168.1.11 You said that you were using the 192.168.2.0/24 network, where is that ipaddress coming from ? > ldb_wrap open of secrets.ldb > > update failed: NOTAUTH >

Hi again. the users work usually in this way, browsing the network to find a serverdc using \\serverdc on explorer file. and after that them choose the correct share and working on inside with their files need it. someone set that share as mapped unit with letter Z or Y. but they normally work in this way daily. so, i can't set browseable = No because the users need to be see the shares on

Thank You Rowland. I did it like You say, killed avahi, added the record without domain suffix, but nothing changed, and the record seems no different compared to other records added with the suffix some time before. My Samba DNS record looks like this (and I see nothing special in there):   Name=, Records=3, Children=0     SOA: serial=39, refresh=900, retry=600, expire=86400, minttl=3600,

root at DC2:~# cat /etc/resolv.conf # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8) # and managed by Zentyal. # # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN # nameserver 192.168.1.254 #search domain1.domain /etc/hostname cat /etc/hostname DC2 /etc/hosts root at DC2:~cat /etc/hosts 127.0.0.1 localhost.localdomain localhost 127.0.1.1