I just installed a new SBS 2003 server (Dual Xeon 2.4 GHz and 4 GB RAM) and made it the gateway between the LAN and the outside world (public IP on the External Network NIC). The office consists of approximately 15 PCs. Obviously the SBS server is a DC, but the PCs all currently run XP Home, so none of them can join the domain. This will be corrected a few PCs at a time over the next 6 months or so, but cannot be corrected immediately. Since installing the SBS server and making it the sole DNS server on the desktops, internet connectivity has been incredibly slow. It takes forever for a page to begin to load. Once it finally started actually loading it seemed to load quickly. I finally tracked this down to being a DNS issue. On a client, if I do an "nslookup www.cnn.com
" for example, I comes back in about 2-3 seconds and says it lists the server as the DNS server that it checked with, but says it couldn't resolve the address. If I then wait another 3-4 seconds and try again, it still says the SBS server couldn't resolve it, but give a non-authoritative response with the IP of the CNN.com. So it seems that the holdup with websites loading up-front is that the browser is waiting on the IP to resolve. Other than re-running CEICW again, does anyone have any suggestion as to why it's taking the server so long to resolve external addresses? Thank you in advance for any advice or assistance.