Local domain and website using same name, how do i get local users to my site?

[adamck]

Hi Guys.
So... i have a domain that is the same as the website that i have.
I created an A record called WWW which i pointed to the IP of my server (dedicated).
This now means when im on the network as a domain user and i type in www.xxxxxxx.com i now get the 'Default Website Page' from the dedicated server.
Not the website on the server that i wanted.
How do i set this up so that the www will go to correct website on my server, not the root?

The website works fine outside of the network.

Thanks
Adam.

[ArielP]

By 'domain', do you mean an Active Directory Domain Services domain?

[adamck]

By 'domain', do you mean an Active Directory Domain Services domain?

Yes I mean a network domain.

Our network is plxxxxxxxxx.co.uk which points to an internal IP.
When a user types in http://www.plxxxxxxxxx.co.uk we want it to go to the website.
If I add an A record with my web servers IP (at surpass) it shows the default web page.
I want it to go to the website for plxxxxxxxxx.co.uk not the default server homepage.
So if its not an A record I need, what is it?
I tried delegation in windows server DNS in our domain and it didn't work either.

The website http://www.plxxxxxxxxx.co.uk works fine from everywhere else on the web.

[ArielP]

This is the reason why people will usually name their AD domains along the lines of "domain.tld.local", otherwise the combination of local and remote names can get confusing very fast...

You need to set an A record within the AD-controlled DNS server that points www.(domain) to the dedicated server's IP address, as IIRC, AD will not query remote DNS servers for what AD considers its own data.

[adamck]

This is the reason why people will usually name their AD domains along the lines of "domain.tld.local", otherwise the combination of local and remote names can get confusing very fast...

You need to set an A record within the AD-controlled DNS server that points www.(domain) to the dedicated server's IP address, as IIRC, AD will not query remote DNS servers for what AD considers its own data.

I've already created a 'www' A record that points to the dedicated servers IP address.
Hen I visit www.plxxxxxxxxx.co.uk it takes me to the dedicated server, but only the 'default web page' page. Not the correct website within the dedicated server.

If you try to visit my dedicated server via IP you would have to go to xx.xx.xx.xx/~someaccount in order to get the actual website.
As I can only enter an numerical IP address into the A record I can only point to the default server IP, not the account I want!

[ArielP]

Do you have a VirtualHost set up on the dedicated server to handle requests for that domain name?
If you do, you will need to configure your AD DNS to point the A record to the IP address that the VirtualHost is configured to use.
If you don't, you need to create one (usually, a VirtualHost is created to a specific IP address and a domain name, with a ServerAlias of www.(domain))