Luca Olivetti
2017-Apr-27 15:12 UTC
[Samba] Samba AD with internal DNS: Can't resolve aliases anymore
El 27/04/17 a les 16:46, Dirk Heinrichs via samba ha escrit:> Am 22.04.2017 um 17:59 schrieb Dirk Heinrichs via samba: > >> Am 22.04.2017 um 14:56 schrieb Luca Olivetti via samba: >>> Check nsswitch.conf. Make sure you just have "iiles dns" in the hosts >>> line. >> Yes, that's the case. > > Is there anything else I could check?I don't know, sorry, I just know that when I had the same problem I saw that nsswitch in the hosts line had "files mdns4_minimal [NOTFOUND=return] dns" and I just removed the "mdns4_minimal [NOTFOUND=return" part. Now that I checked nsswitch I see that something put the mdns4_minimal part back again and it's still working, so I'm not sure that it was the real problem. Bye -- Luca Olivetti Wetron Automation Technology http://www.wetron.es/ Tel. +34 93 5883004 (Ext.3010) Fax +34 93 5883007
lingpanda101
2017-Apr-27 15:25 UTC
[Samba] Samba AD with internal DNS: Can't resolve aliases anymore
On 4/27/2017 11:12 AM, Luca Olivetti via samba wrote:> El 27/04/17 a les 16:46, Dirk Heinrichs via samba ha escrit: >> Am 22.04.2017 um 17:59 schrieb Dirk Heinrichs via samba: >> >>> Am 22.04.2017 um 14:56 schrieb Luca Olivetti via samba: >>>> Check nsswitch.conf. Make sure you just have "iiles dns" in the hosts >>>> line. >>> Yes, that's the case. >> >> Is there anything else I could check? > > I don't know, sorry, I just know that when I had the same problem I > saw that nsswitch in the hosts line had "files mdns4_minimal > [NOTFOUND=return] dns" and I just removed the "mdns4_minimal > [NOTFOUND=return" part. > Now that I checked nsswitch I see that something put the mdns4_minimal > part back again and it's still working, so I'm not sure that it was > the real problem. > > ByeDo you have a A record associate with server1? The host command should have given you something like this host alias1 alias1.altum.de is an alias for server1. server1 has address 192.168.1.1 Preferable it should look like this if server1 is joined to the domain. host alias1 alias1.altum.de is an alias for server1.altum.de. server1.altum.de has address 192.168.1.1 -- -- James
Dirk Heinrichs
2017-Apr-27 16:40 UTC
[Samba] Samba AD with internal DNS: Can't resolve aliases anymore
Am 27.04.2017 um 17:25 schrieb lingpanda101 via samba:> Do you have a A record associate with server1? The host command should > have given you something like this > > host alias1 > alias1.altum.de is an alias for server1. > server1 has address 192.168.1.1 > > Preferable it should look like this if server1 is joined to the domain. > > host alias1 > alias1.altum.de is an alias for server1.altum.de. > server1.altum.de has address 192.168.1.1Yes, I have: # samba-tool dns add server1 altum.de server1 A 192.168.1.1 ERROR: Record already exists Anyway, found it: Seems I've added the CNAME record using samba-tool dns add server1 altum.de alias1 CNAME server1 After deleting it and re-adding it using the FQDN for server1 like this samba-tool dns add server1 altum.de alias1 CNAME server1.altum.de it's working again. Thanks to all for helping... Dirk -- Dirk Heinrichs <dirk.heinrichs at altum.de> GPG Public Key: D01B367761B0F7CE6E6D81AAD5A2E54246986015 Sichere Internetkommunikation: http://www.retroshare.org Privacy Handbuch: https://www.privacy-handbuch.de -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: OpenPGP digital signature URL: <http://lists.samba.org/pipermail/samba/attachments/20170427/2ea552f0/signature.sig>
Seemingly Similar Threads
- Samba AD with internal DNS: Can't resolve aliases anymore
- Samba AD with internal DNS: Can't resolve aliases anymore
- Samba AD with internal DNS: Can't resolve aliases anymore
- Problem with ticket lifetimes of Linux clients authenticating to Samba 4 AD
- Samba Virtual Servers (Host aliases) configuration problem