asked on DNS alias shares are not working and some authentication from non-Windows systems are having issues since our domain controller reboots
Our issue at the highest level is that our DNS alias shares are not working and some authentication from non-Windows systems are having issues since our domain controller reboots.
We have one 2008 R2 DC and five (5) 2016 domain controllers in play at the moment. The only reason we are keeping the 2008 DC is for an old authentication system which will be decommissioned next month. However, one of our 2012 DC's was having an issue with CPU utilization/hung so it was rebooted. A few days later, we rebooted the 2008 DC and the troubles began. One thing to note, we have no issues accessing the NAS via the alias from a Win7 PC and/or a Windows 2008 R2 server. MS has not been able to help us this thing figure out.
Has anyone experienced anything like this and have any ideas?
The server or device that hosts your shares - which LDAP ( AD DNS) servers is it pointing to?
Does the issue go away if you repoint it to another DC?
For the non-Windows devices, have you looked into which servers they are using for DNS?
You should also confirm whether the issue is DNS, or authentication (or both?) - you might be able to do that using just IP address instead of share name
C:\>nslookup xfiles1
Server: TestDC02.mydomain.local
Address: n.n.n.n
Name: NAS800fsaa.mydomain.local
Address: n.n.n.nxn
Aliases: files1.mydomain.local
Files1.mydomain.local (or files1) is not accessible
Server: TestDC02.mydomain.local
Address: n.n.n.n
Name: NAS800fsaa.mydomain.local
Address: n.n.n.nxn
Aliases: files1.mydomain.local
so it is returning 2 records when it should only be returning 1 record
which is the correct one? testDC02 or NAS800fsaa ?
The actual hostname is a NAS server that gets replaced every few years by new storage vendor or storage platform. We have been using a CNAME alias to point the hostnames for ease of changing.
Another thing to note, we can't map storage and other non-windows via SMB except to a 2008 server.
Why can't you map storage via smb without going through a jump server?
CIFS not setup on the NAS, always using iSCSI?
I've setup Synology, QNAP, Dell, HP, freenas and all support CIFS and integration with AD via LDAP
Maybe you mean CNAME records.
You'll debug this by probing your DNS servers with dig or nslookup.
DNS will have no effect on CPU utilization... and if DNS is... incorrect... no telling what's occurring, which might be the root cause of CPU spinning.