How to set DNS server in Win 2008 to be able to make subdomeins?

Hi experts!

I have a dedicated server with Win 2008 Server and IIS7.
I need to start 2 ASP net application on this server and as I understand I need to create 2 WEB sites and to start DNS Server so I to get something like http://pc.89.23.128.228 and http://sc.89.23.128.228 where 89.23.128.228 is my real IP.

 Can somebody send me link or write me what are steps which I should do ? This DNS server will be only to allow me to start more than 1 WEB site on this server, nothing more.

 Thanks
dvplayltdAsked:
Who is Participating?
 
Chris DentConnect With a Mentor PowerShell DeveloperCommented:

> so I to get something like http://pc.89.23.128.228  and http://sc.89.23.128.228 
> where 89.23.128.228 is my real IP.

You can't mix names and IPs, you need one or the other.

Typically that means creating:

pc.somedomain.com   Host (A)   89.23.128.228
sc.somedomain.com   Host (A)   89.23.128.228

Then those names would be used for the site Host Header in IIS.

> This DNS server will be only to allow me to start more than 1 WEB site
> on this server, nothing more.

This is where Host Headers come in, it allows you to run more than one website on a single IP Address / Port combination. Otherwise each site would need a unique IP address.

That makes the DNS part as follows:

1. Open the DNS console
2. Expand Forward Lookup Zones
3. Select your Forward Lookup Zone
4. Create new Host (A) records as described above

And the IIS part:

1. Open the IIS console
2. Select your web site
3. Select Edit Bindings...
4. Edit the existing entry
5. IP Address remains "All Unassigned"
6. Port remains 80
7. Host Header value should match the name added to DNS for each site

Each site can have more than one binding. That means you can give a site a number of different names if you wish. Your description only calls for one binding per site.

HTH

Chris
0
 
Mike ThomasConsultantCommented:
I'm not an IIS expert but I think you should be doing this with host headers.

So you would create 2 DNS records for example

Site1 pointing at 89.23.128.228
Site2 pointing at 89.23.128.228

IIS can then be set to direct to the correct website based on whether the browser has been directed to http://site1 or http://site2

But like I said this isn't my area really, but I hope that gives you some idea of what should be happening.
0
 
dvplayltdAuthor Commented:
I know this and I start to do it. but I see many many options and I need more detail info where exatly to click and to type.

Thanks.
0
SMB Security Just Got a Layer Stronger

WatchGuard acquires Percipient Networks to extend protection to the DNS layer, further increasing the value of Total Security Suite.  Learn more about what this means for you and how you can improve your security with WatchGuard today!

 
Chris DentPowerShell DeveloperCommented:

This might help a bit as well, a description of how to set Host Headers with screenshots:

http://www.dotnetscraps.com/dotnetscraps/post/Did-you-know-Add-host-header-to-a-Web-Site-in-IIS-7-IIS-75.aspx

Chris
0
 
Andres PeralesCommented:
Concur with above solutions...
0
 
dvplayltdAuthor Commented:
To Chris

I try, but do not have luck. Look pic,. and tell me, do you find somethink wrong? I think I follow you at 100 % .

AdsSchedulePro.com domein is working OK (it is main domein), but when I try
pc.AdsSchedulePro.com I get no luck (say me have not such address)

Let me ask. In this case, dedicated server with real Ip and domein redirect to this IP, with sure wrong setting is on my server, right ?

Thanks.
state.JPG
0
 
dvplayltdAuthor Commented:
To Chris

By the way … I make try and if I give different port to second WEB site all is working OK, only need:
http://www.adsschedulepro.com:8080/

(if I use port 8080 for second site)

Is this problem in real usage ? I think that both ports 80 and 8080 are standard open in routers ?
In fact I have a problem with work with http://www.adsschedulepro.com:8080/ of 1 part of part of my sute, however if I not found solution I will use this.


Thanks,
0
 
Andres PeralesCommented:
What is your default website set too?  It must be running with host headers as well, add set it to be www.adsschedulepro.com port 80, ip address all unassigned.
0
 
dvplayltdAuthor Commented:
To peralesa

