"kj" wrote:

>
> "Mike55" <Mike55@discussions.microsoft.com> wrote in message
> news:F6FF5070-F705-43E7-9F93-6E85B5ACF589@microsoft.com...
> >
> >
> > "Herb Martin" wrote:
> >
> >> "Kevin D. Goodknecht Sr. [MVP]" <admin@nospam.WFTX.US> wrote in message
> >> news:O28C7Bu%23GHA.4428@TK2MSFTNGP04.phx.gbl...
> >> > Herb Martin wrote:
> >> >
> >> >> Not an issue if he only has one DHCP server OR if
> >> >> his DHCP servers have never registered the record
> >> >> (they aren't yet fighting over it.)
> >> >
> >> > I guess you missed this in Mike's OP.
> >> >> I have a Windows 2003 domain with 2 2003 DHCP servers and 3 DNS
> >> >> servers
> >> >
> >>
> >> No, not really -- the key was that he didn't see to be
> >> getting ANY updates for Macs (ever) and had no
> >> problems (yet) with other machines.
> >>
> >> Eventually he has to deal with the credentials if
> >> the two DHCP servers lease to (any of) the same
> >> names (clients more from subnet to subnet or both
> >> DHCP servers offer on same subnets.)
> >>
> >> That is your point and he he needs to know about
> >> that so you did well too inform him, but it isn't going
> >> to fix his initial problem and therefore needs to be
> >> differentiated from the direct issue in the question.
> >>
> >> --
> >> Herb Martin, MCSE, MVP
> >> Accelerated MCSE
> >> http://www.LearnQuick.Com
> >> [phone number on web site]
> >>
> >> "Kevin D. Goodknecht Sr. [MVP]" <admin@nospam.WFTX.US> wrote in message
> >> news:O28C7Bu%23GHA.4428@TK2MSFTNGP04.phx.gbl...
> >> > Herb Martin wrote:
> >> >
> >> >> Not an issue if he only has one DHCP server OR if
> >> >> his DHCP servers have never registered the record
> >> >> (they aren't yet fighting over it.)
> >> >
> >> > I guess you missed this in Mike's OP.
> >> >> I have a Windows 2003 domain with 2 2003 DHCP servers and 3 DNS
> >> >> servers
> >> >
> >> >
> >> >>
> >> >> The point of the credentials is to give all of the
> >> >> DHCP servers which might ever update the record
> >> >> the same account so the record will (effectively) be
> >> >> owned in common.
> >> >
> >> > The best point of the credentials is so the DHCP servers maintain
> >> > single
> >> > ownership of the records all DHCP servers create. Otherwise, "Delete A
> >> > and
> >> > PTR records when lease expires" won't happen because the DHCP servers
> >> > doesn't have ownership. This function comes in real handy for removing
> >> > PTR
> >> > records for laptops that register their own records and are usually
> >> > suddenly
> >> > disconnected without releasing their IP lease leaving the PTRs in DNS.
> >> > It's
> >> > not a big problem for A records because laptops are not usually not
> >> > renamed
> >> > while disconnected and can easily overwrite A records with its name
> >> > because
> >> > it owns it. The next time the laptop is connected, it may not be able
> >> > to
> >> > lease the same IP and it cannot update a record it does not own, so it
> >> > just
> >> > registers another PTR.
> >> >
> >> >
> >> > --
> >> > Best regards,
> >> > Kevin D. Goodknecht Sr. [MVP]
> >> > Hope This s
> >> > ===================================
> >> > When responding to posts, please "Reply to Group"
> >> > via your newsreader so that others may learn and
> >> > benefit from your issue, to respond directly to
> >> > me remove the nospam. from my email address.
> >> > ===================================
> >> > http://www.lonestaramerica.com/
> >> > http://support.wftx.us/
> >> > http://message.wftx.us/
> >> > ===================================
> >> > Use Outlook Express?... Get OE_Quotefix:
> >> > It will strip signature out and more
> >> > http://home.in.tum.de/~jain/software/oe-quotefix/
> >> > ===================================
> >> > Keep a back up of your OE settings and folders
> >> > with OEBackup:
> >> > http://www.oe.com/OEBackup/Default.aspx
> >> > ===================================
> >> >
> >> >
> >>
> >>
> >>
> >
> > Thanks for all your input so far! Here's some more info:
> >
> > I have several hundred windows 2k/xp clients and a couple dozen windows
> > 2k/2k3 servers all working fine in my domain. The DHCP, DNS, and domain
> > controllers are all the same machines. So I have:
> > SERVER1: Win2k3 Domain Controller, DNS, DHCP
> > SERVER2: Win2k3 Domain Controller, DNS, DHCP
> > SERVER3: Win2k Domain Controller, DNS (legacy server soon to be retired)
> >
> > The mac client I am working on is a OS X 10.3 with all latest updates. I
> > can bind it to AD and AD recognizes it fine. I can also login to the Mac
> > using an AD domain account and connect to windows server shared drives,
> > etc.
> > The Mac gets a DHCP lease successfully, and it is pingable by ip, but in
> > doing a ping -a to the ip, the name is not resolved, nor is the computer
> > added to DNS. The DHCP server does list the computer by computer name,
> > but
> > cannot ping it.
> >
> > I did add user credentials to the DHCP properties just to make sure that's
> > not the problem, but it doesn't seem to have made any difference.
> >
> > I haven't tried restarting DHCP or DNS, yet, so that may be in order.
> >
> > Any other ideas?
> >
> > Can you get a Mac OS X client onto your AD domain and get it working with
> > your DHCP/DNS systems? Maybe we can compare configs...
>
>
> On the DHCP server properties, check the last box under DNS that reads;
>
> "Dynamically update DNS A and PTR records for DHCP clients tha do not
> request updates..."
>
> That should do it, but I might restart the DHCP server service just to make
> sure.
>
> ---
> /kj
>
>
>

I have found the solution. I had already selected these options on the DHCP
server:

'Enable DNS dymanic updates according to the settings below:'
'Always dynamically update DNS A and PTR records'
'Discard A and PTR records when lease is deleted'
'Dynamically update DNS A and PTR records for DHCP clients that do not
request updates (for example, clients running Windows NT 4.0)'

What I tried this morning was to also check these options on the SCOPE for
each DHCP server. I restarted DHCP services and now my non-windows DHCP
clients (Mac OS X and Linux) are listed in DNS. So it appears that either
you need to have the options checked on both the DHCP server and SCOPE or at
least have them set on the SCOPE...