Displaying 3 results from an estimated 3 matches for "p002507".
2017 Nov 07
2
after DCs migration to 4.7, two things
...svol
and all is looking well: no db errors, no replication issues, ldapcmp
matches across DCs, etc.
So, I took things to production today, and now I see two things that I
would like some feedback on:
Bind complains:
> Nov 07 18:20:28 dc4 named[19990]: samba_dlz: disallowing update of signer=p002507\$\@SAMBA.DOMAIN.COM name=P002507.samba.domain.com type=AAAA error=insufficient access rights
> Nov 07 18:20:28 dc4 named[19990]: client 192.168.10.12#57335/key p002507\$\@SAMBA.DOMAIN.COM: updating zone 'samba.domain.com/NONE': update failed: rejected by secure update (REFUSED)
> Nov...
2017 Nov 07
3
after DCs migration to 4.7, two things
...rying to add a
dynamic dns record.
I took a look with the Microsoft DNS tool, and noticed that the current
workstation dns records are listed with timestamp 'static'. As I come
from samba 4.5 with internal dns, perhaps this is the way samba adds them..?
So I removed both A/AAAA for the p002507 dns entry, and ran on the
windows p002507 workstation: "ipconfig /registerdns"
suddenly it worked: A new dns record appeared, now with timestamp
"7-11-2017 20:00:00", both A and AAAA records. And they are renewed
every hour, I noticed.
As I don't think we require dns of...
2017 Nov 07
0
after DCs migration to 4.7, two things
...d.
>
> I took a look with the Microsoft DNS tool, and noticed that the
> current workstation dns records are listed with timestamp 'static'.
> As I come from samba 4.5 with internal dns, perhaps this is the way
> samba adds them..?
>
> So I removed both A/AAAA for the p002507 dns entry, and ran on the
> windows p002507 workstation: "ipconfig /registerdns"
> suddenly it worked: A new dns record appeared, now with timestamp
> "7-11-2017 20:00:00", both A and AAAA records. And they are renewed
> every hour, I noticed.
>
> As I don&...