Strange WWW behaviour on Connect Server.

Hi

I have a strange issue on an Adobe Connect server. The site has just one server which is running Windows 2008 R2 Std. The server has Active Directory, DHCP, and DNS servers installed. It also has Adobe Connect 9. When it was setup the server was assigned the same DNS suffix as the organisation’s public domain name – e.g. company.org. The Connect server settings are configured for the URL ‘connect.company.org’. Internal DNS settings have an ‘A’ record pointing to the server’s internal IP address and similar external DNS points to the external IP. This all works fine.

The organisation has a website which is hosted off-site by an ISP. The external DNS has a record pointing ‘www.company.org’ to this host which works fine. The internal DNS also has an ‘A’ record pointing ‘www.company.org’ to the ISP, however when a user inside the network browses to ‘www.company.org’ the page returned is the login screen of the Adobe Connect server. If I use nslookup or ping the URL ‘www.company.org’ from inside it returns the IP of the ISP web host so the internal DNS seems to be working correctly. It is like the Connect server is somehow hijacking internal calls to ’www’. I have tried setting up an identical DNS record but for ‘www1.company.org’ and this browses fine to the correct web site. The issue is just with ‘www’. 

I know that one solution would probably be to change the internal DNS suffix to something different – like company.local however I am reluctant to do this as it will impact to other functions such as Active Directory. I would rather just that Connect behaved itself and left calls to www alone!

Does anyone have any ideas?

Thanks, Mark.