Need Some Help Adding A Video Server

Hi.

I need some basic set-up help for adding a video server
to my network. I want the video server to live on it own sub
domain - such as video.domain.com .

Right now I have my folders under Inetpub as such:

C:/Inetpub :
- ftproot
- mailroot
- videoroot
- wwwroot

Both videoroot and mailroot will live at video.domain.com and
mail.domain.com respectively. Each subdomain will represent
its own computer (video and mail server).

My question is simply - how do I set up the sub domains on my network
(and get them to point to new addresses)?

Thank you.

"pbd22" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed) oups.com...
> Both videoroot and mailroot will live at video.domain.com and
> mail.domain.com respectively. Each subdomain will represent
> its own computer (video and mail server).
>
> My question is simply - how do I set up the sub domains on my network
> (and get them to point to new addresses)?

You don't.
They are not sub-domains. They are host names.

Create "A" Records (Host Records) in your AD/DNS server and point them to
the correct IP#s.

mail 192.168.35.45
video 192.168.35.46

If the IP#s are already registered in DNS to the *real* name of the machine
then use CNAME (Alias) Records instead and them point the Aliases to the
correct "real" A Record.

mail myserver.addomain.loc
video myserver.addomain.loc

In this second case there is typically only one IP# and Port# being used,
hence the same "myserver.addomain.loc" in both places. So you would use Host
Headers to distinguish one site from another. Host Headers are just simply
the full Host Name/Domain Name used in the URL

ex. "mail.myserver.loc" or "video.myserver.loc"


**NOTE**
All of this is only relevant on your local LAN. It has nothig to do with the
Public Internet or having people on the Internet get to your Servers

--
Phillip Windell
www.wandtv.com

The views expressed, are my own and not those of my employer, or Microsoft,
or anyone else associated with me, including my cats.
-----------------------------------------------------

On Sep 4, 9:33 am, "Phillip Windell" <philwind...@hotmail.com> wrote:
> "pbd22" <dush...@gmail.com> wrote in message
>
> news:(E-Mail Removed) oups.com...
>
> > Both videoroot and mailroot will live at video.domain.com and
> > mail.domain.com respectively. Each subdomain will represent
> > its own computer (video and mail server).
>
> > My question is simply - how do I set up the sub domains on my network
> > (and get them to point to new addresses)?
>
> You don't.
> They are not sub-domains. They are host names.
>
> Create "A" Records (Host Records) in your AD/DNS server and point them to
> the correct IP#s.
>
> mail 192.168.35.45
> video 192.168.35.46
>
> If the IP#s are already registered in DNS to the *real* name of the machine
> then use CNAME (Alias) Records instead and them point the Aliases to the
> correct "real" A Record.
>
> mail myserver.addomain.loc
> video myserver.addomain.loc
>
> In this second case there is typically only one IP# and Port# being used,
> hence the same "myserver.addomain.loc" in both places. So you would use Host
> Headers to distinguish one site from another. Host Headers are just simply
> the full Host Name/Domain Name used in the URL
>
> ex. "mail.myserver.loc" or "video.myserver.loc"
>
> **NOTE**
> All of this is only relevant on your local LAN. It has nothig to do with the
> Public Internet or having people on the Internet get to your Servers
>
> --
> Phillip Windellwww.wandtv.com
>
> The views expressed, are my own and not those of my employer, or Microsoft,
> or anyone else associated with me, including my cats.
> -----------------------------------------------------

Phillip -

Thanks for your clear response.
Would you mind elaborating on the last point, the "NOTE".
I am building with the intention of having Internet traffic
get to my video server.

Thanks again.

"pbd22" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed) ups.com...
>> **NOTE**
>> All of this is only relevant on your local LAN. It has nothig to do with
>> the
>> Public Internet or having people on the Internet get to your Servers

> Would you mind elaborating on the last point, the "NOTE".
> I am building with the intention of having Internet traffic
> get to my video server.

In that case you need to create a second Zone in your DNS that matches your
Public Domain. For example your AD Domain Name may be "MyLan.loc" and the
Public Domain might be "MyCompany.com". Your AD/DNS will already have one
for your "MyLan.loc" so you will only have to create the other zone. It
will be just a regular normal new Zone,..nothing special about that.

