dynamic DNS

[Eran]

Hi,

Is it possible to implement dynamic DNS with Windows 2000 Server DNS?

Thanks,

Eran

 

[Herb Martin]

Hi,

Is it possible to implement dynamic DNS with Windows 2000 Server DNS?

Sure. It was released to support Win2000 AD which requires Dynamic DNS.

Both Unsecure and Secure-Only (with AD Integrated) Dynamic Updates are
possible on both Win2000 and Win2003.

 

[Eran]

Thanks for the reply.

Could you point me in the right direction?
My main server has a static IP and remote server with dynamic IP.
The remote server does not use AD.

Thanks,
Eran

Hi,

Is it possible to implement dynamic DNS with Windows 2000 Server DNS?

Sure. It was released to support Win2000 AD which requires Dynamic DNS.

Both Unsecure and Secure-Only (with AD Integrated) Dynamic Updates are
possible on both Win2000 and Win2003.

 

[Herb Martin]

Thanks for the reply.

Could you point me in the right direction?
My main server has a static IP and remote server with dynamic IP.
The remote server does not use AD.

First, it isn't safe to do this unless the DNS server is behind a firewall
and you can be reasonably sure that no one INTERNAL will abuse
the DNS server by registering false records -- I say this because you
don't have a domain and you mention a "remote" server.

Do you have DNS setup?
Open the DNS console.
Add you DNS server if it isn't there.
Find the Forward lookup zone for which your server is PRIMARY and
which you wish to make dynamic (You can only do this on the Primary
without AD.)
Right click on the zone->Properties-> General tab in the middle of the
tab.

For help, search the built-in help for [ DNS checklist ] or for
[ Dynamic DNS checklist ].

Ask a specific question if you need more help.

 

[Eran]

Hi Herb,

Thanks for the reply.

My main server does have a domain (say abc.com) with DNS Server functioning
and a public static IP.
AD is installed on the main server.

The remote server does not have AD installed, but I can enable the DNS
server/client services on it.
The remote server is in a different location and therefore not connected to
the same internal LAN.
Also, the remote server is behind a firewall and NAT (private ip). I don't
have problems opening ports for it.
Although the remote server's private IP is static, the router's public IP is
dynamic.

Can I use dynamic DNS so that "remote1.abc.com" will point to the remote
server?

Will dynamic DNS resolve the remote server's private IP to the router's
public IP?

I understand from your explanation how to set it up on the main server, but
what do I need to do on the remote server that is on a different network?

The TCP/IP settings on the remote server have the DNS IPs of their ISP. Do I
need to change this to the DNS ip of my main server?

Thanks,

Eran

Thanks for the reply.

Could you point me in the right direction?
My main server has a static IP and remote server with dynamic IP.
The remote server does not use AD.

First, it isn't safe to do this unless the DNS server is behind a firewall
and you can be reasonably sure that no one INTERNAL will abuse
the DNS server by registering false records -- I say this because you
don't have a domain and you mention a "remote" server.

Do you have DNS setup?
Open the DNS console.
Add you DNS server if it isn't there.
Find the Forward lookup zone for which your server is PRIMARY and
which you wish to make dynamic (You can only do this on the Primary
without AD.)
Right click on the zone->Properties-> General tab in the middle of the
tab.

For help, search the built-in help for [ DNS checklist ] or for
[ Dynamic DNS checklist ].

Ask a specific question if you need more help.

 

[Herb Martin]

Hi Herb,

Thanks for the reply.

I have been away from News mostly. Sorry for the delay.

My main server does have a domain (say abc.com) with DNS Server
functioning
and a public static IP. AD is installed on the main server.

[Simplify by just saying "my main server is a DC with DNS."]

The remote server does not have AD installed, but I can enable the DNS
server/client services on it.

Not a DC. Ok, so it will be a Secondary to the existing DNS server on the
DC.

The remote server is in a different location and therefore not connected
to
the same internal LAN.
Also, the remote server is behind a firewall and NAT (private ip). I don't
have problems opening ports for it.
Although the remote server's private IP is static, the router's public IP
is
dynamic.

That can be overcome -- e.g., if you need to build a VPN. You can use
dynamice DNS service on the Internet to give the router a stable "Name"
that will resolve to the correct IP when it changes.

Can I use dynamic DNS so that "remote1.abc.com" will point to the remote
server?

Not SAFELY with the Microsoft DNS probably. Use a public (e.g.,
dyndns.org or some such) dynamic DNS for that router. This way you
don't have to expose your dynamic Microsoft DNS server to the Internet.

Setup a VPN, route the remote office to the main office through that VPN
and keep everything encrypted in there.

Will dynamic DNS resolve the remote server's private IP to the router's
public IP?

It can.

I understand from your explanation how to set it up on the main server,
but
what do I need to do on the remote server that is on a different network?

You cannot safely setup a dynamic DNS server on a NON-DC, especially if
it is exposed to the Internet. You cannot have two Primaries unless they
are
both on DCs.

The TCP/IP settings on the remote server have the DNS IPs of their ISP. Do
I
need to change this to the DNS ip of my main server?

"Domain machines" and other "internal" (i.e., corporate) DNS clients cannot
reliably use an ISP on their NIC settings since they much resolve the DCs of
the
domain and other servers -- they must use STRICTLY the internal DNS servers
which know how to find the DCs and other resource servers.