I have a file server running on a Windows Server 2012 R2 two-node cluster. The cluster role's real name is dept-server, as the university's central IT wants computer names in AD to be dept-xxxxx.
So the cluster role's FQDN is dept-server.dept.example.edu. I also want server.dept.example.edu to work as well, so I set an alias for the cluster. Works great, and I can access the shares via \dept-server as well as \server.
Here's where it gets frustrating: every morning when I wake up, I check my (2012 R2) DNS server, and for this alias name, there exist two new AAAA records...and the A record is deleted. I delete the AAAA records by hand and add the A record, and we're back in business. If the AAAA record lingers around and finds its way into workstations, I get the problems where \server doesn't work as expected.
This is quite simple; I need to do one of two things, preferably both:
- Tell the 2012 R2 clustered file server to stop registering AAAA records.
- Tell the 2012 R2 DNS servers to never, ever accept a registration from ipv6.
My DNS servers are internal for my department, forward to the campus BIND DNS servers, and are not authoritative on the campus domain.