Internal RRAS address registering in DNS causing problems

[Darin]

Whenever someone connects to our RRAS server it registers
the RRAS internal address in DNS. This in turn can cause
problems with workstation on the network connecting to
certain things on this server. (Yes, it's a DC) I found MS
Q article explaining that this is expected behaviour if
RRAS is installed on a DC. They suggested removing the
Internal RRAS address from being a listner interface for
DNS. Done that, but record still registered. Next thing
they recommend is setting up a registry key called
PublishAdresses and specifying each address that DNS would
allow for registration. Is there an easier way or can I
enter a range value instead of individual addresses? My
current allowable DHCP range .20 through .239 on a class C
subnet (about 210 individual addresses), so all of these
need entered so they can still use DDNS.

 

[Bill Grant]

Do you mean KB 289735? You seem to have misread what it says. You are only
preventing the server service from registering addresses with DNS, not
preventing clients from registering.

In Publish Addresses, you only list the IP addresses you want registered
for your domain controller. Usually this is just the LAN IP.

 

[Chetan Raghavendra [MSFT]]

Hi Darin,

Darin: "This in turn can cause problems with workstation on the network
connecting to certain things on this server."

Can you please let me know why registering of internal RRAS address would
cause this? Can you explain in detail what the above problem is?

Did you reboot the machine after chagning the registry settings? Article at
http://support.microsoft.com/default.aspx?scid=kb;EN-US;246804 which
explains this type of configuration suggests to do this.
--
Thanks
Chetan
(e-mail address removed)

This posting is provided "AS IS" with no warranties, and confers no rights.