Link to home
Start Free TrialLog in
Avatar of scoobyftl
scoobyftl

asked on

Adding www redirect to Active Directory

Client has 3 domains in AD DNS.  The www A record has the static IP of the external site.  They just made a change and were given a new IP.   It looks like externally the .com and .net redirect to the .org which has the new IP.  Internally, made the change to .org and is resolving correctly.  However, the .com and .net left as before and with new IP fail to resolve.  

I checked for any static routes with route print but there are not persistent routes.

really not sure how this is working.  
Thanks
Avatar of Jeremy Weisinger
Jeremy Weisinger

I'm not sure what you're asking. Could you explain your setup with a little more detail, give example DNS names and IP addresses?
Avatar of scoobyftl

ASKER

It was set up by someone else and part of the problem.  They have 3 domains in DNS that match their external registered domains.  

INTERNAL
domain.com is the primary internal domain.
domain.org and domain.net are the other two.

External
domain.org main website
domain.com and domain.net redirect to domain.org (at registrar redirects to correct network solutions IP)

Internal DNS

There were www A records for the previous network solutions IP address listed under domain.com, domain.org and domain.net.  The change was made to match the previous set up.  

However, after flushing DNS only domain.org goes out to the website while the other two fail to redirect.  I've checked IIS for a redirection but don't see anything there.

If you ping outside the domain .com and .net resolve to a different ip than the .org. I tried using that IP address to force redirection once outside but that failed to work.

Hope this explanation helps.
Just so I have this straight, your external setup is:

www.domain.org -> 1.1.1.1
www.domain.net -> 2.2.2.2 which the registrar redirects to domain.org
www.domain.com -> 2.2.2.2 which the registrar redirects to domain.org

And internally your setup is:
www.domain.org -> 1.1.1.1
www.domain.net -> 1.1.1.1
www.domain.com -> 1.1.1.1

Is the above correct? Is the website located internally?
It is correct.
No the website is external.

Previously www.domain.com, www.domain.org and www.domain.net were set internally to 1.1.1.1 which is why they configured www A record same way again.  When it wasn't working i tried setting internal DNS so that www.domain.org ->1.1.1.1
                                 www.domain.com ->2.2.2.2 (so that it then redirects to 1.1.1.1)
                                 www.domain.net -> 2.2.2.2
however that didn't work.
What are the results when you try to ping the different domains? Do you get the expected IP address? When internal are you using the "www.domain.com" address as opposed to just "domain.com"?

yes when i ping internally to www.domain.com or .org or .net i get the external IP address of network solutions as set in DNS.

When i ping from outside i get a different IP for .com and .net. which is the IP that then gets redirected to the network solutions IP.   That is what i can't figure out internally.  how to get that redirection.  I tried entering the IP that shows up when i ping from outside but that failed to work.
ASKER CERTIFIED SOLUTION
Avatar of Jeremy Weisinger
Jeremy Weisinger

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
Thanks for the feedback.  Will see if i can get that set up.
Just to be clear.  

Add a new web site (default being used) with description of domain.com, point to dummy directory and choose an open internal static IP assigned to this IIS server.  Then in Home directory tab i set to redirect to www.domain.com

Internal DNS i change www A record IP to one assigned to the IIS site.

Anything else i would need to do?

Yes that should work.

I assume that you meant www.domain.org as what you're redirecting to. And in DNS only point the .net and .com domains to the internal IIS server.
Actually, typing http://1.1.1.1 takes me to the same network solutions construction page we're getting when typing www.domain.com or www.domain.org.

http://1.1.1.1 from an outside location results in same thing.

when you ping http://www.domain.org you also get IP 1.1.1.1 which doesn't quite make sense.  The IP address from outside should also direct you to the website.
sorry yes www.domain.org
What's happening is the website is using host header values. Basically if the proper host isn't in the header it doesn't return the website you're looking for. This is how they can have multiple websites running on the same server and same IP address. With the IIS website redirecting to the proper url it should eliminate this problem because it points the user to www.domain.org. DNS can't make this translation which is why we have to setup this kludge.
worked perfectly.