Link to home
Start Free TrialLog in
Avatar of nostrasystems
nostrasystems

asked on

Have a dns issue

Hi Guys

I have a DNS issue i have a AD domin that was setup as mycompany.com so when the users try access their own home page mycompany.com they can not surf the page but works fine outside anyone any ideas on how to work around this?

Many thanks in advance
Avatar of darkmooink
darkmooink
Flag of United Kingdom of Great Britain and Northern Ireland image

is it hosted in your local network?
if so this is a common problem that i am unable to resolve but im sure that someone will be able to help
ASKER CERTIFIED SOLUTION
Avatar of Kieran_Burns
Kieran_Burns

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of nostrasystems
nostrasystems

ASKER

the server is hosted externally?
or if you don't have an internal dns server then you can make a sub domain that will point to the local ip and is only used for internal use because it wont work externally
sorry i ment to say the mycompany.com website is hosted externally
If you ping the address of the web server what IP address do you get?

I'm assuming it will be an internal address - in which case you do the opposite of what I originally suggested and manually add the EXTERNAL ip address of the web-site in the DNS forward lookup zone

Or have you created a web-site with the exact same name as the Internal domain name?
someone else did but i think they have created a ad domain with the exact same name as the external web domain
Avatar of Chris Dent

You're trying to access the external website on mydomain.com rather than www.mydomain.com?

It gets tricky because AD won't let go of mydomain.com if it's the name of the AD Domain. It's used for Group Policy distribution, joining the domain by using "mydomain.com", Distributed File System, etc, etc.

You can work around it as follows:

1. Ensure that the website responds on www.mydomain.com
2. On each of the Domain Controllers install IIS (if not already)
3. Make a Web Site on each DC and set it to Redirect to www.mydomain.com

It ain't pretty, but it would get around the issue while still allowing some access with just the domain name.

Chris
Because your domain is using the same FQDN as your internet domain you will need to manually manage any external DNS records internally. This is due to the fact that your DC's believe they are in charge of the FQDN.

So for a website at mycompany.com you need to open the DNS managment console, browse to your zone (mydomain.com) and create a new A record called "www", this should resolve the to external IP address of the website www.mydomain.com. Users will be able to now access that website, however they will require the use of the fully address "www.mydomain.com" for this to work.

Any other internet DNS records such a "mail.mydomain.com", "owa.mydomain.com" etc etc will have to manually added and maintained internally on your domains DNS servers.
The best solution I can think of is to rename the external Web site to www.mycompany.com because renaming the Domain would be a complete nightmare.

Sorry.
i fixed it, added an a host record on our internal dns server called www using the ip from an nslookup on mycompany.com from the outside

thanks guys
sorry raptorjb007 just the fix before u posted up but ur solution is correct too :)
Which was what I said second :-)

Glad to see it worked!
sorry Kieran_Burns so u did ur the winner :)