fix a dns host record

  • Thread starter Thread starter simon
  • Start date Start date
S

simon

Does anyone know how to manually set a DNS host record
and prevent it from being updated?

In our win 2000 Domain we use DDNS but I have recently
set up a server off-site and want to fix its DNS record
as the router's public IP rather than the server's
private IP.

Any advice is appreciated, Rgds, Simon.
 
In
simon said:
Does anyone know how to manually set a DNS host record
and prevent it from being updated?

In our win 2000 Domain we use DDNS but I have recently
set up a server off-site and want to fix its DNS record
as the router's public IP rather than the server's
private IP.

Any advice is appreciated, Rgds, Simon.
Click to expand...


If I understand what youre trying to do, you may need a separate DNS server
to do this. If you change the DC's record to a different IP than what it's
registering (what the machine is configured to use), then numerous errors
may result.

What are the reasons, if I may ask?

--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.
This posting is provided "AS-IS" with no warranties and confers no
rights.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory

HAM AND EGGS: A day's work for a chicken; A lifetime commitment for a
pig. --
=================================
 
The reason I want to use the public IP of the router is
to allow the off-site server to be part of the same
domain and replicate AD.

Is there another way to allow the routing? For example
could I setup a permanent route to the off-site server
through the router's IP?
 
In
Simon said:
The reason I want to use the public IP of the router is
to allow the off-site server to be part of the same
domain and replicate AD.

Is there another way to allow the routing? For example
could I setup a permanent route to the off-site server
through the router's IP?
Click to expand...

I see. So let me get this straight, one DC is behind a NAT and the other one
is on a public IP range? This will get you in trouble due to the fact that
domain coimmunication won;t work thru a NAT. Actually, Kerberos, LDAP and
RPC will not work thru NAT. The way to make this work is to utilize a VPN
tunnel using the NAT devices as endpoints, provided that both sites are
using NAT. This way they can communicate directly to each other because to
both networks it would appear seamless.

If you need more info on designing this, I would suggest to contact a vendor
such as Linksys, Cisco (PIX), Netgear, Sonic Wall, or Netscreen. Two of my
clients use Netscreen, they're easy to configure and it works nicely.

--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.
This posting is provided "AS-IS" with no warranties and confers no
rights.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory

HAM AND EGGS: A day's work for a chicken; A lifetime commitment for a
pig. --
=================================
 
Back
Top