I try, but after I put  www.adsschedulepro.com to defauilt WEB site it stop working . So problem is not this.
0
 
Chris DentPowerShell DeveloperCommented:

> I think that both ports 80 and 8080 are standard open in routers ?

8080 is not as a general rule, some systems may permit that port, but it doesn't have the standing of the regular HTTP port (80).

> pc.AdsSchedulePro.com I get no luck (say me have not such address)

That suggests DNS hasn't figured it out. Are you able to run "ping pc.AdsSchedulePro.com" or "nslookup pc.AdsSchedulePro.com"?

Is the IP address you're using assigned directly to the server (that is, do you see it when you run ipconfig)? Or are you use NAT (Network Address Translation) or PAT (Port Address Translation) to get the public IP to a private IP for your server?

Chris
0
 
dvplayltdAuthor Commented:
I get real IP (72.167.165.58)  directly to LAN netwrok of my server.


I have this warring in DNS Events. Does this mean that  I need to change somethink ?
I need to change name of compuyter to AdsSchedulePro.com to work DNS ???

I try to write in workgroup AdsSchedulePro.com but I can not, look that name is too long for workgroup ??? Then ???



The DNS server computer currently does not have a DNS domain name.  Its DNS name is a single-label host name with no domain (for example:  "host" rather than "host.microsoft.com").
 
You might have forgotten to configure a primary DNS domain for the server computer.
 
Because the DNS server has only a single-label name, all zones created will have default records (SOA and NS) created using only this single-label name for the server's host name.  This can lead to incorrect and failed referrals when clients and other DNS servers use these records to locate this server by name.
 
To correct this problem:
  1) Click Start, and then click Control Panel.
  2) Open System and Maintenance , and then open System.
  3) Click Change Settings, and then click Change.  4) Click either Domain or Workgroup, and then type the name of the domain or  workgroup you want the computer to join; the domain or workgroup name will be used as your DNS domain name.
  5) When prompted, restart the computer.
 
After the computer restarts, the DNS server will attempt to fix up default records, substituting the new DNS name of this server for the old single-label name.  However, you should review the zone's SOA and NS records to ensure that they now use the correct domain name of this server

 
0
 
Chris DentPowerShell DeveloperCommented:

> I get real IP (72.167.165.58)  directly to LAN netwrok of my server.

Okay, so IIS is potentially refusing to serve the page?

You should have some log files for your web sites here:

%SystemRoot%\System32\LogFiles

There will be a number of W3SVC folders, each corresponds to a website, we need to look at the new website and see if anything at all is being logged (to see if the site has had any visitors at all).

> I need to change name of compuyter to AdsSchedulePro.com to work DNS ???

No, definitely not.

> I try to write in workgroup AdsSchedulePro.com but I can not, look that name is
> too long for workgroup ??? Then ???

Workgroup names cannot contain dots, but that's fine, you don't need to modify that either.

> You might have forgotten to configure a primary DNS domain for the server computer.

Which means it's more work for you, but it is not critical, it won't cause IIS to misbehave.

Chris
0
 
dvplayltdAuthor Commented:
I have only 1 directory
MSFTPSVC1

and look that it is for default WEB Site.
We do not have any directory for this second WEB site. What this mean ?

:-(

I'm almost give up ...

WHere I can find in log of DNS that requiest for pc.adsschedulepro.com was accepted ?

I need to find with sure where is problem - in DNS, or in IIS7.

 I review Event Log and can not find nothing strange ...

0
 
Chris DentPowerShell DeveloperCommented:

If you can resolve the name to an IP address with nslookup / ping then the problem is with IIS 7. That should let you rule out DNS pretty quickly.

That means we just need to fix up the sites on IIS 7. You have two sites at the moment don't you? Default and the new one?

Chris
0
 
dvplayltdAuthor Commented:
Thanks for you time, I give up. DO not know why this is so hard .. it should be standard for IIS7 ?

I will need this in real after 2 months, I guest I will order second IP for second site. Then it will be with defauilt WEB site and I think will be OK.

Thanks again!
0
All Courses

From novice to tech pro — start learning today.