Resolver Configuration

So, what exactly does the resolver allow you to configure Most resolvers let you configure at least three aspects of their behavior the DNS suffix, 2 the search list, and the name server(s) that the resolver queries. 2 We're using the Windows term here for clarity. You may know the DNS suffix as the default domain if you've configured the BIND resolver before. The DNS suffix is the DNS domain in which a system resides. Under certain circumstances, the resolver uses the DNS suffix to generate...

Wildcards

Something else we haven't covered yet is DNS wildcards. At times you want a single resource record to cover any possible name, rather than creating zillions of resource records that are all the same except for the domain name to which they apply. DNS reserves a special character, the asterisk (*), to be used in a DNS datafile as a wildcard name. It will match any number of labels in a name, as long as that name isn't an exact match with a name already in the DNS database. Most often, you'd use...

Using dig

That's one way to< deal with what's arguably a shortcoming in nslookup. Another is just to chuck nslookup and use dig, the Domain Information Groper (a reverse-engineered acronym if we've ever heard one). dig is a powerful DNS query tool that comes with BIND. Unfortunately, it isn't shipped with Windows Server 2003, but you can get a version of dig that runs on Windows NT, Windows 2000, and Windows Server 2003 from You may also need to download the other DLLs available at Follow the...