mathias dufresne
2016-Jun-15 13:30 UTC
[Samba] [samba] MS DNS console for reverse zones issue
Hi all, Back on digging into some ldapsearch issue I opened MS DNS console to check reverse zones and found that all records in my reverse DNS zones are shown with 5 bytes rather 4: A.B.C.C.D rather than A.B.C.D Zones are B.A.in-addr.arpa. Under these zones there are one "directory" per "C" byte. Using MS DNS console to add new entries is working well, entry is added and then shown with form A.B.C.C.D. Deletion of these entries through MS DNS console is not working. Our AD domain is composed with several Samba DC. Some were running 4.4.4, some were running 4.4.3. An update of all DC to 4.4.4 is in progress. Our MS clients are Windows 7. Did someone already faced that issue?
mathias dufresne
2016-Jun-15 16:10 UTC
[Samba] [samba] MS DNS console for reverse zones issue
All DC updated to last Samba 4.4.4, issue is the same. In the console, addresses are A.B.C.D: Left panel shows: B.A.in-addr.arpa \_ C Right panel shows: A.B.C.C.D PTR some-name.ad.domain.tld DNS entries are correctly added by MS DNS console (host A.B.C.D replies some-name.ad.domain.tld) but the console can't manage these records. It's like there is confusion with this sub-container "C", as if it re-added by MS DNS console to display name in right panel. 2016-06-15 15:30 GMT+02:00 mathias dufresne <infractory at gmail.com>:> Hi all, > > Back on digging into some ldapsearch issue I opened MS DNS console to > check reverse zones and found that all records in my reverse DNS zones are > shown with 5 bytes rather 4: > A.B.C.C.D rather than A.B.C.D > > Zones are B.A.in-addr.arpa. Under these zones there are one "directory" > per "C" byte. > Using MS DNS console to add new entries is working well, entry is added > and then shown with form A.B.C.C.D. > > Deletion of these entries through MS DNS console is not working. > > Our AD domain is composed with several Samba DC. Some were running 4.4.4, > some were running 4.4.3. > An update of all DC to 4.4.4 is in progress. > > Our MS clients are Windows 7. > > Did someone already faced that issue? >