It is not in the LDAP/AD, this "dig" is served by bind, and this is
what I think is out of sync. I am not sure how it exactly works, but if
clients are not registering to master DNS then secondary DNS instances
will not get the domain updates?
Adam Pribyl
On Wed, 9 Jun 2021, Marco Gaiarin via samba wrote:
> Mandi! Rowland penny via samba
> In chel di` si favelave...
>
>> Why do you think I went to all the trouble to write this:
>>
https://wiki.samba.org/index.php/Configure_DHCP_to_update_DNS_records_with_BIND9
>> You need to use the dns from your DC's , though you can get your
main dns
>> servers to forward requests for the AD domain to the AD DC's.
>> Putting it simply, your AD dns is broken.
>
> It worked until last week. If i remember well, dhcp/dns registration it
> is needed for reverse zone, but reverse zone is not required (and i can
> confirm that, because i'm running the domain by 2 year without reverse
> zones...).
>
>
> Anyway, something seems to have broken my DNS setup, something that:
>
> samba-tool ldapcmp ldap://vdcsv1 ldap://vdcpp2 -U Administrator
>
> does not catch. How can i debug this?
>
>
> Thanks.
>
> --
> dott. Marco Gaiarin GNUPG Key ID: 240A3D66
> Associazione ``La Nostra Famiglia''
http://www.lanostrafamiglia.it/
> Polo FVG - Via della Bont?, 7 - 33078 - San Vito al Tagliamento
(PN)
> marco.gaiarin(at)lanostrafamiglia.it t +39-0434-842711 f
+39-0434-842797
>
> Dona il 5 PER MILLE a LA NOSTRA FAMIGLIA!
> http://www.lanostrafamiglia.it/index.php/it/sostienici/5x1000
> (cf 00307430132, categoria ONLUS oppure RICERCA SANITARIA)
>
> --
> To unsubscribe from this list go to the following URL and read the
> instructions: https://lists.samba.org/mailman/options/samba
>