I have an active directory and exchange 2003 setup on my windows server 2003 standard box just fine. I can resolve my domain and all that goodness inside my network. Problem is, I also want to host my website on the internet for that domain on my box too. I can do it seperately by configuring IIS and the DNS properly, but when I have AD running, it keeps messing up my DNS settings. I'm behind a little wired linksys home router. I have port 53 and 80 forwarded to my server, and it works just fine without active directory on, but AD just messed up the WAN IPs I setup for the name server and host entries. It sets them back to my local network's class C IP automatically. I was wondering if there's a way I can have the hosts resolve as the WAN IP by default, or if I can assign one of the NIC ports to resolve to the WAN IP and the other to the LAN IP? Problem is, I don't want to share the internet connection through that server, simply just have it be used as a dedicated DNS/WEB/AD server so the rest of the network can function independently. My guess would be to setup DHCP on the box and have the clients pickup the DNS server as the primary DNS and the gateway as the secondary DNS? But I still have to figure out how to have the server send the proper resolved IP to the proper party requesting it. I hope that sounds understandable, I'm kinda muttering right now. Thank you! Edit: Another issue, even when I don't have AD installed and the DNS is done correctly, it takes a very long time for the IP to be resolved. I mean 20+ seconds here. Is there any reason why it's so slow? My server is a dual 1.7GHz Xeon w/ 768MB pc800 and a fresh install of server 2003, shouldn't be that slow.