Dynamic DNS

[Stuart Carrison]

Experts,

A little advice please:

I have a W2K DC running RRAS in with a single ADSL connection NAT'ing my
LAN.

Obviously only TCP/IP is bound to the external interface 'remote router'.

Despite having the 'Register this connection's addresses in DNS' _un-ticked_
on the RRAS box, whenever the ADSL connection is established my external IP
is registered on the W2K dynamic DNS (which must stay dynamic to support the
internal clients), along with an IP reserved by RRAS for dial-in clients.

Please can you tell me how I can stop my external IP and the RRAS reserved
IP from being registered in DNS?

Appreciate your time,

Stuart

P.S. Since I don't check the group too often it would be a help if you could
cc: my e-mail address (minus the obvious spam block) with any replies.

 

[Kevin D. Goodknecht [MVP]]

In

Experts,

A little advice please:

I have a W2K DC running RRAS in with a single ADSL connection NAT'ing
my LAN.

Obviously only TCP/IP is bound to the external interface 'remote
router'.

Despite having the 'Register this connection's addresses in DNS'
_un-ticked_ on the RRAS box, whenever the ADSL connection is
established my external IP is registered on the W2K dynamic DNS
(which must stay dynamic to support the internal clients), along with
an IP reserved by RRAS for dial-in clients.

Please can you tell me how I can stop my external IP and the RRAS
reserved IP from being registered in DNS?

Appreciate your time,

Stuart

P.S. Since I don't check the group too often it would be a help if
you could cc: my e-mail address (minus the obvious spam block) with
any replies.

There is a few things you need to do.
Start by using the DNS Management console, right click on the server name
choose properties, on the interfaces tab select listen only on the internal
IP address.

Then right click on Network Places, choose properties, then in the Advanced
Menu select Advanced Settings. In the connections pane make sure your
internal interface is at the top of the list and that Client for MS Networks
and File Sharing are only bound to that interface, not to the external
interface.

Use regedt32 to add this registry entry to stop the creation of the (same as
parent folder) records for all IPs then manually create the record noted
below.
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Netlogon\Parameters

Registry value: DnsAvoidRegisterRecords
Data type: REG_MULTI_SZ
Values: LdapIpAddress

Then manually create a new host leaving the name field blank give it the IP
of the internal interface in you domain's Forward Lookup zone. It will bark
at you saying (same as parent folder) is not a valid host name click OK to
create the record anyway.

 

[Stuart Carrison]

Thanks!

In

There is a few things you need to do.
Start by using the DNS Management console, right click on the server name
choose properties, on the interfaces tab select listen only on the internal
IP address.

Then right click on Network Places, choose properties, then in the Advanced
Menu select Advanced Settings. In the connections pane make sure your
internal interface is at the top of the list and that Client for MS Networks
and File Sharing are only bound to that interface, not to the external
interface.

Use regedt32 to add this registry entry to stop the creation of the (same as
parent folder) records for all IPs then manually create the record noted
below.
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Netlogon\Parameters

Registry value: DnsAvoidRegisterRecords
Data type: REG_MULTI_SZ
Values: LdapIpAddress

Then manually create a new host leaving the name field blank give it the IP
of the internal interface in you domain's Forward Lookup zone. It will bark
at you saying (same as parent folder) is not a valid host name click OK to
create the record anyway.