Re: Cant ping Domain by Name but can by FQDN
- From: "Todd J Heron" <todd_heron(delete)@hotmail.com>
- Date: Tue, 22 Nov 2005 10:30:25 -0500
"Tecnik" <Tecnik@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message...
>I have a domain called Testlabuk.local when at the command prompt I can
>ping testlabuk.local but cannot ping testlabuk. This is causing >machines
>saying the domain is not available. I'm sure it is a record I am missing
>but cannot see where to look. I have two DNS servers for >this domain and
>both have their A host record registered.
Could be one of several reasons. Your DNS domain name is Testlabuk.local
but the NetBIOS domain name is Testlabuk. A ping to Testlabuk assumes a
NetBIOS query and the Windows client will look at a WINS (or LMHosts file)
before trying DNS. If not Lmhosts or WINS is configured, the Windows client
will look in DNS in the zone matching it's domain membership
(Testlabuk.local) and then in other zones according to it's DNS Search
Suffix. When all of these fail an error will return such as you have
received. I don't think an A record matching the NetBIOS name of the domain
is created automatically in DNS when you build a domain. If you create an A
record called Testlabuk in the Testlabuk.local zone it will work. But I
would not do that as it can cause confusion. If you install WINS these
problems will go away. Some AntiVirus, Backup software and Exchange needs
NetBIOS functionality so you should install WINS. Legacy clients such as
Win95/98 and NT 4.0 also need WINS to find the domain.
--
Todd J Heron, MCSE
Windows Server 2003/2000/NT; CCA
----------------------------------------------------------------------------
This posting is provided "as is" with no warranties and confers no rights
.
- Prev by Date: Re: Windows 2003 DNS Issues
- Next by Date: Re: WINDOWS 2003
- Previous by thread: Registration of DNS records failed: The RPC server is unavailable
- Next by thread: Re: WINDOWS 2003
- Index(es):
Relevant Pages
|
Loading