|
Re: Strange DNS lookup problems ... I think ...
2004-03-06 10:27:44
Resolving IP address to a hostname (reverse lookup) is the part that
looks broken, check the reverse domain in the DNS i.e.
host 172.24.16.86
or
nslookup 172.24.16.86
The error says *hostname* lookup failed, not "address lookup failed."
Someone else reported a similar problem a few days ago, and he reported
that there was a typo in the reverse domain file of the DNS, and that
fixing that fixed the problem.
I wonder though, Why does amanda need to do a reverse lookup? You give
amanda a hostname in the DLE, and it looks up the IP address, which
should be adequate for amanda to do what it needs to do. But then it
tries to do a reverse lookup for the hostname based on the IP address,
and gives up if that fails.
It would be nice if the reverse lookup could be avoided. In principle,
yes, the reverse table in your DNS should be correct, but failing backup
seems like an expensive DNS diagnostic.
planner: ERROR intrap: [addr 172.24.16.86: hostname lookup failed]
--jonathan
|
|
|
