Running the Dig utility from Windows command line

How to install and use the dig utility on a Windows system

The dig (domain information groper) utility is something I use on my Linux hosts so often that I miss it when I move back to a Windows host. Here’s how to install and use the dig utility on a Windows system:

  1. Download the BIND package from the Internet Systems Consortium web site for your Windows
  2. Extract to the directory that you’d like to run the program from, probably C:UsersMyUsername
  3. Run the dig command

Microsoft Windows [Version 6.1.7601] Copyright (c) 2009 Microsoft Corporation. All rights reserved. C:Userstechpain>dig mx ; <<>> DiG 9.9.5-W1 <<>> mx ;; global options: +cmd ;; Got answer: ;; ->>HEADER<
Dan Esparza’s blog has a great post on different ways to use the dig utility and understanding the output.

Also, check out how to run the WhoIs utility from Windows command line.

Windows dig command options


WhoIs lookup from Windows command line

A WhoIs lookup will show the registration record for a domain name, and being able to run this right from the command line is really convenient.

This utility will run on Windows XP and higher (client) and Windows Server 2003 and higher (server).

Download the utility from the Windows Sysinternals site and copy it to the path that you want to use (probably C:\Users\MyUsername). After that you can run the WhoIs utility like this:

Windows WhoIs - Command line example
An example whois lookup from the Windows command line


WhoIS command and output

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.


Whois v1.11 - Domain information lookup utility
Sysinternals -
Copyright (C) 2005-2012 Mark Russinovich

Connecting to
Connecting to

Registrar WHOIS Server:
Registrar URL:
Updated Date: 2013-10-22T03:40:00-06:00
Creation Date: 2010-08-04T00:59:03-06:00
Registrar Registration Expiration Date: 2017-08-04T00:59:03-06:00
Registrar:, Inc.
Registrar IANA ID: 625
Registrar Abuse Contact Email:
Registrar Abuse Contact Phone: +1.17202492374
Domain Status: clientTransferProhibited
Registrant Name: Whois Agent
Registrant Organization: Whois Privacy Protection Service, Inc.
Registrant Street: PO Box 639
Registrant City: Kirkland
Registrant State/Province: WA
Registrant Postal Code: 98083
Registrant Country: US
Registrant Phone: +1.4252740657
Registrant Fax: +1.4259744730
Registrant Email:
Admin Name: Whois Agent
Admin Organization: Whois Privacy Protection Service, Inc.
Admin Street: PO Box 639
Admin City: Kirkland
Admin State/Province: WA
Admin Postal Code: 98083
Admin Country: US
Admin Phone: +1.4252740657
Admin Fax: +1.4259744730
Admin Email:
Tech Name: Whois Agent
Tech Organization: Whois Privacy Protection Service, Inc.
Tech Street: PO Box 639
Tech City: Kirkland
Tech State/Province: WA
Tech Postal Code: 98083
Tech Country: US
Tech Phone: +1.4252740657
Tech Fax: +1.4259744730
Tech Email:
Name Server:
Name Server:
DNSSEC: NotApplicable
URL of the ICANN WHOIS Data Problem Reporting System:

>>> Last update of WHOIS database: 2014-02-15T13:50:43-07:00 <<< The Data in the, Inc. WHOIS database is provided by, Inc. for information purposes, and to assist persons in obtaining information about or re lated to a domain name registration record., Inc. does not guarantee i ts accuracy. By submitting a WHOIS query, you agree that you will use this Data only for lawful purposes and that, under no circumstances will you use this Dat a to: (1) allow, enable, or otherwise support the transmission of mass unsolici ted, commercial advertising or solicitations via e-mail (spam); or (2) enable hi gh volume, automated, electronic processes that apply to, Inc. (or its systems)., Inc. reserves the right to modify these terms at any time. By submitting this query, you agree to abide by this policy.

Also, check out how to run the dig utility from Windows command line.


Windows 7 – Tips and Tricks

Accessing Administrative Shares (\HOSTNAMEc$)

From To enable administrative shares you gotta make a registry change. Click on the orb and in the search box type ‘regedit’ and hit enter. Browse to


Add a new DWORD called “LocalAccountTokenFilterPolicy” and give it a value of 1. Reboot and yer done! (Applies to Vista too!)

Allow ICMP (ping) Requests Through Firewall

Right click ‘cmd’ from the start menu and select ‘Run as Administrator’, then

netsh firewall set icmpsetting 8 enable

and to enable again

netsh firewall set icmpsetting 8 disable

(Applies to Vista too!)

Get back your Quick Launch toolbar

1. Right-click the taskbar, choose Toolbars / New Toolbar
2. In the folder selection dialog, enter the following string and hit OK:
%userprofile%AppDataRoamingMicrosoftInternet ExplorerQuick Launch
3. Turn off the “lock the taskbar” setting, and right-click on the divider. Make sure that “Show text” and “Show title” are disabled and the view is set to “small icons”.
4. Use the dividers to rearrange the toolbar ordering to choice, and then lock the taskbar again.

Starting Windows Explorer from “My Computer”

From Tim Sneath’s Blog:
If you spend more time manipulating files outside of the documents folders than inside, you might want to change the default starting directory for Windows Explorer so that it opens at the Computer node:

To do this, navigate to Windows Explorer in the Start Menu (it’s in the Accessories folder). Then edit the properties and change the target to read:

%SystemRoot%explorer.exe /root,::{20D04FE0-3AEA-1069-A2D8-08002B30309D}

Vista Wireless Adaptor Issues

Vista Wireless sucks. I’ve had intermittent wireless connectivity issues on my laptop (which now dual boots Ubuntu 9.04), and now I have friends and family complaining about the same problem.
Microsoft blames the DHCP BROADCAST flag, which was disabled in XP SP2, but is NOT disabled in Vista. Here is the M$ support KB entry, and here is a post with the regedit steps including screenshots.

Notes: Client’s router is a netgear WGR614v6 (firmware: V1.0.11_1.0.7NA), if this is really the issue, then setting a static IP should resolve the problem. Let’s try that and see if it helps… Also, the latest firmware for that router is 2.0.19_1.0.19, which I downloaded in case we want to try that next. Download and instructions can be found at

Update: Setting a static IP seems to have improved the situation, but not resolved it entirely. Now the issue appears only when coming out of sleep mode. A post by “Deke” on explains:

I had this issue on my desktop after it returns from an S3 sleep state. You can do one of two things.

1. You can simply open an elevated command prompt and type ipconfig /renew each time,


2. You can automate the the above process:

Make a small batch file with a single line: ipconfig /renew

Put it in a folder somewhere (I used c:windowssystem32).

Open the task scheduler and create a new task. Make sure that you check “Run with highest privileges.”

Trigger should be set to “On workstation unlock of any user”.

Action is “Start a program”. Point it you your batch file.

Under the Conditions tab, make sure “Start the task only if the computer is on AC power” and “Stop if the computer switches to battery power” are both unchecked.

Lets give that go…