Univention Bugzilla – Bug 36089
Add "name resolve order" to smb.conf
Last modified: 2017-10-18 12:02:40 CEST
In samba 4.2 the default for the parameter "name resolve order" was changed to match the manual page: Before it was "wins host bcast", now it is "lmhosts wins host bcast". Ad debug level 4 this results in the following messages when running any samba relates tool (univention-s4search etc.): ============================================================================== resolve_lmhosts: Attempting lmhosts lookup for name master50.ar40i1.qa<0x20> startlmhosts: Can't open lmhosts file /etc/samba/lmhosts. Error was No such file or directory ============================================================================== This is just a minor thing, but reading the manapage shows another: ============================================================================== When Samba is functioning in ADS security mode (security = ads) it is advised to use following settings for name resolve order: name resolve order = wins bcast DC lookups will still be done via DNS, but fallbacks to netbios names will not inundate your DNS servers with needless querys for DOMAIN<0x1c> lookups. ============================================================================== So maybe we should configure this parameter accordingly: * Samba4 DC: name resolve order = wins host bcast * Samba/AD member joined with security=ADS: name resolve order = wins bcast
Well, there should be a new UCR variable introduced in order to distribute this configuration via a policy.
Created attachment 8009 [details] Set "name resolve order" in smb.conf via samba.conf.d/10global
Created attachment 8010 [details] Set "name resolve order" in smb.conf via new ucr variable samba/name/resolve/order
applied patch from Comment 3.
updated to univention-samba4 package from errata4.2-2 but no samba/name/resolve/order ucr var debian/changelog has not been updated !!!! seems that the univention-samba4 package has not been built with the changes Please keep in mind, every time you merge something to the ucs branch (4.2-2 in this case) the debian/changelog has to be updated (new package version) and you have to import/build the package
updated debian/changelog and built the package
OK - template OK - defaults OK - ucr description OK - yaml
<http://errata.software-univention.de/ucs/4.2/200.html>