Improve company productivity with a Business Account.Sign Up

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 664
  • Last Modified:

SBS 2008, How to setup dns for a new domain name to use just mywebsite.com.

I am migrating from sbs2003 to sbs 2008.
AD, DNS, EXCHANGE and IIS is migrated and is functioning with no issues.
Why my company decided to muck with domains and webhosting during a sbs migration is one of life's most endearing msyteries, but I have to deal with it.

I've purchased a new domain name that is a secondary, seperate and distinct domain name from my AD.
I'd like sbs 2008 to host it.

The add new ip address wizard does not work for me because I did not purchase from the MS list of approved registrars.

I've searched EE and came close with this snippet from this ID: 21992046;
(same as parent folder) must be a Host(A) record with the IP Address if you want people to be able to get to mywebsite.com.

I can't figure out how to create a host(a) record with the ip address.

www.mywebsite.com works great, points to new domain name and iis is hosting it great.
mywebsite.com points to my default site which is not good.
I am looking to have mywebsite.com point to the same location as www.mywebsite.com

This is what I have in sbs2008 server manager DNS for my new zone; mywebsite.com.
(same as parent folder)              SOA                    servername.domain.local
(same as parent folder)              NS                       sbs2003 servername.domain.local
(same as parent folder)              NS                       sbs2008 servername.domain.local
webserver                                  host(a)                10.0.0.50
www                                          alias(cname)       webserver.mywebsite.com

Thank-you for your insight.
0
axsys1
Asked:
axsys1
  • 8
  • 3
1 Solution
 
axsys1Author Commented:
Hmmm, after further searching, maybe I'm not aproaching this right at all.  Maybe it's all about my iis7 host headers being messed up.  I'm going to google now.
0
 
axsys1Author Commented:
I was missing mywebsite.com from my iis bindings, but that did not resolve my issue, infact now mywebsite.com resolves to nothing.

From the server I can ping www.mywebsite.com and it resolves to my server ip.
ping website.com does not get resolved, so I am sure this is a DNS issue, and is proably still a missing host record issue?
0
 
Ken FayalCTOCommented:
Well, first you DO have to configure your DNS.  But from the looks of it, you are trying to host your OWN DNS with Windows, or are you hosting the Domain name (and DNS) through a registrar?

If that is the case, then yes, you simply create a new web site in IIS and create host header records for both the www.mywebsite.com and mywebsite.com.
0
Easily Design & Build Your Next Website

Squarespace’s all-in-one platform gives you everything you need to express yourself creatively online, whether it is with a domain, website, or online store. Get started with your free trial today, and when ready, take 10% off your first purchase with offer code 'EXPERTS'.

 
axsys1Author Commented:
Yes, I am using my server to host the DNS for this domain. My isp DNS records points to this DNS as the authoritive DNS server.


you know what, that was going to be my answer, but after thinking about it and doing a whois on my new domain, the nameservers on my whois points to my isp, not my server.  

Is it possible that I am beating a dead horse by making this poverly complicated?
0
 
axsys1Author Commented:
Bah, Im going home now.  My supper is ready.  I will deal with this in the morning.

Thanks for you efforts KaptainKenbo:

0
 
Ken FayalCTOCommented:
I would keep the ISP as the DNS hoster for your domain and configure a default host, and www host record there.  Then just configure a new web site in IIS and create the 2 host headers where one is www.mywebsite.com and the other is mywebsite.com.
0
 
axsys1Author Commented:
Would you believe that I came home and from outside the AD network, mywebsite.com points to the correct site as does www.mywebsite.com. It works a-ok from outside my domain.

So I remoted back into my server and some clients, and I still can't access mywebsite.com from any computer inside my domain.
Very weird.
I can live with it.  As long as the outside world can see everything ok, I can deal with internal stuff only if/when I have time.
I'm moving on with my migration.  Tomorrow I start dealing with software vendors.  Oh joy.

As to your point, I have verified that I have the two host headers binded to the site. I appreciate your fast responces.  Thanks!
0
 
axsys1Author Commented:
This answer pointed me in the direction that I needed to go at.
0
 
axsys1Author Commented:
Oh, I just had a thought.  If the ISP is my domain name's DNS server, and is redirecting to my www server, and my iis is configured to use host headers, then why do I need to have a dns entry in my AD?  What would be the consequence of removing said DNS entry?
0
 
Ken FayalCTOCommented:
I don't think there would be any adverse consequences.  Regarding your inside clients not being able to get to your web site.. do you have a cisco firewall by any chance?  If you do then it might be something as simply as setting up DNS doctoring on the firewall.
0
 
axsys1Author Commented:
I have removed my forword lookup zone entry for this domain, and everything works great, from inside the AD network, and the rest of the outside world.  

I do not have a cisco firewall, but I was making things overly complicated by trying to setup DNS when the ISP has already done so.

Thanks again!
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Building an Effective Phishing Protection Program

Join Director of Product Management Todd OBoyle on April 26th as he covers the key elements of a phishing protection program. Whether you’re an old hat at phishing education or considering starting a program -- we'll discuss critical components that should be in any program.

  • 8
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now