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:
RE: Forgive my frustation, but... ~Yoshi Lopkichekflar 8.Jan.03 06:03 PM a Web browser Domino Administrator 6.0All Platforms
Your response is both well thought out and technically correct. Had you not warned me, this was specifically what I was about to do when a false positive is generated. What about the following scenario:
DNS Blacklists operate by either resolving or not resolving a named ping request. When the DNS Blacklist resolves a named ping with "unknown host," that indicates that the host is not blacklisted. If it resolves to 127.0.0.X (and therefore replies when pinged) it is blacklisted. You can add additional hosts to your personal blacklist by placing their IP address in your HOSTS file as d.c.b.a.relays.osirusoft.com where a.b.c.d is the IP address you wish to blacklist. Make the host resolve to 127.0.0.1. Of course, if you do not use relays.osirusoft.com, substitute for a different DNS Blacklist. Example below:
127.0.0.1 83.33.104.201.relays.osirusoft.com
Now if you wanted to whitelist an IP address, couldn't you put the same line in your HOSTS file, but have the name resolve to an unknown machine in your domain? For instance:
Whereas there is no machine in my domain with the hostname shinola. When I put this line in my HOSTS file and pinged 83.33.104.201.relays.osirusoft.com, I got "unknown host." Wouldn't this effectively whitelist the IP address? I know it seems sloppy, but it might work until Lotus implements a whitelist feature.
Return to top
. . . . . . . . RE: Forgive my frustation, but... (~Yoshi Lopkiche... 8.Jan.03) 
Print this page
