Re: DNS Problem??
- From: "Herb Martin" <news@xxxxxxxxxxxxxx>
- Date: Sun, 8 May 2005 18:14:07 -0500
"Tom" <oldfatjedi@xxxxxxxxxxx> wrote in message
news:ea9lAbBVFHA.2420@xxxxxxxxxxxxxxxxxxxxxxx
> I am assisting someone install a new 2003 server (I am working remotely
2000
> miles away).
> I believe the problems point to DNS but I'm not sure.
Most AD problems really are DNS problems so it is
a good bet.
> The problems are:
>
> 1). Clients will not receive an address from the server's DHCP. I have to
> enable DHCP at the router for clients.
That is normal -- clients broadcast for the DHCP
server so any intevening routers must pass these
broadcasts -- or a relay agent must assist.
This isn't really a problem since you have fixed it
by enabling the router to provide DHCP or to assist
by forwarding the client broadcasts.
> 2). When attempting to login to the domain from a client station that has
> joined the domain, it takes 5 minutes to login.
The clients must be set to use STRICTLY the internal DNS
server (set) -- this usually explaines this problem but below
you seem to say that this is the case due to DHCP.
> 3). The DNS at the server doesn't update with client info (all client PC's
> are XP Pro).
The internal DNS (on the DC)? That must be set
to be dynamic. The clients must be set to use only
this server (or it's associated secondaries, etc.)
Since you say that the clients are correct (due to the
DHCP providing the correct, internal DNS server
address) then this implies that the DC itself is not
set to use the internal DNS server (itself in this case)
OR the DNS server is not dynamic.
> The DHCP currently provided by the router point DNS to the AD server.
If by "DNS at the AD Server" you mean the internal, dynamic
DNS server (set) that support the AD Domain, then that is the
only correct place.
> Everyone is able to access the internet properly and I can ping stations
by
> name or IP.
Then that would imply that the internal DNS (on the DC) is
setup correctly to forward to the Internet or resolve the
Internet correctly itself.
> DNS was installed (and reinstalled) with the default settings except for
the
> addition of a DNS forwarder (to the ISP DNS).
That is normally correct.
> Any ideas on how to troubleshoot this??
Make sure ALL the internal machines (especially the DC or
any other servers) use strictly the internal DNS.
Make sure the DNS is set to be dynamic for the zone.
Make sure all the machines list the correct Domain/Zone
name (your AD domain name) on their SYSTEM CONTROL
panel, so that each machine is name along this pattern:
computer.domain.com
Here is a general checklist of DNS for AD:
1) Dynamic for the zone supporting AD
2) All internal DNS clients NIC\IP properties must specify SOLELY
that internal, dynamic DNS server (set.)
3) DCs and even DNS servers are DNS clients too -- see #2
4) If you have more than one Domain, every DNS server must
be able to resolve ALL domains (either directly or indirectly)
netdiag /fix
....or maybe:
dcdiag /fix
(Win2003 can do this from Support tools):
nltest /dsregdns /server:DC-ServerNameGoesHere
http://support.microsoft.com/kb/q260371/
Ensure that DNS zones/domains are fully replicated to all DNS
servers for that (internal) zone/domain.
Also useful may be running DCDiag on each DC, sending the
output to a text file, and searching for FAIL, ERROR, WARN.
Single Label domain zone names are a problem Google:
[ "SINGLE LABEL" domain names DNS 2000 | 2003 microsoft: ]
--
Herb Martin, MCSE, MVP
Accelerated MCSE
http://www.LearnQuick.Com
[phone number on web site]
.
- Follow-Ups:
- Re: DNS Problem??
- From: IT Guy
- Re: DNS Problem??
- References:
- DNS Problem??
- From: Tom
- DNS Problem??
- Prev by Date: DNS Problem??
- Next by Date: Re: DNS Problem??
- Previous by thread: DNS Problem??
- Next by thread: Re: DNS Problem??
- Index(es):
Relevant Pages
|
