Host file and possbily to many "."

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Hi,
I've been having a lttle touble with the hosts file, and have found a work
around but not sure why the fix has worked.

I needed to resolve a address - example1.abc.webdsi.com to 152.15.122.2
the host couldnt be found.
However adding a further line to the host file of
152.15.122.2 example1
once this was added it allowed for name resolution of the smaller name, but
also for the full address.
what was stopping the intial line from allowing the name resolution?
thanks
 
Hello Lee,

Thank you for choosing Microsoft and for using our Newsgroups. I have
reviewed the information you have provided this far. My understanding of
the issue is the following:

You are adding an entry in your hosts file and want to know why you can
contact a machine by netbios and FQDN when the hosts entry is "server
192.168.0.1"

RESOLUTION:
============

The reason this works over using the full FQDN in the hosts file is because
when a Win2k, XP, or WIn2k3 machine makes a name query, it will
autmatically append the domain name that the physical machine is a member
of. For example, if you have a client machine that is a member of
"microsoft.com" and you query for a machine called "Lee". Your client will
autmatically query "lee.microsoft.com".


Best Regards,

James Raines
Microsoft Corporation
 
In
James Raines said:
Hello Lee,

Thank you for choosing Microsoft and for using our Newsgroups. I have
reviewed the information you have provided this far. My
understanding of the issue is the following:

You are adding an entry in your hosts file and want to know why you
can contact a machine by netbios and FQDN when the hosts entry is
"server 192.168.0.1"

RESOLUTION:
============

The reason this works over using the full FQDN in the hosts file is
because when a Win2k, XP, or WIn2k3 machine makes a name query, it
will autmatically append the domain name that the physical machine is
a member of. For example, if you have a client machine that is a
member of "microsoft.com" and you query for a machine called "Lee".
Your client will autmatically query "lee.microsoft.com".


Best Regards,

James Raines
Microsoft Corporation
Click to expand...

Just to add for Lee, that would be the Search Suffix, which is by default,
the Primary DNS Suffix, which is based on the domain the machine is joined
to. One can add additional search suffixes, if required in a specific
scenario to suffix specific domains that are trusted outside of the
organization, for example, such as a partner organization's domain suffix,
provided there's access to the partner's zone, whether a secondary zone is
configured, a conditional forwarder is configured, or standard forwarder is
configured, to their name systems.

Cheers!

--
Regards,
Ace

Please direct all replies ONLY to the Microsoft public newsgroups
so all can benefit.

This posting is provided "AS-IS" with no warranties or guarantees
and confers no rights.

Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSE+I, MCT, MVP
Microsoft Windows MVP - Windows Server - Directory Services

Security Is Like An Onion, It Has Layers
HAM AND EGGS: A day's work for a chicken;
A lifetime commitment for a pig.
 
Back
Top