Difference between DNS and WINS and best practice

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

Guest

Hi, i'm currently running Windows 2000 Domain with AD and all my clients are
running Windows XP with SP2.

I do understand a little bit of DNS and WINS but not much cause i'm still a
newbie and i would like to hear it from an expert , can anyone please tell me
the difference between DNS and WINS and what would happen if i don't use them
in my domain environment ?

I have 2 DCs , 1 is Primary and another is secondary, do i install DNS &
WINS service on both of them ?
 
aznan said:
Hi, i'm currently running Windows 2000 Domain with AD and all my clients
are
running Windows XP with SP2.

I do understand a little bit of DNS and WINS but not much cause i'm still
a
newbie and i would like to hear it from an expert , can anyone please tell
me
the difference between DNS and WINS and what would happen if i don't use
them
in my domain environment ?
Click to expand...

They are similar enough to confuse even some of those who think they
are experts since they "resolve names to IP addresses" -- DNS resolves
the names used on the Internet (e.g., www.google.com) and WINS
resolves "NetBIOS" names to IP addresses.

NetBIOS was used historically for networking Microsoft (& IBM) networks
and is still use mainly for Browsing, external trusts, and a few other minor
feature including even some things in Exchange and Cluster services.

DNS is now, as of Win2000 and Active Directory, required for your domain
to work well.

In fact, most problems with AD replication OR authentication are actually
DNS
issue. And in many cases, problems with resource access or slow logons are
also due to DNS problems.
I have 2 DCs , 1 is Primary and another is secondary, do i install DNS &
WINS service on both of them ?
Click to expand...

DNS almost for sure. Otherwise you will have problems when one DC is
down, even for short reboots.

You only need WINS servers if you have more than one Subnet, although
having a WINS server can reduce broadcasts. On a single subnet (i.e.,
no internal routers) the broadcasts can resolve the NetBIOS names without
the WINS server(s).

If you wish fault tolerance for NetBIOS names across routers you will
also need to have that second WINS Server.

All internal clients, especially DCs and servers, must be set STRICTLY
as clients of the Internet DNS server, and also of the WINS Server on
the NIC->IP Properties.
 
DNS = hierarchical name resolution system for FQDNs to IP (e.g.
COMPUTER.DOMAIN.COM --> 10.1.1.1 = forward name resolution) or IP to FQDNs
(e.g. 10.1.1.1 --> COMPUTER.DOMAIN.COM = reverse name resolution)
WINS = flat name resolution system for COMPUTERNAME to IP (e.g. COMPUTER -->
10.1.1.1)


DNS is a MUST for AD! cannot argue with that
WINS was needed for NT4 environments (actually NetBIOS as WINS is just the
name resolution mechanism). AD environments might need WINS, that really
depends if you have legacy apps or systems that use NetBIOS name resoulution

--

Cheers,
(HOPEFULLY THIS INFORMATION HELPS YOU!)

# Jorge de Almeida Pinto # MVP Windows Server - Directory Services

BLOG (WEB-BASED)--> http://blogs.dirteam.com/blogs/jorge/default.aspx
BLOG (RSS-FEEDS)--> http://blogs.dirteam.com/blogs/jorge/rss.aspx
 
Guys thanks a lot for the information....appreciate your prompt replies.
--
The International School of Penang (Uplands)


Jorge de Almeida Pinto said:
best practices... forgot these

for DNS:
http://blogs.dirteam.com/blogs/jorg...configure-DNS-in-an-AD-environment_3F00_.aspx

for WINS:
http://technet2.microsoft.com/WindowsServer/en/library/ed9beba0-f998-47d2-8137-a2fc52886ed71033.mspx

--

Cheers,
(HOPEFULLY THIS INFORMATION HELPS YOU!)

# Jorge de Almeida Pinto # MVP Windows Server - Directory Services

BLOG (WEB-BASED)--> http://blogs.dirteam.com/blogs/jorge/default.aspx
BLOG (RSS-FEEDS)--> http://blogs.dirteam.com/blogs/jorge/rss.aspx
------------------------------------------------------------------------------------------
* How to ask a question --> http://support.microsoft.com/?id=555375
------------------------------------------------------------------------------------------
* This posting is provided "AS IS" with no warranties and confers no rights!
* Always test before implementing!
------------------------------------------------------------------------------------------
#################################################
#################################################
------------------------------------------------------------------------------------------
"Jorge de Almeida Pinto [MVP - DS]"
DNS = hierarchical name resolution system for FQDNs to IP (e.g.
COMPUTER.DOMAIN.COM --> 10.1.1.1 = forward name resolution) or IP to FQDNs
(e.g. 10.1.1.1 --> COMPUTER.DOMAIN.COM = reverse name resolution)
WINS = flat name resolution system for COMPUTERNAME to IP (e.g.
COMPUTER --> 10.1.1.1)


DNS is a MUST for AD! cannot argue with that
WINS was needed for NT4 environments (actually NetBIOS as WINS is just the
name resolution mechanism). AD environments might need WINS, that really
depends if you have legacy apps or systems that use NetBIOS name
resoulution

--

Cheers,
(HOPEFULLY THIS INFORMATION HELPS YOU!)

# Jorge de Almeida Pinto # MVP Windows Server - Directory Services

BLOG (WEB-BASED)--> http://blogs.dirteam.com/blogs/jorge/default.aspx
BLOG (RSS-FEEDS)--> http://blogs.dirteam.com/blogs/jorge/rss.aspx
Click to expand...
Click to expand...
 
Back
Top