Resource Records Vs Aliases
Kevin Darcy
kcd at daimlerchrysler.com
Tue Jun 12 21:33:09 UTC 2001
Smith, William E. (Bill), Jr. wrote:
> Here's the situation we have. We are currently in the midst of migrating to
> a Windows 2000 environment. Part of this migration is moving to multiple
> child sub domains for our various groups/departments. i.e. dept1.jhuapl.edu,
> dept2.jhuapl.edu, etc. Some departments have Windows 2000 servers running
> lab wide services that are currently registered in the root jhuapl.edu
> domain. Our dilemma is that when we migrate these servers to Windows 2000
> we want to move them into the departmental sub domain (e.g.
> server.dept1.jhuapl.edu.) This presents a problem in that all web pages
> with links to these hosts, user's bookmarks, etc. are pointing to
> host.jhuapl.edu and not host.subdomain.jhuapl.edu. The best solution
> obviously would be to update all web pages, bookmarks etc. to reference the
> server as host.subdomain.jhuapl.edu; however, that is a long term
> resolution/goal. In the meantime, we're trying to come up with a way such
> that these servers can be found via host.jhuapl.edu and
> host.subdomain.jhuapl.edu. One solution we see was creating one A record in
> say subdomain.jhuapl.edu and then creating an alias for that host such as
> host.jhuapl.edu. Another option we see is to create a separate A record for
> each domain, i.e. host.jhuapl.edu and host.subdomain.jhuapl.edu. Both seem
> to have some drawbacks. We're looking for some suggestions on how to best
> approach this issue. Thoughts and comments would be appreciated.
More information about the bind-users
mailing list