At work, we have a Network (W2K Advanced Server with SQL 7 + Exchange 2K Server)with a Domain named after our company and we are looking at becoming a small ASP. The problem is that the client we are offering a soloution to says that it is unacptable to have to log on to a nomain named after out company. Is there any way of changing the Network Domain Name without starting from scratch?
This conversation is currently closed to new comments.
There are several ways of doing this. This is how I defined a second domain name. 1) Pick an IP number from your IP range. 2) Set up a DNS server for your new domain with only the one IP number defined(you can have as many domain names as you like associated with an IP number or range.) 3) Register the new domain name.
This is just the outline, each of these steps could be divided into several sub-steps and also implies the prerequisites such as NIC-handles, secondary DNS servers etc. This is the method I found easiest when I set up an additional domain name here several years ago and it has worked without any hassles.
No problem, make you client register the domain name that he wants, and fill DNS records (upon services required) with the valid internet address asigned (no matter where the server resides, that is in his ip range or your's or any other provider)
If you're asking for technical help, please be sure to include all your system info, including operating system, model number, and any other specifics related to the problem. Also please exercise your best judgment when posting in the forums--revealing personal information such as your e-mail address, telephone number, and address is not recommended.
Changing Network Domain Name???
The problem is that the client we are offering a soloution to says that it is unacptable to have to log on to a nomain named after out company.
Is there any way of changing the Network Domain Name without starting from scratch?