I realized that I would need to fire up Network Monitor to get the story. Later I realized that I was on to something here. EDns is a relatively new DNS protocol extension that is still coming of age. I skimmed some R2 release notes I found and I saw that there were EDns (EDNS0) changes with R2 but it was pretty vague. I tried all the basic troubleshooting methods to no avail. I did some searching and didn’t find an answer (although now that I know what search terms to look for, I see that others have run into this now). (feel free to skip to the bottom for the fix if you don’t want to read the details) However, if I pinged the DNS name, it worked. What made it even more confusing was that if I viewed the errors in my browser, it timed out and gave a DNS error. It’s almost as if Microsoft decided they didn’t want to grow their search engine market share anymore and would start blocking their visitors. However, other websites worked perfectly. Visiting some websites like and a number of other Microsoft websites didn’t work. ![]() However, after the install, I got the strangest behavior. ![]() The upgrade process itself wasn’t too much work but was a bit more than ‘next, next, finish’ because the AD schema needed to be updated and the installer required that WSUS be uninstalled first. I recently upgraded my home Windows Server 2008 Domain Controller to R2.
0 Comments
Leave a Reply. |