My problem - I think - is not resolving a.razor2.cloudmark.com ... my problem is that the system does not even know the machine in your example is among the servers. I do not know anything (yet) about razor, but it appears to me that the <...>/servers.discovery.lst , or <...>/servers.nomination.lst do not exist, though the package was installed from an RPM, presumably designed to contain everything. I wonder if I should've used the tarball?!? Or - perhaps - create a list "by hand"?!? Hmmm ...
Actually that DNS lookup *IS* your problem... a.razor2.cloudmark.com is only used for DNS detection of the discovery servers, which is how razor bootstraps itself when it doesn't already have a working discovery server to talk to.
And of course, when razor runs it gets:
Finding Discovery Servers via DNS in the razor2.cloudmark.com zone Found 0 Discovery Servers via DNS in the razor2.cloudmark.com zone
If you run tcpdump while it does this, you should see it attempting to resolve a.razor2.cloudmark.com via DNS. For some reason, this is failing for razor.
Check your /etc/resolv.conf, make sure you don't have any bogus DNS server entries in it.. it's possible that razor only tries the first resolver in your resolv.conf, yet host works because it will try every resolver in the list.
------------------------------------------------------- SF.Net is sponsored by: Speed Start Your Linux Apps Now. Build and deploy apps & Web services for Linux with a free DVD software kit from IBM. Click Now! http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click _______________________________________________ Razor-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/razor-users
