Re: Verify how a name is resolved

In news:O0nHwwYqFHA.2816@xxxxxxxxxxxxxxxxxxxx,
Deji Akomolafe <noemail@xxxxxxxxxxxxxxxx> made this post, which I then
commented about below:
> Ace,
>
> Your list:
>> E.g. If you ping "machinename" on a Win2000 or newer machine, it will
>> attempt to use DNS FIRST:
>> 1. Checks it's own name.
>> 2. Local cache.
>> 3. HOSTS file
>> 4. It will then suffix the Search Suffix configured on the machine,
>> then query DNS
>
> Does not bear out your statement:
>> it will attempt to use DNS FIRST:
>
> My own experience is as follows (discounting node-type):
> IF you have an hosts file, the client will use hosts before DNS, for
> FQDN or NetBIOS. Interestingly, your list seems to be agreeing with
> my own understanding. You can test this out by just massging your
> hosts files and clearing your cache and pinging.

I should have said, "It attempts hostname resolution mehod first," which is
more descriptive.

And yes, the hosts file will be checked prior to DNS.

However funny thing about the local cache, it checks that first because when
you create an entry in the hosts file, it automatically gets loaded into
cache. I think it's redundant that it checks the hosts file afterwards,
since it's assumed that whatever is in hosts, would have been autoloaded
into cache anyway.

Ace


.

Relevant Pages

  • Re: What are those records in "ipconfig /displaydns"
    ... I then issued "ipconfig /flushdns" followed ... Ipconfig /displaydns is the command that displays the contents of the DNS ... Client cache. ... file because the HOSTS file is loaded to the DNS Client cache. ...
    (microsoft.public.win2000.dns)
  • Re: svchost consumes 100% of CPU on startup
    ... 2.4MB I thought my HOSTS file was pretty good sized at 288 KB. ... > MS-MVP Windows Shell/User ... >>> reset the contents of the DNS client resolver cache. ...
    (microsoft.public.windowsxp.perform_maintain)
  • Re: svchost consumes 100% of CPU on startup
    ... 2.4MB I thought my HOSTS file was pretty good sized at 288 KB. ... in a command prompt window and see if that works. ... >> reset the contents of the DNS client resolver cache. ...
    (microsoft.public.windowsxp.perform_maintain)
  • Re: svchost consumes 100% of CPU on startup
    ... Windows IP Configuration ... Could not flush the DNS Resolver Cache: ... 2.4MB I thought my HOSTS file was pretty good sized at 288 KB. ...
    (microsoft.public.windowsxp.perform_maintain)
  • Re: svchost consumes 100% of CPU on startup
    ... Could not display the DNS Resolver Cache. ... If Windows File Protection is working correctly, ... Try ipconfig /flushdns and ipconfig /displaydns commands again. ...
    (microsoft.public.windowsxp.perform_maintain)
Loading