I'm setting up an active directory/domain controller that is also doing DNS using Windows Server 2008 R2.

The install went smoothly. I am able to add a computer to the domain, and can even connect to the internet from this workstation. However, I cannot connect to the internet from the actual domain controller (I'm trying to run windows updates).

Can anyone provide some guidance?



Check the gateway setting for your network interface on your server. Assuming the desktop you can browse from (which you state is a domain member) is using the DNS server on the domain controller, then it almost certainly isn't a DNS problem.


Please provide some additional information to help further troubleshoot this problem:

The output from ipconfig /all from both the server and the workstation is a good starting point, along with a short description of the network and how it is connected to the internet.


Yeah, I'd check your DNS. Make sure you either have root hints and/or a forwarder for all other domains beside your. Ensure you don't have a '.' zone defined, or your machine is claiming that it's definitive for the entire DNS namespace.

Obviously there's a lot of other things to check (routing, firewall, as stated by @DaDaDom), but when you look into DNS, those are common mistakes.

  • can you send me screen shot of a forwarder for all other domains beside own? – mson Feb 22 '10 at 16:09
  • No, you typically use DNS provided by your upstream provider for that, or you could conceivably use OpenDNS or Google. – mfinni Feb 22 '10 at 16:52

Your Domain controller will be set to use itself as its primary DNS server (assuming you installed AD DNS on it), this is how it should be. However if your DNS server is not setup with the proper forwarders to your ISP's DNS server then you will have problems getting connected to the internet.

  • yes - i don't know how to setup the forwarders... – mson Feb 22 '10 at 16:10
  • But if this is the case, how can the workstation browse the web? The workstation must be using the same DNS server as the server after all. – Bryan Feb 22 '10 at 16:10
  • He could have his workstation using a secondary external DNS, potentially. – mfinni Feb 22 '10 at 16:52
  • correct mfinni - using local dns as well as isp – mson Feb 22 '10 at 17:12
  • simple query on dns server works fine; recursive query fails – mson Feb 22 '10 at 17:26

Well, I'd go with the typical steps:

  • Check the reachability of the path which leads to the internet hop-by-hop (switch, router, firewall, ...) with the help of ping or tracert
  • see if there are firewall rules blocking your server from the internet
  • Does DNS lookup work?
  • the network and sharing center actually displays no internet connection. i think a forward lookup zone is missing/hosed – mson Feb 22 '10 at 15:38
  • But the physical connection is available and it also does have an IP address? I guess it does, as the workstation could connect, but still ... – DaDaDom Feb 22 '10 at 16:01

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.