"Remote Access Auto Configuration Manager" is disabled. This says something about controlling how the computer communicates with remote DNS servers. Does this have anything to do with my problem?
that would be a no....your computer itself actually isn't connecting to an outside DNS server....your computer is using either your modem or your router (whichever it's connected directly to) as it's DNS server...then your modem or router is using the ISP dsns servers...
*Basic DNS lesson*
all computer communications are controlled by IP addresses (the 4 sets of numbers seperated by dots). well...people have a hard time remembering ip addresses (imagine having to type in 64.233.161.99 to get to google every time) so we use DNS (Domain Name Service or something to that effect). DNS allows an IP address to be translated to more user friendly names (like www.google.com). so how do you keep this mass of information in one place? well..you don't...you keep it in ALOT of places...
so what happens when you type www.google.com into your webbrowser? your computer checks it's HOSTS file to see if there's a static listing for www.google.com, when it sees that there's nothing there it checks it's DNS settings and forwards the request on to it's selected DNS server (your router) your router doesn't retain any DNS information (unless it does caching..but..forget that) so it asks it's DNS server (your modem)...the modem again doesn't store any dns info so it asks IT's DNS server (your ISP's DNS server)...now...your ISPs DNS server MIGHT know the answer...if it does...it sends the info back and your computer connects to www.google.com ....if the ISP dns server has no idea what www.google.com translates to...then it asks another DNS server higher in the chain...and so on and so on and so on untill you either find the ip for the requested site...or untill there's a failure in the communication chain..
what COULD be happening in your situation is that your ISP's DNS server doesn't know the IP for the site you're requesting...so it's sending out a request up the chain to another DNS server that might know the address...but there's a problem in that link between DNS servers (i.e. router problems between the servers, network outages, alien invasions etc..)...so it can't get a reply to it's request..so neither can you...this is what i THINK is happening...but i could be wrong