GlimmerBlocker is no longer maintained and should no longer be used as web sites have migrated from using plain http to using https (i.e. encrypted) which prohibits modification by a proxy unless you resort to install custom SSL certiticates on the client.
You should use a browser extension instead.
It was made as a hobby project during 2007-2008 by Peter Speck. It features both a custom http server and http client and a Mac OS X control panel.
This is a feature for advanced users. The native Mac OS X dns resolver is normally used when looking up ip-addresses for an hostname, but you can specify the list of DNS servers that it should use instead of the native resolver, and the list can be URL-specific just like proxies.
It is important to understand all about GlimmerBlocker's support for proxies.
When GlimmerBlocker forwards the request to another proxy, it doesn't contact the server directly, and therefore doesn't resolve the hostname. It will be the remove proxy that resolves the hostname. The dynamic DNS resolution is only used when GlimmerBlocker contacts the web-server directly. So it either uses a remove proxy or resolves the hostname.
When GlimmerBlocker resolves hostnames itself, it sends requests to DNS servers using the dnsjava library, so the firewall must not block simple dns lookup UDP packets, or it will fail to resolve.
The DNS server is specified by assigning a comma/semicolon/whitespace separated list of ip numbers to the gb.network.dnsServers variable. Just like gb.network.proxy it is initially empty in the global script, and in request-specific scripts it is initialized to the global value.
If you want to use OpenDNS when using the University's wireless network, you can use a global proxy script like this:
if (gb.network.interfaces.en1.AirPort.ssid == 'The Great University') gb.network.dnsServers = "188.8.131.52 , 184.108.40.206";
If you want to use OpenDNS when resolving URLs for the university, no matter which AirPort network you are connected to, create a rule like this: