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:
Interesting thought - I may just try this ~Umberto Nongeroson 9.Jan.03 08:47 AM a Web browser Domino Administrator 6.0All Platforms
But I can think of a couple of reasons why it might not work. DNSRBL is not a ping, it is a DNS look-up, probably using a gethostbyname type of call to the host stack.
Most DNSRBLs return 127.0.0.2 for listed hosts, but some return other values like 127.0.0.n where n varies depending upon the reason for the listing. Host not found in list is signified by a look-up failure.
The Domino DNSRBL function does not appear to distinguish between returned values, but does block on them. In other words, it doesn't seem to care if the result of a look-up is 127.0.0.2 or 1.2.3.4, only that the look-up gives a result. Now, it may be clever enough to know that if it sees a returned value of, say, 254.0.0.1 (via a line in the local hosts file) then that does not indicate a positive result, but then again, perhaps not.
Depending upon how the DNS look-up call is handed to the OS IP stack and how the OS IP stack is configured, the local hosts file may not be used anyway.
However, on the face of it, this appears to be worthy of a few tests to see if it can be persuaded to work. If it does, then well done, you have given us a sensible workaround pending a proper whitelist from Lotus.
And of course, if anyone from Lotus/IBM who is lurking here can say for sure that DNSRBL look-ups are always expected to return values in the range 127.0.0/24 then that would be a great help.
Return to top
. . . . . . . . . . Interesting thought - I may just tr... (~Kelly Zekwebur... 9.Jan.03) 
Print this page
