Dynamic DNS on Intranet

[Jamie]

We have a central DNS server setup and running. When a system does a
lookup for host.company.com it replies back with the proper IP address
(ie 192.168.3.1)

What I would like to do is setup the DNS server so that when a query is
made to host.company.com, the IP address that is reported back is
dynamic based on the person's IP.

We have some WAN links that we would like to have the host name resolve
to that LAN segment, to reduce loads.

For instance, if we have three sites:

Atlanta - 192.168.1.0 255.255.255.0
Dallas - 192.168.2.0 255.255.255.0
Toronto - 192.168.3.0 255.255.255.0

When a query is made to host.comapny.com, depending on the person's
location, the IP address would would be different for each LAN segment.
If a specific IP range is not specified, then a default IP should be
used, like so:

Atlanta - host.company.com = 192.168.1.1
Dallas - host.company.com = 192.168.2.1
All Other offices - host.company.com = 192.168.3.1


This way we can setup an NAS device in three sites and our applications
point to this single host name.

I'd prefer not to setup DNS servers in all the remote sites.
Can this be done?

 

[Ace Fekay [MVP]]

In

We have a central DNS server setup and running. When a system does a
lookup for host.company.com it replies back with the proper IP address
(ie 192.168.3.1)

What I would like to do is setup the DNS server so that when a query
is made to host.company.com, the IP address that is reported back is
dynamic based on the person's IP.

We have some WAN links that we would like to have the host name
resolve to that LAN segment, to reduce loads.

For instance, if we have three sites:

Atlanta - 192.168.1.0 255.255.255.0
Dallas - 192.168.2.0 255.255.255.0
Toronto - 192.168.3.0 255.255.255.0

When a query is made to host.comapny.com, depending on the person's
location, the IP address would would be different for each LAN
segment. If a specific IP range is not specified, then a default IP
should be used, like so:

Atlanta - host.company.com = 192.168.1.1
Dallas - host.company.com = 192.168.2.1
All Other offices - host.company.com = 192.168.3.1


This way we can setup an NAS device in three sites and our
applications point to this single host name.

I'd prefer not to setup DNS servers in all the remote sites.
Can this be done?

Have you tried this and found it didn't work?

You will need to disable Round Robin in order to make this work. Make sure
netmask ordering is enabled. This is for all DNS servers hosting this zone.

The way it works by default is if you create three records for "host" under
domain.com, and the 3 IPs are of different subnets, the DNS server should
respond with an IP closest to the subnet of the querying host. This is
called netmask ordering as is enabled by default.

If you want this only on one DNS server in the central location, you can do
this as well, but if you ask me, its alot of querying traffic across the WAN
link. Ideally, its recommended to have a DNS server at each location. If all
the DNS servers are DCs, why not make the zone AD Integrated and host one at
each location to make this scenario more efficient?


--
Regards,
Ace

Please direct all replies ONLY to the Microsoft public newsgroups
so all can benefit.

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 Windows MVP - Windows Server - Directory Services

Security Is Like An Onion, It Has Layers
HAM AND EGGS: A day's work for a chicken;
A lifetime commitment for a pig.

 

[Jamie]

Ace, that worked. Didn't even think to just "try" it.

Thanks!

 

[Ace Fekay [MVP]]

In

Ace, that worked. Didn't even think to just "try" it.

Thanks!

See, you never know unless you try!

Ace