Re: Stand Alone Networks, Their Domain Names, and DNS

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

Richard,

Thanks for all the help!

Don



"Richard G. Harper" <rgharper@xxxxxxxxx> wrote in message
news:eVE3KlNYGHA.3448@xxxxxxxxxxxxxxxxxxxxxxx
The .local form of the name is the FQDN (Fully Qualified Domain Name) of
your network. The NetBIOS name is just the prefix.

I would recommend you run DNS in your domain. If you are running Active
Directory you will need DNS to allow it to function properly. Without it,
PCs will be slow logging onto the domain, if you have more than one domain
controller they will be unable to synchronize to each other, and so on.

--
Richard G. Harper [MVP Shell/User] rgharper@xxxxxxxxx
* PLEASE post all messages and replies in the newsgroups
* for the benefit of all. Private mail is usually not replied to.
* My website, such as it is ... http://rgharper.mvps.org/
* HELP us help YOU ... http://www.dts-l.org/goodpost.htm


<emq_33@xxxxxxxxxxx> wrote in message
news:1145023123.972678.260240@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

Richard,

My DNS question sort of comes from the ponderable: "If there is a
single domain (labdomain.local), does it make sense to have a domain
name server (DNS) since there are no other domains?" Admittedly a
naive view of the world! But what role will a DNS serve in a single
domain network? And if it does serve a role, what, if any, special
considerations are there since there is only one domain. While I
understand the macro concepts, these special situations (at least in my
mind!) perplex me!

The NetBIOS/DNS explanation for the different versions of the domain
name helps a lot!! Is the .local domain name form considered good
practice in the situation of a standalone network? Or is there a
preferred naming scheme? In terms of NetBIOS vs DNS resolution, is
having the two systems and acceptable fact of life? Or should I be
working to one or the other?

Thanks for the naming explanation!

Don


Richard G. Harper wrote:
Depending on what tool or utility you're using you can see either the
NetBIOS name for the domain (labdomain) or the DNS name for the domain
(labdomain.local). Which one you'll see depends on whether the tool or
utility is using NetBIOS name resolution or DNS name resolution.

Not sure what your question about DNS is - can you explain further?

--
Richard G. Harper [MVP Shell/User] rgharper@xxxxxxxxx
* PLEASE post all messages and replies in the newsgroups
* for the benefit of all. Private mail is usually not replied to.
* My website, such as it is ... http://rgharper.mvps.org/
* HELP us help YOU ... http://www.dts-l.org/goodpost.htm


"Don" <someone@xxxxxxxxxxxxx> wrote in message
news:ut7U7Y1XGHA.3448@xxxxxxxxxxxxxxxxxxxxxxx
We have a Win2000 server in our lab supporting user authentication,
print
serving, and file serving. There is not (and never will be) a
connection
to
the internet. The admin who set up the system named the domain
"labdomain".
I have been "promoted" to administer this system and am curious about
the
domain name. In some contexts I see "labdomain" and in others I see
"labdomain.local" Unfortunately, the references I have looked at
don't
really discuss domains that are not connected to the internet.
Especially
omitting discussions of the ".local" suffix.

A couple of questions:

1) Given that the network the server is on is a stand alone network,
is
the
name "labdomain" or "labdomain.local" appropriate?

2) Are "labdomain" and "labdomain.local" interchangeable? Aliases
for
each
other?

3) What are the implications, if any, for configuring the DNS as it
is
a
single domain?

Any comments or pointers to references will be greatly appreciated!

Thanks!

Don









.

Relevant Pages

  • Re: Cannot browse the network after migration
    ... nothing missing(DNS, GW, WINS all defined in all machines, DNS & WINS point to the DC) ... If you have WINS on the network. ... > 188305 Troubleshooting the Microsoft Computer Browser Service ... > 189101 Understanding NetBIOS Resource Record Flags ...
    (microsoft.public.windows.server.migration)
  • Re: DHCP, DNS, NETBIOS and WINS
    ... > DNS resolves the IP address of the PC against a pc's name, ... > DHCP assigns an available IP address to a PC which logs onto the network, ... and this was adapted to use IP addresses with Netbios over TCP/IP. ...
    (microsoft.public.windows.server.networking)
  • Re: Stand Alone Networks, Their Domain Names, and DNS
    ... your network. ... The NetBIOS name is just the prefix. ... Directory you will need DNS to allow it to function properly. ... * PLEASE post all messages and replies in the newsgroups ...
    (microsoft.public.win2000.networking)
  • Re: computer name length issue
    ... This length is reflective of the old NETBIOS computer name which was 8 characters, 15 on then newer Windows OSes. ... However, what Microsoft did a long time ago when they finally added Internet support over its NETBIOS based LAN support, was WINS which ties the IP address of the machine with the netbios computer name. ... That is only TRUE when the network administrator has made it that way via DNS and WINS. ...
    (microsoft.public.vc.language)
  • Re: NBTSTAT problem : "-a" works, "-A" not.
    ... > NBTSTAT stands for NetBIOS over TCP Status. ... > LMHOSTS table showing all the machines on your network or a WINS Server, ... Microsoft DNS resolution may ...
    (microsoft.public.win2000.networking)