This function works great (despite the fact that some in the community believe it should have been named Get-DNSName). This module supplies the Resolve-DNSName. Luckily, I no longer have to use the old-fashioned command-line NSLookup tool because Windows 8, Windows Server 2012, and even the Microsoft Surface have the DNSClient module built-in. Unfortunately, the old-fashioned Windows NSLookup command-line utility is not all that much fun to use. When I moved into consulting and began working on different systems, I decided I needed to learn how to use the Windows NSLookup command-line utility-because it was the only tool I could be confident would be available. A long time ago, I used to have a dedicated NSLookup GUI utility. An intermediate troubleshooting step is to use the old-fashioned NSLookup utility. Therefore, I need to do all the troubleshooting on my own, so I can tell the Help desk what they need to do in order to resolve my problem. Often, when traveling, a quick call to the Help desk turns into a very long and frustrating call to the Help desk, which in turn becomes the Helpless desk. But if the name does not resolve correctly, then my applications do not work. Actually, I do not need to do this my computer needs to do this. To make a connection, I need to resolve a DNS host name to an IP address. Today, I want to continue that discussion by examining a couple of more functions. Specifically, I talked about looking at the configured DNS server and at the DNS client cache. Yesterday, I talked about using some of the functions from the DNSClient module to troubleshoot networking issues. Microsoft Scripting Guy, Ed Wilson, is here. Summary: Microsoft Scripting Guy, Ed Wilson, continues his discussion about using Windows PowerShell on Windows 8 to troubleshoot DNS issues.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |