This forum is closed to new posts and
responses. Individual names altered for privacy purposes. The information contained in this website is provided for informational purposes only and should not be construed as a forum for customer support requests. Any customer support requests should be directed to the official HCL customer support channels below:
Back to the drawing board ~Umberto Nongeroson 9.Jan.03 01:34 PM a Web browser Domino Administrator 6.0All Platforms
I tried to "whitelist" a test host that ordb.org lists and then ran the ordb test. This test was successfully blocked (obviously, I wanted the test to fail due to my "whitelist").
If you create an entry in your hosts. file that looks like:
127.0.0.1 1.0.168.192.relays.ordb.org
where 1.0.168.192.relays.ordb.org is a valid ordb.org listing for a host 192.168.0.1, then ping 1.0.168.192.relays.ordb.org, you will see responses from 127.0.0.1. But do an OS nslookup like so:
nslookup 1.0.168.192.relays.ordb.org
and you don't get 127.0.0.1, because the nslookup doesn't check the hosts. file, it just goes straight to the DNS as I suspected it would.
If we want to have the desired effect, what we need to be able to do is prevent RBL style DNS look-ups of "whitelisted" hosts from resolving in the OS.
Windows DNS is not sufficiently open to permit this kind of tinkering. I am willing to bet that it could be accomplished relatively easily on a Linux box as you have all of the source code for name server look-ups right there to play about with. That is well beyond my programming capabilities though, so this is where I stop for now.
Return to top
. . . . . . . . . . . . Back to the drawing board (~Kelly Zekwebur... 9.Jan.03) 
Print this page
