Restrict client web access by network port?
I currently ask that the users turn on/off AirPort (highest priority network) to change to the ethernet network, but they obviously forget 😉
I do not have total control over the networks themselves, but it occurred to me that I may be able to use a local Mac OS X 10.6.5 server as a DNS server that could be used in the ethernet configuration on the client machines; and perhaps THAT could redirect traffic to any other domains to an error page.
I only want the clients (while connected to the ethernet network) to be able to visit "http://approved-domain.com" or any of the various "http://*.approved-domain.com sub-domains that exist.
Again, I know it would be easier with control of the network/router itself, but I don't and am hoping for a workable solution without it.
A whitelist through a DNS server seemed like a good idea. Is it possible? How might I set it up?
Mac OS X (10.6.5)