<div>
The dots imply sub-domains (DNS domains, not Windows domains). &nbsp;When you use dashes, you're at the &quot;top level&quot; domain where you are (since this is a private DNS domain and doesn't come under the public TLD's).
</div>


<div>
To expand a little fisher.sherman.pft implies:<br />
pvt -!<br />
&nbsp; &nbsp; &nbsp; &nbsp;sherman-!<br />
&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;fisher<br />
<br />
and fisher-sherman-pvt implies:<br />
<br />
fisher-sherman-pvt (all one domain, instead of 3).
</div>


<div>
so what would i do to have the implication of fisher.sherman.pvt?<br />
create dns domains pvt sherman and fisher?
</div>


<div>
sherman.pvt &nbsp; is the domain<br />
fisher &nbsp;is the member, which should be your server's name<br />
(workstations do not need it defined unless you have to)<br />

</div>


<div>
<div class="content wysiwyg-content">
Can someone please explain to me (or point me to a good resource) as to why my site becomes available when using dashes instead of dots? For example, when i use<br />
<br />
<a href="http://fisher-sherman-pvt" rel="ugc">http://fisher-sherman-pvt</a>, my site comes up fine. However, when I use <a href="http://fisher.sherman.pvt" rel="ugc">http://fisher.sherman.pvt</a>, I get &quot;The website can not be found&quot;<br />
<br />
This is an internal site on a NT network, on a 2K3 server. I know this isn't much to go on, so if you need more specifics, let me know. I just thought maybe this was a common issue. THanks.
</div>
</div>


Can someone please explain to me (or point me to a good resource) as to why my site becomes available when using dashes instead of dots? For example, when i use

http://fisher-sherman-pvt, my site comes up fine. However, when I use http://fisher.sherman.pvt, I get "The website can not be found"

This is an internal site on a NT network, on a 2K3 server. I know this isn't much to go on, so if you need more specifics, let me know. I just thought maybe this was a common issue. THanks.

The dots imply sub-domains (DNS domains, not Windows domains).  When you use dashes, you&#39;re at the &quot;top level&quot; domain where you are (since this is a private DNS domain and doesn&#39;t come under the public TLD&#39;s).

To expand a little fisher.sherman.pft implies:
pvt -!
       sherman-!
                     fisher

and fisher-sherman-pvt implies:

fisher-sherman-pvt (all one domain, instead of 3).

so what would i do to have the implication of fisher.sherman.pvt?
create dns domains pvt sherman and fisher?

sherman.pvt   is the domain
fisher  is the member, which should be your server&#39;s name
(workstations do not need it defined unless you have to)


DNS Question

Can someone please explain to me (or point me to a good resource) as to why my site becomes available when using dashes instead of dots? For example, when i use

http://fisher-sherman-pvt, my site comes up fine. However, when I use http://fisher.sherman.pvt, I get &quot;The website can not be found&quot;

This is an internal site on a NT network, on a 2K3 server. I know this isn&#39;t much to go on, so if you need more specifics, let me know. I just thought maybe this was a common issue. THanks.

Networking is the process of connecting computing devices, peripherals and terminals together through a system that uses wiring, cabling or radio waves that enable their users to communicate, share information and interact over distances. Often associated are issues regarding operating systems, hardware and equipment, cloud and virtual networking, protocols, architecture, storage and management.

Networking

The Domain Name System (DNS) is a hierarchical, globally distributed system responsible for associating the name of a computer, service or other resource into an IP address for connecting to the Internet or a private network. Most prominently, it translates domain names to the numerical IP addresses needed for the purpose of computer services and devices worldwide.