For each primary zone, you'd have various DNS records like
[auroranet.nt.ca]
auroranet.nt.ca A 123.123.123.2
www CNAME auroranet.nt.ca
[somename](subdomain)
somename A 123.123.123.5
www CNAME somename.auroranet.nt.ca
[something.com]
something.com A 123.123.123.3
www CNAME something.com
[somethingelse.com]
somethingelse.com A 123.123.123.4
www CNAME somethingelse.com
You'd have to add NS, MX and any other CNAMEs or A records to each primary
zone as needed. Do not add an NS record for a subdomain
(somename.auroranet.nt.ca)--the toplevel domain is already handling that
with its NS record.
Josh Hillman
hillman@talstar.com
> From: Franco Nogarin <webmaster@auroranet.nt.ca>
> Hi all, I have been getting a lot of requests from customers for virtual
> hosting, I am running IIS 4.0 on NT 4.0 and am wondering if I have my
ideas
> are strait, I figured this is how it goes:
>
> 1- we are www.xyz.com and our class c is 123.456.789.0
> 2- our customer has their own domain name of ourcustomer.com
> 3- so I would assign an additional IP to my NIC in my webserver of
> 123.456.789.169 (Previously unused)
> 4- then I would open my DNS and add a subdomain of ourcustomer.com to
> xyz.com
> 5- add an a record of www for 123.456.789.169 in the ourcustomer.com
> subdomain
> 6- create a virtual server in IIS and bind it to IP 123.456.789.169
> and thats it?