On 19.04.2006, at 16:53, Vlad Seryakov wrote:
On the other hand, on my servers i often use 0.0.0.0 as address, so
nsd listens on all registered interfaces. For me it sound more
logical then trying to determine what IP address i am resolving to,
if no specific then listen on all.
Something like:
[19/Apr/2006:17:28:43][681.2684415384][-main-] Notice: nssock:
listening on 0.0.0.0:8050
[19/Apr/2006:17:28:43][681.25186304][-driver-] Notice: starting
[19/Apr/2006:17:28:43][681.25186304][-driver-] Notice: driver:
accepting connections
?
Allright, I see, this could be the trick to bypass that reverse lookup.
I think I'm going to use that for the time being and see if this fixes
our blues.
Thanks for the tip.
Cheers
Zoran
