Displaying 3 results from an estimated 3 matches for "dc02x".
Did you mean:
dc02
2018 Aug 21
3
Samba 4.8.4 + BIND 9.9.4 - possibility of nonsecure DNS updates
...samdom.svmetal.cz 192.168.45.1 as samdom.svmetal.cz.
Looking for DNS entry SRV _ldap._tcp.samdom.svmetal.cz dc03x.samdom.svmetal.cz 389 as _ldap._tcp.samdom.svmetal.cz.
Checking 0 100 389 dc01.samdom.svmetal.cz. against SRV _ldap._tcp.samdom.svmetal.cz dc03x.samdom.svmetal.cz 389
Checking 0 100 389 dc02x.samdom.svmetal.cz. against SRV _ldap._tcp.samdom.svmetal.cz dc03x.samdom.svmetal.cz 389
Checking 0 100 389 dc03x.samdom.svmetal.cz. against SRV _ldap._tcp.samdom.svmetal.cz dc03x.samdom.svmetal.cz 389
Looking for DNS entry SRV _ldap._tcp.dc._msdcs.samdom.svmetal.cz dc03x.samdom.svmetal.cz 389 as _l...
2018 Aug 21
0
Samba 4.8.4 + BIND 9.9.4 - possibility of nonsecure DNS updates
...> samdom.svmetal.cz.
> Looking for DNS entry SRV _ldap._tcp.samdom.svmetal.cz
> dc03x.samdom.svmetal.cz 389 as _ldap._tcp.samdom.svmetal.cz.
> Checking 0 100 389 dc01.samdom.svmetal.cz. against SRV
> _ldap._tcp.samdom.svmetal.cz dc03x.samdom.svmetal.cz 389
> Checking 0 100 389 dc02x.samdom.svmetal.cz. against SRV
> _ldap._tcp.samdom.svmetal.cz dc03x.samdom.svmetal.cz 389
> Checking 0 100 389 dc03x.samdom.svmetal.cz. against SRV
> _ldap._tcp.samdom.svmetal.cz dc03x.samdom.svmetal.cz 389
> Looking for DNS entry SRV
> _ldap._tcp.dc._msdcs.samdom.svmetal.cz
>...
2018 Aug 24
0
Samba 4.8.4 + BIND 9.9.4 - possibility of nonsecure DNS updates
I have one more interesting thing.
I copied DC01 to LAB environment. I demoted "dead" servers DC02X and
DC03X. After that I changed DNS backend to BIND.
Now samba_dnsupdate --verbose --all-names run as expected (without TSIG
errors).
Also, I have one problematic client joined to domain during
troubleshooting and it cannot do DNS update with Bind. So I also cloned
it to LAB like DC01.
At the firs...