Then in that new public Zone you would add the records for your public
Hosts. These would be the same hosts names that your ISP has registered in
their DNS,..the only difference is that you would point them to either the
internal LAN IP#s or the internal AD Host Records that exist in your
original AD Zone,...while your ISP would be pointing the same name at the
public IP# that the internet user would be comming in at. In the event that
you have a machine that litterally does use a Public IP# then that DNS entry
would be the same in your new zone as it would be on the ISP's.

Any IP# will work in a Zone,..the Zone doesn't care,...the main focus of the
Zones are the hosts names. The Records only care about the host portion
(www, video, mail),...the rest of the name is always assumed to match the
Zone Name (MyCompany.com, MyLan.loc) So if the Zone is "MyCompany.com" and
the Record is "www" the machine is assumed to be www.MyCompany.com

The purpose of doing all this is because your internal LAN users are *not*
supposed to try to make a "U-turn" through the Firewall to get to a resource
that already physically sits on the LAN,..they are supposed to go directly
to the Resource itself.

Public User --> video.MyCompany.com = <the Public IP#>
LAN User-----> video.MyCompany.com = <LAN IP# or LAN Host>

This does mean that all machines on the LAN (*all*) are to use only your
AD/DNS for their DNS and *nothing* else. Your Ad/DNS would then have the
ISP's DNS listed in the Forwarders List in the Config of the DNS Service
itself. The Firewall would need to allow your Ad/DNS to make outbound DNS
queries to the ISP's DNS.

Then finally, you have the ability to run multiple websites from the same
IP# and Port# if you use host headers. So you have use only one LAN IP# on
the Web Server and only one Public IP# on the outside. The ISP would point
www, video, mail, ect to the same IP#. In your AD/DNS your would point the
www, video, mail, ect, in the New zone to the same Host Record in your AD
Zone (MyLan.loc). You would do this with CNAME (Alias) Records.

If the web server on the LAN was "myserver.mylan.loc" .....then

ISP's DNS:
www = <public IP>
video = <same public IP>

Your AD/DNS (MyLan.loc Zone)
myserver.mylan.loc = 192.168.14.65 (Host [A] Record entry)

Your AD/DNS (Mycompany.com Zone):
www = myserver.mylan.loc (a CNAME entry)
video = myserver.mylan.loc (a CNAME entry)

HostHeaders in IIS:
www.mycompany.com = site with "wwwroot"
video.mycompany.com = site with "videoroot"


--
Phillip Windell
www.wandtv.com

The views expressed, are my own and not those of my employer, or Microsoft,
or anyone else associated with me, including my cats.
-----------------------------------------------------

