This is an issue that I've now inherited... our domain, blahblah.edu, is now both our new website and our internal active directory domain. On the internal DNS, blahblah.edu is currently pointed to a domain controller. So, if I add the web server's IP to that entry, I'm afraid that it'll cause issues with the domain. Should it? Other than forcing the internal users to use www.blahblah.edu, instead of blahblah.edu is there any way to make the web site and the domain work properly? I was thinking that there may be some type of script to load on the domain controller that would allow me to forward anything accessing port 80, to another IP. That's probably just too easy to be true... Thanks in advance for any assistance..

Do you mean your internal DNS name is the same as your external DNS name? if so the problem you have with name resolution is because your internal domain is authoritative for that namespace. Thus when a query is made by clients to the DNS its stops there and wont send a query out to external DNS for name resolution. The only way around that is to create manual entries in your DNS that point to the external IP address`s of the said domain name.