Hello, I am trying to make plans to support automatic web proxy discovery in my small office network, since some of the client PCs are laptops that come and go. There will also be visiting laptops. I've been reading up on this. One strategy is to provide a web server with a virtual hostname of wpad.mydomain.tld, which the client web browser will seek out to download a proxy.pac file. For those who are as new to this as I am, WPAD stands for Web Proxy Automatic Discovery protocol. In another stategy, certain DHCP servers can provide instructions to aquire the proxy information to a client PC at the time the address lease is granted. I'm trying to figure out which if these is feasible with a SoHo-grade router controlling the LAN. The first choice above seems fairly straightforward, and it would be an easy matter to provide a webserver at wpad.mydomain.com. However it's been my experience that most routers in the mdoest price range will not loop-back to the LAN if a client PC attempts to route a hostname on mydomain.tld, necessitating the insertion of a special line in the /etc/hosts file of the client PC. So, that sounds like the wpad.mydomain.tld comcept is no solution for SoHo-grade routers because visiting laptops will never be able to route to a local web host, thus their browsers will fail to find the proxy instructions. Your comments are most welcome.