I'm currently running a test setup with Samba4 internal DNS (Version 4.1.5
from Debian backports) and 2 clients (Linux and a Windows).
Everything seems to work so far.
However, I do not manage to get automatic PTR generation working. I'm using
the internal DNS at the moment, but I wouldn't mind changing to bind if
this will make it work.
While reverse DNS seem to work with manually generated entries (from Windows
DNS Manager, samba-tool does not work for this either) the automatic
generation does not seem to work.
When trying to trigger generation in mmc it tells me that the entry already
exists.
Is this a known issue?
Regards
Sven
--
Trotz der zunehmenden Verbreitung von Linux erfreut sich der Bär,
und - dank Knut - insbesondere der Eisbär, deutlich größerer
Beliebtheit als der Pinguin. (Gefunden bei http://telepolis.de/)
/me is giggls@ircnet, http://sven.gegg.us/ on the Web
--
To unsubscribe from this list go to the following URL and read the
instructions: https://lists.samba.org/mailman/options/samba
to make reverse DNS work on the fly with samba 4.1 you just have to create the reverse lookup zone with samba-tool,ex:
samba-tool dns zonecreate your-samba-dns-server 135.168.192.in-addr.arpa.
Then every client that register will auto get a reverse entry.
If you do it by hand the automatic dns update of the client will be denied in your log files and will not succeed.
EDV Daniel Müller
Leitung EDV
Tropenklinik Paul-Lechler-Krankenhaus
Paul-Lechler-Str. 24
72076 Tübingen
Tel.: 07071/206-463, Fax: 07071/206-499
eMail: mue...@tropenklinik.de
Internet: www.tropenklinik.de
"Der Mensch ist die Medizin des Menschen"
-----Ursprüngliche Nachricht-----
Von: samba-...@lists.samba.org [mailto:samba-...@lists.samba.org] Im Auftrag von Sven Geggus
Gesendet: Mittwoch, 5. März 2014 10:21
An: sa...@lists.samba.org
Betreff: [Samba] Does automatic DNS PTR generation in Samba4 AD DC work at all?
Not for Linux clients. The easiest way to get secure dns updates against
AD from Linux clients is via sssd:
dyndns_update = True
dyndns_update_ptr = True
They then behave as windows clients wrt dns.
HTH,
Steve
> Then every client that register will auto get a reverse entry.
hm, not really:
root@linuxclient:~# net ads dns register -P
Successfully registered hostname with DNS
root@linuxclient:~# nslookup linuxclient
Server: 192.168.56.10
Address: 192.168.56.10#53
Name: linuxclient.samdom.example.com
Address: 192.168.56.12
root@linuxclient:~# nslookup 192.168.56.12
Server: 192.168.56.10
Address: 192.168.56.10#53
** server can't find 12.56.168.192.in-addr.arpa.: NXDOMAIN
Reverse Zone has just been created using the following command:
samba-tool dns zonecreate sambadc 56.168.192.in-addr.arpa
Looking at the reverse zone using mmc.exe on the windows client I can not
see any entry either.
As before. Manually adding reverse dns entries to this zone still works fine.
Sven
--
Das Internet ist kein rechtsfreier Raum, das Internet ist aber auch
kein bürgerrechtsfreier Raum. (Wolfgang Wieland Bündnis 90/Die Grünen)
> Not for Linux clients. The easiest way to get secure dns updates against
> AD from Linux clients is via sssd
I don't use sssd currently but nslcd and a cronjob calling "net ads dns
register -P".
Is this not supposed to generate a forward as well as a reverse DNS entry?
Sven
--
Das allgemeine Persönlichkeitsrecht (Art. 2 Abs.1 i.V.m. Art.1 Abs. 1GG)
umfasst das Grundrecht auf Gewährleistung der Vertraulichkeit und Integrität
informationstechnischer Systeme. (BVerfG, 1BvR 370/07)
/me is giggls@ircnet, http://sven.gegg.us/ on the Web