DNS designation

Netswitcher is the way to go.
I use it daily and have not had any real problems.
List price is $14.oo but if purchasing in bulk the price seems to come down quickly.
www.netswitcher.com

Not quite sure i understand the question.

DNS maps IP address to domain names'.

How many NIC's are on your server and are you using a router?
(I would recommend two using different Subnet Mask)
Do you have a Static IP address assigned from your ISP?
Are you connecting VIA BB, DSL or Modem.

Normally under TCP/IP properties on the NIC on PC's or laptops your DNS should be set to automatically obtain an address be it a PC or a laptop from the LAN server not your ISP.
your LAN clients should be obtaining their DNS from the LAN server.
Then in internet explorer on client pc's/laptops click Tools > Internet Options > Connetions > Lan settings and point your client laptops and pc's to your server name going through port 8080.

This means the server will act as a proxy dealing with the requests from client Pc's.

Your LAN DNS should be someting like 192.168.16.2 or another recommended non-rouatble address.

If you have two Nic's then point the external NIC to the DNS of your ISP and also Obtaining an IP address automatically from DHCP or inserting the ip address of the DHCP server with which your ISP have given you.

Ah, sorry. I meant that the local server's DHCP setup has my ISP's DNS addresses. What I meant was that, on workstations logging into the server I changed the network settings from the defaults to define my domain controller as the DNS server so the workstations would be "pointed" there. This begs the issue of what to do about laptop users who perhaps connect to other networks.

This may all be moot. I just ran across a potential configuration change in the client DNS configuration that may resolve the issue.