|
|
Hi,
I have two seperate 2003 forests. A DHCP server is running in FOREST1. I
have XP Clients in FOREST2 which get their IP and DNS details from the DHCP
server in FOREST1.
The XP Clients are correctly registering and updating their A record in DNS
in FOREST2, but are not registering themselves in the Reverse Lookup Zone.
So far, I have tried using group policy to force the DNS client to "Register
PTR Records". I have also tried statically adding the FOREST2 DNS servers to
the client.
The client machines are configured to "Register this connection's addresses
in DNS".
Can anyone give me any suggestions in how to get the PTR records registering
correctly?
The only time it seems to work is if I assign a static IP to the clients,
which I really want to avoid!!
Thanks,
Curtis.
--
Please reply to news group only. Thank you.
|
|
In news:e4h8Q0zrHHA.1204[ at ]TK2MSFTNGP04.phx.gbl,
Curtis Fray <xxx[ at ]xxx.com> typed:
[Quoted Text] > Hi,
>
> I have two seperate 2003 forests. A DHCP server is running in
> FOREST1. I have XP Clients in FOREST2 which get their IP and DNS
> details from the DHCP server in FOREST1.
>
> The XP Clients are correctly registering and updating their A record
> in DNS in FOREST2, but are not registering themselves in the Reverse
> Lookup Zone.
> So far, I have tried using group policy to force the DNS client to
> "Register PTR Records". I have also tried statically adding the
> FOREST2 DNS servers to the client.
>
> The client machines are configured to "Register this connection's
> addresses in DNS".
>
> Can anyone give me any suggestions in how to get the PTR records
> registering correctly?
>
> The only time it seems to work is if I assign a static IP to the
> clients, which I really want to avoid!!
>
> Thanks,
>
> Curtis.
If it works with static configs, then it;s a DHCP issue. Check how you have
registrations set in DHCP properties, DNS tab. Also, you may want to make
sure the zone is not set to secure updates. You can also use DNS in their
own Forest and setup a zone transfer to your DNS server for the zone.
--
Regards,
Ace
This posting is provided "AS-IS" with no warranties or guarantees and
confers no rights.
Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSE+I, MCT, MVP
Microsoft MVP - Directory Services
Microsoft Certified Trainer
Infinite Diversities in Infinite Combinations
Having difficulty reading or finding responses to your post?
Instead of the website you're using, try using OEx (Outlook Express
or any other newsreader), and configure a news account, pointing to
news.microsoft.com. Anonymous access. It's free - no username or password
required nor do you need a Newsgroup Usenet account with your ISP. It
connects directly to the Microsoft Public Newsgroups. OEx allows you
o easily find, track threads, cross-post, sort by date, poster's name,
watched threads or subject. It's easy:
How to Configure OEx for Internet News
http://support.microsoft.com/?id=171164
"Quitting smoking is easy. I've done it a thousand times." - Mark Twain
|
|
Hi Curtis Fray,
I have very same problem. The only difference is that my DHCP is
running on a Windows 2000 having Windows 2003 Servers on other side (in
forest2).
As I know, Windows XP DHCP clients are registering A records themselves
and are asking DHCP server to register PTR records for them. So, my
understanding is that DHCP server is registering PTR with the DNS from
its own (server’s) DNS settings. Usually those are the DNSes from the
same forest (forest1). So, you might find those PTRs in forest1.
[I was looking on exact information as how DHCP server determines which
DNS is to register PTR record with, but have not found detailed
information anywhere yet. Thus, I assume it just takes 1st DNS from the
it’s adapter DNS settings. If we can find detailed description for this
process, there could be a solution or at least an answer on whether it
is possible to modify the behaviour of DHCP-DNS PTR records
registration.]
I’ve also tried to force a client to register PTR through the GPO, but
looks like GPO has no effect at all in those regards. The record still
appears in forest1 Revers Lookup Zone.
Another thing I was looking at is to group those clients from forest2
on DHCP server and assign them DNS servers from forest2. Then get them
to register their PTR records themselves. That even worked once, but as
I went to implement that with the help of GPO, for some reason it
stopped. In details, I’ve done all of that via following configuration:
- define a User Class on a DHCP server for those clients from forest2
- set 006 DNS Servers option on DHCP server for that class and put in
there DNS from forest2 (that will override default 006 option)
- assign User Class on client computer for network adapter (with
ipconfig /setclassid)
- get client to register it’s PTR by himself:
a) in TCPIP Properties->DNS, DNS Suffix for this connection: domain
from forest2
b) Tick Use this connection’s DNS Suffix in DNS registration
But the problem is that when configuring last step via GPO, I tend to
believe that it’s just not happening. And overall, is looks a bit
complex.
I hoping to find alternative ways to solve that.
--
PanTzeR
------------------------------------------------------------------------
PanTzeR's Profile: http://forums.techarena.in/member.php?userid=26871
View this thread: http://forums.techarena.in/showthread.php?t=766447
http://forums.techarena.in
|
|
-Update for my previous post. -
I’ve done a bit of testing and found a way to have PTR registration
done as I want.
In order to have Windows XP computers from forest2 (that got IP from
DHCP.forest1) to have PTR registered with DNS.forest2 we need to force
DHCP client to register PTR by himself with DNS.forest2.
By default, a DHCP server is set up to register PTR for the client (as
per RFC “Interaction between DHCP and DNS”). And in our case,
DHCP.forest1 server will do it with the DNS.forest1 server as the one
responsible for maintaining the Reverse Lookup Zone (you can check that
DNS.forest1 is the SOA for that zone in forest1 DNS servers). As we will
not try to change DHCP behaviour or SOA set up for that zone on
DNS.forest1, we can ask the client to register PTR with the
DNS.forest2. For that, we need to make sure that:
a) DHCP client have his DNS set to DNS.forest2
b) The client is set to register PTR by himself
Both of that might be done through the GPO. Settings to look for are
located in GPO->Administrative Templates->Network->DNS Client. There
you need to change:
- DNS Servers setting: to your DNS.forest2 (this will override DHCP
settings), and
- Register DNS records with connection-specific DNS suffix: Enable (to
force PTR registration by the client).
Thus, at the end, when I’ve done testing as above, I’ve ended up having
proper PTR records for forest1 (registered by DHCP) and forest2
(registered by the GPO-abiding client).
Unfortunately, we decided not to go this way, but to consolidate
everything in one forest (forest2). As we will gradually move from
another one anyway.
Hope this helps!
*Regards,
PanTzeR*
--
PanTzeR
------------------------------------------------------------------------
PanTzeR's Profile: http://forums.techarena.in/member.php?userid=26871
View this thread: http://forums.techarena.in/showthread.php?t=766447
http://forums.techarena.in
|
|
In news:PanTzeR.2sgw7g[ at ]DoNotSpam.com,
PanTzeR <PanTzeR.2sgw7g[ at ]DoNotSpam.com> typed:
[Quoted Text] > -Update for my previous post. -
>
> I've done a bit of testing and found a way to have PTR registration
> done as I want.
>
> In order to have Windows XP computers from forest2 (that got IP from
> DHCP.forest1) to have PTR registered with DNS.forest2 we need to force
> DHCP client to register PTR by himself with DNS.forest2.
>
> By default, a DHCP server is set up to register PTR for the client (as
> per RFC "Interaction between DHCP and DNS"). And in our case,
> DHCP.forest1 server will do it with the DNS.forest1 server as the one
> responsible for maintaining the Reverse Lookup Zone (you can check
> that DNS.forest1 is the SOA for that zone in forest1 DNS servers). As
> we will not try to change DHCP behaviour or SOA set up for that zone
> on DNS.forest1, we can ask the client to register PTR with the
> DNS.forest2. For that, we need to make sure that:
>
> a) DHCP client have his DNS set to DNS.forest2
> b) The client is set to register PTR by himself
>
> Both of that might be done through the GPO. Settings to look for are
> located in GPO->Administrative Templates->Network->DNS Client. There
> you need to change:
> - DNS Servers setting: to your DNS.forest2 (this will override DHCP
> settings), and
> - Register DNS records with connection-specific DNS suffix: Enable (to
> force PTR registration by the client).
>
> Thus, at the end, when I've done testing as above, I've ended up
> having proper PTR records for forest1 (registered by DHCP) and forest2
> (registered by the GPO-abiding client).
>
> Unfortunately, we decided not to go this way, but to consolidate
> everything in one forest (forest2). As we will gradually move from
> another one anyway.
>
> Hope this helps!
>
> *Regards,
> PanTzeR*
The only issue I see with forcing DNS client settings to use the other
forest's DNS is the client's current domain records are on it's own DNS.
This was why I suggested secondary zones.
Ace
|
|
Thanks very much for all the info. That's a great help!
Cheers,
Curtis.
[Quoted Text] > --
> Please reply to news group only. Thank you.
>
|
|
In news:eudihU9sHHA.2444[ at ]TK2MSFTNGP06.phx.gbl,
Curtis Fray <xxx[ at ]xxx.com> typed:
[Quoted Text] > Thanks very much for all the info. That's a great help!
>
> Cheers,
>
> Curtis.
Good luck! If you have any other questions, please post back.
Ace
|
|
|