Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations TouchToneTommy on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

web domain name same as network domain name

Status
Not open for further replies.

davidwilson11

Technical User
Sep 4, 2003
89
GB
I ave just upgraded my domain to windows server 2003 and named the domain the same as my external web site domain for example. is the web site and google.co.uk is the internal domain name.

For this reason i cannot get access to the companies web page internally, are there any work arounds to this problem.
 
Work arounds:

1) change the domain name internally (hard solution)
2) Change the external domain name (sucks doing this...especailly if you are happy with your domain names name)
3) Modify DNS

The problem is that your internal DNS name space believes that it is responsible for your domain name. So, when you are inside your network and your try to resolve you web site, your internal DNS server say "yes, Im responisble for resolving records in this domain". However, the record probably doesn't exist in the local DNS database.

The mistake you made was naming your internal domain this: google.co.uk

You should have changed it up a bit like: google-int.co.uk

You can easily solve this problem by adding an "A" record called "WWW" in your local DNS database.

Associate the appropriate IP address with the "WWW" A record.

Then try to connect to the website.

-later

Joseph L. Poandl
MCSE 2003

If your company is in need of experts to examine technical problems/solutions, please check out (Sales@njcomputernetworks.com)
 
the real reason i named the internal address the same as the web address is because i wanted to use full web mail in the following manner.


for example.

the record that i have to add in to DNS is it the external website address?

thanks for your help.
 
thanks very much this helped a treat and now all users can access the companies website.

Thanks for that advice.

david wilson mcp
 
I'm glad it is now working...

By the way, I understand what you were trying to do with your exchange mail. However, you did implement this in a non-reccomended way.

Your internal domain name should not be the same name as your external internet domain name (for security reasons and other...for example, I (and people on the internet) now know the domain name of your internal network. With regards to security this is bad.)

You can still have your external name be while your internal domain = companyxyz-int.com or companyxyz.local

The way this works is that the ip address for "exchange" is listed in external Internet DNS. The A record for Exchange points to your public IP address (which then is NATed to your internal mail server.) That all that is needed...the resolution to your public IP.

Like, the internal domain name for Microsoft.com is not Microsoft.com, it is something different. The internal domain name for Target.com isn't target.com...

Just a point to remember for the future...there isn't much you can do about this now except for changing your internal domain name or changing your Internet domain name...

-later




Joseph L. Poandl
MCSE 2003

If your company is in need of experts to examine technical problems/solutions, please check out (Sales@njcomputernetworks.com)
 
The advice is taken on board, my senior IT engineer told me to set it up like this.

I can see what you mean though, it should not be set-up like this.

what if i am using http over RPC would this make any difference?
 
what if i am using http over RPC would this make any difference?" I'm not sure what you mean here? Can you explain?

As far as I know, it truely does not matter. I do not know of any companies that have the external Internet domain name that is the same as the internal. This goes against the most basic MS security recommendations.

You firewall/router has the job of converting IP's and protocols. So, I can't think of any situation where you would need these to be the same.

-later

Joseph L. Poandl
MCSE 2003

If your company is in need of experts to examine technical problems/solutions, please check out (Sales@njcomputernetworks.com)
 
okay okay i cant argue this point as i am rapidly losing.

thnaks and hope we chat in the future
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top