Re: Production Web Server Setup On Another Server
- From: Joe <joe@xxxxxxxxxxxxxx>
- Date: Tue, 16 Oct 2007 11:55:32 +0100
Ron Brown wrote:
Hi Claus,OK, you can't have two hosts on the same domain, both named www. What you describe will need the www A record (and the main domain.com record, which has become customarily an alternative to www.domain.com) to point to your new web server's public IP address, and you will need an A record with some other name to point to the SBS public address. If you have two separate IP addresses, you must have at least two distinct hostnames.
That was a massive typo. I have learned over the past year that a web site should not
be setup on an SBS, so the answer is no...no website is there.
To answer you second question, it is a public IP address.
On GoDaddy, I created an A record (www) that pointed to the new public IP address
on the Windows 2003 server, but that broke my OWA access in exchange, so I have changed
it back an everything is back working correctly.
After a little rest, this is my overall goal.
I want our domain name to point to a separate server that will be created using a different IP (public)
address. What needs to be installed and configured on the second server? I am sure IIS and DNS will
be required. But when a public user types in our domain, what changes needs to occur at GoDaddy to make
this happen and any other changes need on and if any on the SBS box?
If you already host email on the SBS, then you may already have an A record for mail.domain.com or similar, which will do, or you can create another such as sbs.domain.com. Whatever it is, it becomes the new hostname for OWA and RWW access.
If you do host mail, and you already have an MX record pointing to a mail.domain.com A record which points to the SBS public IP address, that won't need to change. If you host mail and don't already have both of those records, you will need to create them when you change domain.com, which is the default mail server.
If you have the necessary DNS control, set the TTL (time to live) of the records you need to change to something very short, and do it at least the old TTL value in seconds before you make the change. That way, all the DNS caches which may have held the old values will have to discard them before the change happens. Set the TTLs back after making the change. Not a problem for the web server, but important if you do need to change the mail-related records.
As far as DNS for the new server goes, you really don't want to get into hosting a public name server, and organising a geographically separate backup server, for one server computer. The new server can use a public DNS server for its own needs, or even its own router as a caching server, as it doesn't have to know anything about the SBS domain.
.
- Follow-Ups:
- Re: Production Web Server Setup On Another Server
- From: Ron Brown
- Re: Production Web Server Setup On Another Server
- References:
- Re: Production Web Server Setup On Another Server
- From: Claus
- Re: Production Web Server Setup On Another Server
- From: Ron Brown
- Re: Production Web Server Setup On Another Server
- Prev by Date: RE: Exchange Server
- Next by Date: RE: HTTP/1.1 503 Service Unavailable
- Previous by thread: Re: Production Web Server Setup On Another Server
- Next by thread: Re: Production Web Server Setup On Another Server
- Index(es):
Relevant Pages
|