On Sep 4, 12:16 pm, "Phillip Windell" <philwind...@hotmail.com> wrote:
> "pbd22" <dush...@gmail.com> wrote in message
>
> news:(E-Mail Removed) ups.com...
>
> >> **NOTE**
> >> All of this is only relevant on your local LAN. It has nothig to do with
> >> the
> >> Public Internet or having people on the Internet get to your Servers
> > Would you mind elaborating on the last point, the "NOTE".
> > I am building with the intention of having Internet traffic
> > get to my video server.
>
> In that case you need to create a second Zone in your DNS that matches your
> Public Domain. For example your AD Domain Name may be "MyLan.loc" and the
> Public Domain might be "MyCompany.com". Your AD/DNS will already have one
> for your "MyLan.loc" so you will only have to create the other zone. It
> will be just a regular normal new Zone,..nothing special about that.
>
> Then in that new public Zone you would add the records for your public
> Hosts. These would be the same hosts names that your ISP has registered in
> their DNS,..the only difference is that you would point them to either the
> internal LAN IP#s or the internal AD Host Records that exist in your
> original AD Zone,...while your ISP would be pointing the same name at the
> public IP# that the internet user would be comming in at. In the event that
> you have a machine that litterally does use a Public IP# then that DNS entry
> would be the same in your new zone as it would be on the ISP's.
>
> Any IP# will work in a Zone,..the Zone doesn't care,...the main focus of the
> Zones are the hosts names. The Records only care about the host portion
> (www, video, mail),...the rest of the name is always assumed to match the
> Zone Name (MyCompany.com, MyLan.loc) So if the Zone is "MyCompany.com" and
> the Record is "www" the machine is assumed to bewww.MyCompany.com
>
> The purpose of doing all this is because your internal LAN users are *not*
> supposed to try to make a "U-turn" through the Firewall to get to a resource
> that already physically sits on the LAN,..they are supposed to go directly
> to the Resource itself.
>
> Public User --> video.MyCompany.com = <the Public IP#>
> LAN User-----> video.MyCompany.com = <LAN IP# or LAN Host>
>
> This does mean that all machines on the LAN (*all*) are to use only your
> AD/DNS for their DNS and *nothing* else. Your Ad/DNS would then have the
> ISP's DNS listed in the Forwarders List in the Config of the DNS Service
> itself. The Firewall would need to allow your Ad/DNS to make outbound DNS
> queries to the ISP's DNS.
>
> Then finally, you have the ability to run multiple websites from the same
> IP# and Port# if you use host headers. So you have use only one LAN IP# on
> the Web Server and only one Public IP# on the outside. The ISP would point
> www, video, mail, ect to the same IP#. In your AD/DNS your would point the
> www, video, mail, ect, in the New zone to the same Host Record in your AD
> Zone (MyLan.loc). You would do this with CNAME (Alias) Records.
>
> If the web server on the LAN was "myserver.mylan.loc" .....then
>
> ISP's DNS:
> www = <public IP>
> video = <same public IP>
>
> Your AD/DNS (MyLan.loc Zone)
> myserver.mylan.loc = 192.168.14.65 (Host [A] Record entry)
>
> Your AD/DNS (Mycompany.com Zone):
> www = myserver.mylan.loc (a CNAME entry)
> video = myserver.mylan.loc (a CNAME entry)
>
> HostHeaders in IIS:www.mycompany.com = site with "wwwroot"
> video.mycompany.com = site with "videoroot"
>
> --
> Phillip Windellwww.wandtv.com
>
> The views expressed, are my own and not those of my employer, or Microsoft,
> or anyone else associated with me, including my cats.
> -----------------------------------------------------

Hi Phillip.

Thank you again for the clarity.

The only thing that I am a bit unclear on is the distinction between
the .LOC and the .COM zones. It seems, when I check my AD/DNS server
that I have just one running zone - .COM. I set this one up
immediately after I installed the OS. If I do have the .LOC zone, I
have not called it as such and am really not quite sure what I am
looking for. But, having said that, the .COM zone is alive and well
and I was able to do what you suggested without much problems. My
video server hardware is enroute so, I won't be able to point to an
actual IP address on the network until it is set up. For now, when I
point to http://video.domain.com I get "Bad Request (Invalid
Hostname)" which I imagine is because there is nothing there? I "did"
create the header files as you suggested - video.domain.com and
mail.domain.com both answering as CNAME files for the "actual" servers
on the local LAN.

Of course, I'll have a better sense of things once the server shows
up.

Thanks again for your help.
Peter

PS - I privately sent you my DNSStuff stats

"pbd22" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed) ups.com...
> The only thing that I am a bit unclear on is the distinction between
> the .LOC and the .COM zones. It seems, when I check my AD/DNS server
> that I have just one running zone - .COM. I set this one up
> immediately after I installed the OS. If I do have the .LOC zone, I

That was only an example and I spelled it like that to make the distinction
clear. I almost always name my internal AD Domains with a "loc" on the end
( "loc" means "local") to make a clear distinction between the internal AD
Domain and the Public Domain that I might have registered on the Internet
with the ISP. For example I might make the Domain Names identical except
for the ending:

wandtv.loc (AD Domain)
wandtv.com (Public Domain)

The Zones in my AD/DNS machine would mirror that.

LAN Users --> www.wandtv.com = <local IP>, relies on AD/DNS
Public Users--> www.wandtv.com = <public IP>, relies on ISP

However some people use the exact same name in both. Some poeple like it
that way and it does work, I just don't personally like it. If your Domains
names are identical in both, then you just simply will have only one lookup
Zone in your DNS (which will already be there) and would just simply do
everything I mentioned before in the same Zone instead of two Zones,..the
"big picture" doesn't really change.

--
Phillip Windell
www.wandtv.com

The views expressed, are my own and not those of my employer, or Microsoft,
or anyone else associated with me, including my cats.
-----------------------------------------------------