Hi all,
I have recently acquired dedicated server from the mighty Red Fox and I was looking to use it to host multiple ASP.NET websites on it using the single static IP address supplied.
I have been searching for a decent (and thorough) step-by-step example of DNS and multi-homing setup and, although found a few examples, cannot confidently say that they "hit the spot". They were either too vague at key points or miss configuration steps completely. I have some experience with setting up websites on a Windows 2000 Server with a dedicated IP address for each site, but most of the DNS work was out of my hands.
I am pretty sure that I am not the first person to attempt this type of setup
So, here is my story so far:
SERVER\ROLE INSTALL:
1. Acquired dedicated server with "Windows Server 2003 R1" pre-installed and configured using 1 static IP address. For the sake of simplicity, lets call it "1.2.3.4".
2. Installed IIS and ASP.NET 1.1 from the "manage servers" app.
3. Installed DNS from the "manage servers" app and used "forwarding". I noticed 1 warning in the DNS event log after installation stating my DNS may not work because my machine name did not contain a suffix (e.g. ".co.uk"). Does this matter? The machine name "RFHDSXX".
DNS CONFIG:
4. Added a zone with the name "www.domain1.co.uk" (I have already registered this with a 3rd party registrar - "Telivo" to be exact).
5. Added an "A" record to the zone with the name "www.domain1.co.uk".
6. Added a zone with the name "www.domain2.co.uk" (Again, I have already registered this with a 3rd party registrar - and again I used "Telivo").
7. Added an "A" record to the zone with the name "www.domain2.co.uk".
IIS CONFIG:
8. Added a website within IIS 6.0 and edited the host header name to "www.domain1.co.uk" in "advanced settings", leaving the IP address as "all unassigned" and the TCP port as "80".
9. Added a website within IIS 6.0 and edited the host header name to "www.domain2.co.uk" in "advanced settings", leaving the IP address as "all unassigned" and the TCP port as "80".
NAMESERVER CONFIG:
10. Changed the primary name server on my 3rd party registrar "Telivo" for both domain1.co.uk and domain2.co.uk to point at "1.2.3.4":
Telivo domain management
------------------------
nameserver1: ns1.redfoxhosting.com, IP address: 1.2.3.4
nameserver2: ns2.telivo.com, IP address: (I forget telivos address)
I left the 2nd "backup" nameserver to point to Telivo's own nameserver for the sake of simplicity at this point.
I am sure that my setup is not correct! I have a feeling that I need to change the nameserver1 setting of "ns1.redfoxhosting.com" to point to my dedicated server directly.
My questions, after reading several conflicting articles on DNS, are:
1. Do I need to configure my dedicated server as the nameserver, so that I can point the "nameserver1" value of "www.domain1.com" on Telivo to it? If so, how whereabouts\how do I configure my dedicated server to do so?
2. Do I need to add a suffix to server name to make it visible (e.g. "RFHDSXX.co.uk")?
3. Do I need to change my "DNS server address" settings in my "Internet Protocol properties" within "local area connection properties"? I believe they
currently point to a Red Fox DNS.
Please feel free to ask any questions and apologies for my numpty ones!



!
Reply With Quote
Bookmarks