We have a Windows Server 2012 domain. The server acts as our DHCP and DNS. About 2 weeks ago, Comcast changed something in their router I believe, enabling IPv6. Since IPv6 was never initially set up on our Windows 2012 server, the router was now acting as DHCP for IPv6 addresses. Because of that, none of our pc's in the domain could resolve names since it was no longer using IPv4 and our own DNS server.
I found the setting in the Comcast router to turn off IPv6 DHCP, but it appears the damage is already done. I don't know anything about IPv6 and am the "pseudo" IT guy in the office. I've had to go to all the affected machines and ran "ipconfig /release6" as well as remove all the IPv6 DNS entries on our Windows 2012 Server.
This seemed to "band-aid" the situation, but client machines keep getting IPv6 and DNS keeps getting screwed up.
Can anyone lend some advice on what the problem is and how to solve it?