• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 521
  • Last Modified:

Domain name same as website name, so must use www. to reach external site internally

Since I started, this has been an issue-- our website  www.xx.com is the same as our domain name xx.com. Externally, we can go to xx.com and that puts you to our website, but if we are internal and someone types xx.com, they get the standard II7 page. Internal users must type www. to access our site. We do not host our site internally.

Is there some way we can fix this so that we aren't forced to type www. to access our web site internally?
0
sterlingrice
Asked:
sterlingrice
  • 5
  • 5
2 Solutions
 
matthewspearsCommented:
You need to add the zone xx.com in your Forward Lookup Zones within DNS, then add the appropriate DNS entries...
i.e. www     Host(A)     10.1.2.34
or
(same as parent folder)     Host (A)      10.1.2.34
0
 
sterlingriceAuthor Commented:
I checked and we actually do have that set up, but when I go to the IP address it has listed, it goes to a dummy page that says "coming soon please come back later"

If I ping our site, I get that same IP. I checked our hosting service and that is the same IP listed as well.
0
 
matthewspearsCommented:
Do you have the internal IP address bound to your website within IIS?  If not click on the website within IIS and on the right side open Site Bindings and add the specific internal IP.  You can try selecting "all Unassigned" but I've had mixed results.  Once you have entered the IP restart IIS and that should route your website properly.
0
What Security Threats Are We Predicting for 2018?

Cryptocurrency, IoT botnets, MFA, and more! Hackers are already planning their next big attacks for 2018. Learn what you might face, and how to defend against it with our 2018 security predictions.

 
sterlingriceAuthor Commented:
Well our site isn't hosted internally at all right now, so basically we would need to set up IIS on one of our servers and have it try to forward to our website that is being hosted?

If I ping xx.com, I see our DC's IP listed, but we wouldn't want to run IIS on there or anything.
0
 
matthewspearsCommented:
Ahh that's a different problem.  If the site works externally but not internally but is hosted on an external web server use nslookup to connect to an external DNS server and compare the DNS entries for your website to what your internal DNS is using and make updates accordingly.
0
 
matthewspearsCommented:
Ahh that's a different problem.  If the site works externally but not internally but is hosted on an external web server use nslookup to connect to an external DNS server and compare the DNS entries for your website to what your internal DNS is using and make updates accordingly.
0
 
sterlingriceAuthor Commented:
Do you think I would need to edit this on our local DNS server or would I need to do this in our ISP's a zone file?

I spoke with our web host for our site and they claim the IP I have is the corrent one. Locally when I type xx.com it just points to one of our Domain Controllers.
0
 
matthewspearsCommented:
You're on the right track.  But have you added an A record called "www" that points to the public IP of your website?  If not you need to, when you type xx.com you want it to point to your local DC.  If it pointed to anything else you would break all sorts of things, but when you type www.xx.com you want that to point to your website.

So create a DNS entry on your local DC that points www to the public IP and you should be right as rain.
0
 
sterlingriceAuthor Commented:
Ahh yeah that basically answers it for me then. Our domain is xx.com, but our site is www.xx.com (they share the same name, doh!). We were hoping that we'd be able to make it so xx.com actually pointed to our website instead of to one of our DCs, but if that is going to break anything we are just stuck with this situation.

Please correct me if I am misunderstanding what you said, basically whoever created our domain years ago sort of has us stuck in this situation unless we want to rename our domain, which won't be happening haha.
0
 
Chris DentPowerShell DeveloperCommented:

> but if that is going to break anything we are just stuck with this situation.

Unfortunately you're right, doing that will make your AD domain unhappy.

You could set up IIS on each of your DCs, and have that redirect HTTP requests for yourdomain.com to www.yourdomain.com, it's invisible to the end-user at least. It's a bit of a heavy burden if you have more than a couple of DCs, and a problem if there's opposition to the installation of web services on DCs.

Otherwise you're pretty much stuck in domain rename land.

Chris
0
 
sterlingriceAuthor Commented:
Thanks guys. Really appreciate the help. I really would prefer not to install IIS on our DCs, so our employees can deal with adding www. to our site.
0

Featured Post

A Cyber Security RX to Protect Your Organization

Join us on December 13th for a webinar to learn how medical providers can defend against malware with a cyber security "Rx" that supports a healthy technology adoption plan for every healthcare organization.

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