POLICY REDIRECTION

Joseph S D Yao jsdy at cospo.osis.gov
Tue Dec 7 21:26:29 UTC 1999


On Fri, Dec 03, 1999 at 06:31:36PM +0800, fooler wrote:
>     thanks for the reply  but this policy redirection that im thinking of is
> not only applicable for proxy but other services as well. like for example,
> it will return the nearest www server, mail server, ftp server etc for
> having multiple network access point.
>     i saw one  which is cisco distributed redirector, but the problem is,
> its a proprietary protocol and requires cisco router to work with it. so in
> terms of scalability, it wont scale especialy if you have non-cisco router
> in your network access point.

One thing we were able to do for workstations that were NOT going to
roam, was to assign different sites domain1, domain2, domain3, etc.
Then one proxy might be relay.domain1, another might be relay.domain2,
and relay.domain3 might point back to one of the others if domain3 had
no proxy of its own.  The workstation had the domain for its site, and
its proxy name was just "relay".  ;-)  This will obviously not work
dynamically for workstations that are going to be plugged in randomly
around the network.

Barry Margolin <barmar at bbnplanet.com> once described something that they
do to present multiple sites.  I think they have multiple IP addresses
for (say) ns.domain.  Your resolver will find the closest one, and THAT
one will give out IP addresses for the closest proxy.domain, ftp.domain,
et al.

Of course, this whole setup takes additional overhead in terms of making
sure that each area's servers are all (a) up, and (b) synchronised with
the reference copies.

-- 
Joe Yao				jsdy at cospo.osis.gov - Joseph S. D. Yao
COSPO/OSIS Computer Support					EMT-B
-----------------------------------------------------------------------
This message is not an official statement of COSPO policies.


More information about the bind-users mailing list