Re: DNS issue - clients not registering
- From: Johnny Figueroa <jfigueroa@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Tue, 26 Apr 2005 16:27:15 -0700
Take a look a your DHCP servers, I think the key is that you mentioned legacy
clients as the bulk of systems affected. Look at your DHCP server properties,
go to the DNS tab and take a good look. Make sure you are not using option
(2)
In Windows 2000, DHCP servers and clients can register with DNS to provide
this update service if the DNS server supports DNS with dynamic updates. The
Windows 2000 DNS service supports dynamic updates.
A Windows 2000 DHCP server can register with a DNS server and update pointer
(PTR) and address (A) resource records on behalf of its DHCP-enabled clients
using the DNS dynamic update protocol. The ability to register both A and PTR
type records lets a DHCP server act as a proxy for clients using Microsoft
Windows 95 and Windows NT 4.0 for the purpose of DNS registration. DHCP
servers can differentiate between Windows 2000 and other clients. An
additional DHCP option code (option code 81) enables the return of a client's
FQDN to the DHCP server. If implemented, the DHCP server can dynamically
update DNS to modify an individual computer's resource records with a DNS
server using the dynamic update protocol. This DHCP option permits the DHCP
server the following possible interactions for processing DNS information on
behalf of DHCP clients that include Option Code 81 in the DHCPRequest message
they send to the server:
1. The DHCP server always registers the DHCP client for both the forward
(A-type records) and reverse lookups (PTR-type records) with DNS.
2. The DHCP server never registers the name-to-address (A-type records)
mapping information for DHCP clients.
3. The DHCP server registers the DHCP client for both forward (A-type
records) and reverse lookups (PTR-type records) only when requested to by the
client
We use option 3, this is the default behavior: For Windows 2000 Clients, the
Client updates its forward (A) name with DNS servers. The DHCP Server updates
the DNS reverse (PTR) name for the client. For clients prior to Windows 2000,
the DHCP Server automatically updates both the forward (A) name and reverse
(PTR) names for the client
If tha takes you nowhere, you may want to look at this DNSUpdateProxy group
in AD, http://msmvps.com/ulfbsimonweidner/archive/2004/11/15/19325.aspx
"kevw" wrote:
> If you have the zone named RSD then you indeed have a single label domain
> name. Not good. You will always have DNS issues in 2003. See article KB300684:
>
> http://support.microsoft.com/default.aspx?scid=kb;en-us;300684
>
> kevw
>
> "Joe Heaton" wrote:
>
> > Wow, first off, thank you for the responses. Now that we have some
> > suggestions out there, let me give you some background information that
> > hopefully will help out.
> >
> > I work at a small school district, with 5 physical sites. We run Server
> > 2k3, with most of the servers having SP1. We had a server at each site with
> > AD loaded on it. We started having some pretty major DNS related slowdowns,
> > so we took a step back and decided to:
> >
> > 1) Demote all servers except for one at our central site, by removing AD
> > from them.
> > 2) Consolidate DNS by removing DNS services from all servers except for our
> > central site.
> > 3) Remove our second domain, which was setup for our webserver only.
> >
> > If I look in my DNS server at the forward lookup zones, I have two. One, is
> > the single name zone RSD (Robla School District), which is the one that I
> > want. The other is robla.k12.ca.us, which is the zone based on our webserver.
> >
> > Here are my issues:
> >
> > 1) I have less than half of my clients registered in DNS at all.
> > 2) I have around 40 or so clients that are registered in the robla.k12.ca.us
> > forward lookup zone, instead of the other one.
> > 3) I have lots of computers now that are giving me the error we have already
> > discussed.
> >
> >
> > I checked my zones yesterday. RSD is set to accept secure and nonsecure
> > updates. The other was set to accept secure, I changed it to accept either,
> > just to see if that is the zone these machines are trying to register in.
> > I've looked at my DHCP, which is running at each site individually, since
> > they are all separate subnets, and I didn't want to centralize that at this
> > point. DHCP is assigning the DNS server, it is also assigning the DNS suffix
> > as the one that I want. I don't have a dot in front of the zone name in
> > DHCP, do I need one?
> >
> > Anyway, hopefully someone out there will read this loooong post, and help me
> > out. I looked at the KB that Paul suggested, but it's for 2000, is that
> > still applicable for 2K3?
> >
> >
> > Thanks for all the help guys,
> >
> > Joe Heaton
.
- References:
- DNS issue - clients not registering
- From: Joe Heaton
- Re: DNS issue - clients not registering
- From: ptwilliams
- Re: DNS issue - clients not registering
- From: Joe Heaton
- Re: DNS issue - clients not registering
- From: kevw
- Re: DNS issue - clients not registering
- From: Joe Heaton
- Re: DNS issue - clients not registering
- From: kevw
- DNS issue - clients not registering
- Prev by Date: Re: Group Policy
- Next by Date: DNS Client, Invalid record returned from DNS Server
- Previous by thread: Re: DNS issue - clients not registering
- Next by thread: HELP - Must Remove AD but can only access DSRMode!
- Index(es):
Relevant Pages
|
|
