Cannot goto www.domain.com

[circulent]

Our network was setup so that the DNS suffix is domain.com, instead of domain.local.

The problem is that all requests to our web site at

http://www.domain.com

are blocked. Could the DNS suffix be a conflict? If so, how do we repair it without screwing up the whole network?

Thanks

 

[HalfaCracka]

Its been a while since I did this but I had the same issue. The domain.com suffix shouldnt cause a conflict. On your internal DNS server just make sure in your domain.com zone you have a record pointing to the address of web server. Then all internal requests will be translated to that address.

 

[mrdenny]

The problem with doing that is that all requests for the Active Directory network share will also be redirected. IE \\domain.com\shares\DFSlink\folder will be redirected to the external IP not the internal IP.

Check the MSKB there are Microsoft Tools out there which you can use to rename your domain. They aren't painless, but they can be done.

Denny
MCSA (2003) / MCDBA (SQL 2000)
MCTS (SQL 2005 / Microsoft Windows SharePoint Services 3.0: Configuration / Microsoft Office SharePoint Server 2007: Configuration)
MCITP Database Administrator (SQL 2005) / Database Developer (SQL 2005)

--Anything is possible. All it takes is a little research. (Me)

http://www.mrdenny.com

 

[Roadki11]

Add a hostA record in your local DNS with a host called

http://www and

the IP of your external host, it will work then.

RoadKi11

 

[circulent]

I tried adding an A record in DNS, but got this message:

Warming: The associated pointer (PTR) record cannot be created, probably because the referenced reverse lookup zone cannot be found.

Thoughts?

 

[Roadki11]

Thats pretty normal and just create the hostA record without creating the reverse PTR record you really shouldnt need it anyway. If you want the reverse PTR record you need to create a new reverse lookup zone for the IP of your web host. So... if your hostA record looks like this, host www, IP 66.34.23.12 then you need to create a reverse lookup zone for 66.34.23.x subnet. Make sense? you really dont need to do that though, just create the hostA record.

RoadKi11

 

[circulent]

If our web host is thru GoDaddy, and we have a shared site (meaning we don't have a static IP), should we just enter the FTP address as our IP?

Thoughts?