similar to: Don't use .local

On 05/01/15 07:00, Achim Gottinger wrote: > Hello, > > I deployed an Samba 4 AD back in 2013 with .local, not knowing it can > cause troubles with mDns. > On my linux server i did not install avahi and i do not have mDns in > my nsswitch.conf hosts entry. > On windows machines i usually deinstall bonjour whenever it shows up > and i do not install it when installing

During the Christmas holiday I created a AD DC & a MEMBER server (both on Debian 7.7.0) with these scripts (https://secure.bazuin.nl/scripts/) and thank you, L.P.H. van Belle. However, I have created them with a *.local TLD (that now I need to change.) I will need to adjust my hostname files, need to re-configure the kerberos install and of course Bind9. The hostname files I know how to

I expected to re-provision the domain. (That is easy, now.) Okay, so now the question becomes after the re-provision of the domain on the DC what needs to be changed on the MEMBER server. Obviously, the hostname needs to be corrected and check any needed changes within the smb.conf file. Thoughts? --- ------------------------- Bob Wooden of Donelson Trophy 615.885.2846 (main)

I'm not sure if I would not advise to use .local, sometimes it seems to be needed to make a proper location for a running domain where even .cityname cannot accomplish what you need. To be honest I don't run Avahi and will not either. Avahi and mdns are actually only designed because of of bad DNS management by system administrators and have (Apple) users use all their features, the same

Micrososft changed this statement a several of times. The only reason they did is because people using Apple are complaining some services are not working "well" on their OSX and it's a pain to change the DNS name of your Business Server on Windows Server As said before, running on .alocal for Avahi works perfectly and mDNS is only for small networks, and setting up some proper DNS

Sending to you without the mailinglist is on the same level as proper administration of a network ? This is new to me and I'm sure to others too. What might be new to you is that Avahi runs on the domain it finds and not what it expects. That is how the protocol works, it searches, sees the domain of the protocol and goes on. So all Avahi users in a network will run on .alocal is you set the

I'm not missing the point, the point is that you actually cannot tell why .local should stay local always and forever. That's my point, you don't know either as you ask yourself already, "why should I config Avahi myself ?". Indeed stay in control of your network or stay out. 2015-01-05 13:02 GMT+01:00 Rowland Penny <rowlandpenny at googlemail.com>: > On 05/01/15

On 04/01/15 16:11, Donelson Trophy wrote: > > > During the Christmas holiday I created a AD DC & a MEMBER server (both > on Debian 7.7.0) with these scripts (https://secure.bazuin.nl/scripts/) > and thank you, L.P.H. van Belle. > > However, I have created them with a *.local TLD (that now I need to > change.) > > I will need to adjust my hostname files, need to

On 04/01/15 16:45, Bob of Donelson Trophy wrote: > > > I expected to re-provision the domain. (That is easy, now.) > > Okay, so now the question becomes after the re-provision of the domain > on the DC what needs to be changed on the MEMBER server. Obviously, the > hostname needs to be corrected and check any needed changes within the > smb.conf file. > > Thoughts?

Hello, I deployed an Samba 4 AD back in 2013 with .local, not knowing it can cause troubles with mDns. On my linux server i did not install avahi and i do not have mDns in my nsswitch.conf hosts entry. On windows machines i usually deinstall bonjour whenever it shows up and i do not install it when installing itunes. Till now i have not had any dns resolve issues, still i'd like to change

Hai Achim, If everything is working correct, wel dont change the domainname then. if resolving is setup correct you should not notice the problems. even with apple devices, and looks like you did that already and correct. Its never adviced to change the domainname of a domain, and if you do, make sure you know what to change. - DNS ( any dns/db tools, can be done with the windows tools. (

On 05/01/15 11:18, Matt . wrote: > I'm not sure if I would not advise to use .local, sometimes it seems > to be needed to make a proper location for a running domain where even > .cityname cannot accomplish what you need. Hi, even microsoft don't recommend using .local, see http://technet.microsoft.com/en-us/library/cc726016%28v=ws.10%29.aspx/ For the vast majority of people,

On 05/01/15 11:34, Matt . wrote: > Micrososft changed this statement a several of times. > > The only reason they did is because people using Apple are complaining > some services are not working "well" on their OSX and it's a pain to > change the DNS name of your Business Server on Windows Server > > As said before, running on .alocal for Avahi works perfectly

this is not just a MS change.. more info see : http://en.wikipedia.org/wiki/.local Louis >-----Oorspronkelijk bericht----- >Van: rowlandpenny at googlemail.com >[mailto:samba-bounces at lists.samba.org] Namens Rowland Penny >Verzonden: maandag 5 januari 2015 12:43 >Aan: Matt . >CC: samba at lists.samba.org >Onderwerp: Re: [Samba] Don't use .local > >On

On 05/01/15 11:51, Matt . wrote: > Sending to you without the mailinglist is on the same level as proper > administration of a network ? This is new to me and I'm sure to others > too. No of course it isn't, but it shows that it is very easy to make an error even when you are a super-duper sysadmin. :-) > > What might be new to you is that Avahi runs on the domain it finds

On 05/01/15 12:13, Matt . wrote: > I'm not missing the point, the point is that you actually cannot tell > why .local should stay local always and forever. That's my point, you > don't know either as you ask yourself already, "why should I config > Avahi myself ?". Indeed stay in control of your network or stay out. NO, I do not ask myself "why should I

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 - -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The error codes for' doveadm user' should be improved to avoid error handling workarounds when scripting commands: $ doveadm user doveadm user [-a <userdb socket path>] [-x <auth info>] <user mask> [?] $ echo $? 1 $ doveadm user foo userdb lookup: user foo doesn't exist $

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hallo, when I do an "samba-tool gpo list username" I get an "faild access check on OU=name,......". But not if I do a "samba-tool gpo listall" then everything is ok. Is this normal? If I take "administrator" as username I didn't get this message. Stefan -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2

Hi all, I recently tried to use --kerberos switch in addition to some samba-tool command (mainly samba-tool user create) without any success. The man page of samba-tool is quiet shy on that subject: -k KERBEROS|--kerberos=KERBEROS Use Kerberos Looking into samba-tool python script, in fact into /usr/lib64/python2.7/site-packages/samba/netcmd/user.py, I can't find any

Hi Stefan, Thank you a lot for that, it helped me much. To be a bit more precise, thanks again to your example, to authenticate samba-tool command using --kerberos: syntax is "-k yes" or "--kerberos=yes" or "--kerberos yes" AND -U username must not be present. "-k=yes" is not working. 2015-10-19 11:59 GMT+02:00 Stefan Kania <stefan at