Bug#450711:

[Jos]

That makes sense, as you already must know, I'm not a linux guru. In the resolv.conf man, "If  no nameserver entries are present, the default is to use the name server on the  local  machine." according to other resources on the internet, resolv.conf is not even required if named is running. On localhost named is running, and a nslookup gives a correct result. The line in my resolv.conf does not make any sense, so I removed the resolv.conf. This didn't solved the error, so I created a resolv.conf with the line "nameserver 83.80.1.236" (the ip of  the ISP nameserver) Still the same error "can't initialize DKIM library" in syslog. I'm confused, is this a config problem? If so, why does I never had and have any other problems with ip/name resolving. Jos Mike Markley schreef: On Mon, Dec 17, 2007 at 12:31:12PM +0100, Jos <[EMAIL PROTECTED]> wrote: with bind9. the server has the name "kast". Ah. I'm afraid that's not how resolv.conf works. "search" simply specifies a list of domains under which to search for hosts. So, for example, if you attempted to look up a host simply called "foo", the resolver would try resolving just "foo", then "foo.kast". That keyword has no bearing on where lookups are performed. Your system still needs "nameserver" entries so it knows what name server(s) to actually query. Upstream has dug into the resolver functions a bit and confirmed that this behavior would occur on a system with no nameservers available. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]