search for: dnakey

Hi, Last evening we upgraded one of our 4 Domain Controllers from 4.6.5 to 4.7.1 and all of a sudden the DNS resolution issue started. We are using BIND9_DLZ back end. This server we had upgraded has all 7 FSMO Roles. Some time back we upgraded the other 3 servers from version 4.6.5 to 4.7.1 and there was no issue at all. I have also observed a very peculiar behaviour that is all of a

...ned all FSMO roles. Should we have transferred the FSMO roles to other working servers before upgrade process? 3. Since samba 4.7.x is a multi-process server, is there any DB locking issue, that is stopping named process from reading DB? 4. In named logs, we say that it was unable to obtain the DNAKEY (.) and it was timing out. But this error was shown even before the upgrade. It turned out be a warning that can be safely ignored. 5. We switched back from BIND9_DLZ DNS Back end to SAMBA_INTERNAL DNS Back end, the same issue continued. DNS failed to respond to any queries. Even internally wi...

...ve too many LDAP or RPC connections simultaneously. But it can be mitigated (see previous post on the subject). But it didn't trigger any issues on DNS side for us. By the way, in any case you should go with 4.7.4 and not 4.7.1. > 4. In named logs, we say that it was unable to obtain the DNAKEY (.) and > it was timing out. But this error was shown even before the upgrade. It > turned out be a warning that can be safely ignored. > > 5. We switched back from BIND9_DLZ DNS Back end to SAMBA_INTERNAL DNS > Back end, the same issue continued. DNS failed to respond to any > qu...

...nections > simultaneously. But it can be mitigated (see previous post on the > subject). But it didn't trigger any issues on DNS side for us. > > By the way, in any case you should go with 4.7.4 and not 4.7.1. > >> 4. In named logs, we say that it was unable to obtain the DNAKEY (.) and >> it was timing out. But this error was shown even before the upgrade. It >> turned out be a warning that can be safely ignored. >> >> 5. We switched back from BIND9_DLZ DNS Back end to SAMBA_INTERNAL DNS >> Back end, the same issue continued. DNS failed to re...