DNS issue after joining domain...

I noticed I'm having a similar issue to this guy:

http://social.technet.microsoft.com/Forums/br/w8itprogeneral/thread/408e7970-18bb-4eef-8177-a4cac46d7051

Basically what's happening is when I connect to our domain, I have to use a different DNS server than everyone else in our organization. If I use the DNS server we use for all the other computers, it won't let me join the domain (claiming it can't find the

Active Directory Domain Controller). It says it's a private network instead of a domain network. If I use the DNS server that's behind our firewall (which, to my knowledge...isn't even a DNS server), it'll let me join the domain like normal. The network adapter

will say I'm part of &quot____.local&quot. However I won't be able to access other PCs on our network if I leave that as the primary DNS server (I have to switch the primary DNS BACK to the original DNS server to connect to things beyond the firewall).

I know this is kind of confusing but I'm not sure what's going on here. In short: procedure used to connect to domain normally does not work in Windows 8 and I have to use a different DNS server to join the domain (then switch back to the original DNS server

if I want to connect to computers outside the firewall). Doesn't happen with any of our non-Windows 8-based machines (we have a Server 2012 running in our network as a sandbox server that has the same problem as the Windows 8 PC).

View the full article