- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- different domains
Operating System - HP-UX
1820719
Members
2820
Online
109627
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Discussions
Forums
Discussions
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-25-2003 09:40 PM
10-25-2003 09:40 PM
different domains
Hello,
In our organization, years after years, came to life different domains and now it's very difficult to get rid of them because of legacy application. Now we have many servers with different domains, so sometimes it's a bit annoying trying to find out what is the domain of the server just to telnet it.
Ofcourse the big and hard working servers have the same domain (the new), but the old servers have so many domains ...
I wanted to ask, if someone have the same situation in his company and what solutions the found.
Thanx in advance!
In our organization, years after years, came to life different domains and now it's very difficult to get rid of them because of legacy application. Now we have many servers with different domains, so sometimes it's a bit annoying trying to find out what is the domain of the server just to telnet it.
Ofcourse the big and hard working servers have the same domain (the new), but the old servers have so many domains ...
I wanted to ask, if someone have the same situation in his company and what solutions the found.
Thanx in advance!
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-26-2003 10:17 AM
10-26-2003 10:17 AM
Re: different domains
We have sucessfully migrated internally from one domain to another domain. We used to use our external domain(juf.org) for internal servers. For reasons that never fully satisfied me we decided to become juf.net on the inside.
We also have a number of domains in house on the Winblows side. I don't think its a good idea to publish that structure, but the extra domains were to have test groups on the same network.
We're probably restructuring again because we have a class B network internally and thats a HUGE collision domain.
One of the problems with multiple domains is getting mail around the organization. This can be solved with an internal HP-UX mail server that services the various domains. That would be similar to a webhosting business(I own one) that handles the mail for multiple domains.
To get from our old very chaotic situtation to our current less chaotic situation involved the following steps:
1) We mapped out the current structure and identified every box that needed to change.
2) The person(s) responsible for the boxes that needed to change were told to present plans on how to do the transition. In my case that involved a few itrc searches and a software call.
3) All the plans were put together and test plans were drawn up to make sure important functionality survived the transition.
4) The test and implementation plans were completed over a few weekends. The plans had stopping points that provided functionality.
Did things go perfect? No. One morning I walked in and my HP-UX servers could not talk to any printers via openspool. I had to set up a small DNS server to maintain the current infrastructure. That DNS server survives to this day to provide compatability.
That issue was caused by someone deviating from the project plan and eliminating one of the old domains needed for compatability.
I don't know if this helps. If you identify specific issues, I can provide more specific advice.
SEP
We also have a number of domains in house on the Winblows side. I don't think its a good idea to publish that structure, but the extra domains were to have test groups on the same network.
We're probably restructuring again because we have a class B network internally and thats a HUGE collision domain.
One of the problems with multiple domains is getting mail around the organization. This can be solved with an internal HP-UX mail server that services the various domains. That would be similar to a webhosting business(I own one) that handles the mail for multiple domains.
To get from our old very chaotic situtation to our current less chaotic situation involved the following steps:
1) We mapped out the current structure and identified every box that needed to change.
2) The person(s) responsible for the boxes that needed to change were told to present plans on how to do the transition. In my case that involved a few itrc searches and a software call.
3) All the plans were put together and test plans were drawn up to make sure important functionality survived the transition.
4) The test and implementation plans were completed over a few weekends. The plans had stopping points that provided functionality.
Did things go perfect? No. One morning I walked in and my HP-UX servers could not talk to any printers via openspool. I had to set up a small DNS server to maintain the current infrastructure. That DNS server survives to this day to provide compatability.
That issue was caused by someone deviating from the project plan and eliminating one of the old domains needed for compatability.
I don't know if this helps. If you identify specific issues, I can provide more specific advice.
SEP
Steven E Protter
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Learn About
News and Events
Support
© Copyright 2025 Hewlett Packard Enterprise Development LP