Displaying 2 results from an estimated 2 matches for "011loc1".
Did you mean:
011dc1
2018 Jun 08
3
Samba, AD, 'short' name resolving...
....43#58396/key LOC1-PC01L12\$\@KERBEROS.DOMAIN.TLD: updating zone '1.168.192.in-addr.arpa/NONE': deleting rrset at '43.1.168.192.in-addr.arpa' PTR
Jun 8 11:54:31 named[440]: samba_dlz: subtracted rdataset 43.1.168.192.in-addr.arpa '43.1.168.192.in-addr.arpa.#0111200#011IN#011PTR#011loc1-pc01l12.primarydnsdomain.domain.tld.'
Jun 8 11:54:31 named[440]: client 192.168.1.43#58396/key LOC1-PC01L12\$\@KERBEROS.DOMAIN.TLD: updating zone '1.168.192.in-addr.arpa/NONE': adding an RR at '43.1.168.192.in-addr.arpa' PTR loc1-pc01l12.primarydnsdomain.domain.tld.
Jun 8 11:5...
2018 Jun 08
4
Samba, AD, 'short' name resolving...
Mandi! Rowland Penny via samba
In chel di` si favelave...
> This is probably where you are going wrong. AD lives and dies on DNS,
> your DC MUST be authoritative for the AD domain.
...but *is* authoritative! Simply DHCP server assign the ''old'' DNS,
where all resolution fr the AD (sub)domain are forwarded to AD DNS...
> Your AD clients should be using the DC as