adamkerrigan
asked on
Using Active Directory DNS to redirect users visiting internal websites
Good Afternoon,
I've been told a best practice for internal users accessing the company website is to utilize Active Directory DNS, and setup records to point the users to the inside NIC on the webserver, rather than going through the firewall, then making a U-Turn and coming right back in through the firewall to the webserver.
I've played some and created Host (A) records in DNS for the domains, xyx.com, but the computer still goes to external IP address.
-adam.
I've been told a best practice for internal users accessing the company website is to utilize Active Directory DNS, and setup records to point the users to the inside NIC on the webserver, rather than going through the firewall, then making a U-Turn and coming right back in through the firewall to the webserver.
I've played some and created Host (A) records in DNS for the domains, xyx.com, but the computer still goes to external IP address.
-adam.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Guess you guys can type quicker than me!
ASKER
wow.....
:)
nice response!
-adam.
:)
nice response!
-adam.
hehe
It's just that time of night I think...
ASKER
I'm going to create New Forward Lookup's for
http://www.xyz.com and
http://xyz.com
so, no matter what my users type, they get to the website.
Thanks for the incredible response!
-adam.
http://www.xyz.com and
http://xyz.com
so, no matter what my users type, they get to the website.
Thanks for the incredible response!
-adam.
No worries, sorry for watering down the points split guys!
ASKER
Truly, I did bump the points from 333 to the maximum of 500...
For such a great response, you guys earned it!
-adam.
For such a great response, you guys earned it!
-adam.
Glad I could help out :)
Although you know you don't need both of those zones, one or the other is more applicable. If you're going to create xyz.com then you won't need a seperate zone for www.xyz.com, just the following:
Zone Name: xyz.com
Records:
"(same as parent folder)" Host(A) <WebServerIP>
www Host(A) <WebServerIP>
Which deals with both typed possibilities (xyz.com and www.xyz.com) in one zone as it should be.
Chris
ASKER
Awesome!
-adam.
-adam.