Website and Domain the same....

[Colin]

Went to look at a business today and one of their main complaints is that they can not access thier website from inside the office network.

After a little bit of snooping around I see that Server 2008 domain is set to the same web address, they tell me that site was hosted on the server but then got moved to google.

I think the domain is trying to send the internal network to the now non hosted site on the server and bringing up a 404 page. Am I correct? also what steps are needed to try and resolve this?

I have not dealt with this at all, and doing some research it might be best to redo the Server 2008 install with a new domain?

 

[cyabro]

You could add a cname DNS record for www and point that to the new IP address for the webhost.
You won't be able to fix the problem if they just type in the domain without the www though.

 

[Markverhyden]

Yep, it's a DNS issue. What are the server roles? Doing a nuke and pave is pretty drastic if they are running a domain with AD, etc.

 

[Colin]

They were looking at removing the older server but have no decieded to try and keep it.

I have added a cname to point to the IP address of the website but that currently does not work as the site is on a shared hosting?
Any other options that I may have?

 

[YeOldeStonecat]

I have not dealt with this at all, and doing some research it might be best to redo the Server 2008 install with a new domain?

It's quite common, simply go to DNSMGMT.MSC and drill down...create a dub dub dub record pointing to whatever the public DNS points to for the dub dub dub record. contact the web host if you need something further than just a single IP...find out what they want the record to point to.

 

[Colin]

okay so I setup the DNS forward to the IP address that the webhost has gave me but still nothing.
I have made sure I am typing w WWW and have the correct IP address, but when I open a cmd and ping the www.website.com I can see the correct IP but nothing is returned by ping just a "request time out"

Still scratching my head one this one

 

[PodnutzPro]

I would create a DNS zone called www.domainname.com with the IP address of the www record for the public DNS. This will force the users inside to use www.domainname.com, but it should work. When you ping www.domainname.com you should get the result back from the public IP. forwarders will not work in this case.

 

[drpcfix]

One trick I've used in the past, is do the cname bit (A records also work if you have a static IP for the website) and then find the server that the bare domain (without the www) is resolving to - install IIS there - and make a website that only redirects to www.domainname

so if they hit www.domainname.com it gets the external IP
if they hit domainname.com it hits the local server, which redirects to www.domainname.com - which goes to external IP