Amanda-Users
[Top] [All Lists]
<prev [Date] next>
[Advanced]
 <prev [Thread] next>

Re: amcheck failure "did not resolve" - SOLVED!

2006-08-29 11:16:53
Subject: Re: amcheck failure "did not resolve" - SOLVED!
From: Chris Dennis <chris.dennis AT ndirect.co DOT uk>
To: Chris Dennis <chris.dennis AT ndirect.co DOT uk>, amanda-users AT amanda DOT org
Date: Tue, 29 Aug 2006 16:10:25 +0100 
Chris Dennis wrote:
I've changed my local DNS server so that 192.168.1.2 now resolves correctly to cherry2000.mydomain.org.uk, but amcheck is still giving the 'did not resolve' error. 

Has anyone else seen this?

cheers

Chris
Thanks to Jon who sent me a 'gethostbyname' program, I identified an issue with my /etc/hosts file. It contained 

        127.0.0.1       localhost       cherry2000.mydomain.org.uk
        192.168.1.2     cherry2000.mydomain.org.uk      cherry2000
which I now realise was wrong. Removing the cherry2000.mydomain.org.uk from the localhost fixed it. 

Moral of the story: get the simple things right first...

cheers

Chris
[More with this subject...]
<Prev in Thread] Current Thread [Next in Thread>
Previous by Date:  Hour long delay between each large DLE during dump, Root Jaz Singh
Next by Date:  Re: amcheck failure "did not resolve" - SOLVED!, David Golden
Previous by Thread:  Re: amcheck failure "did not resolve", Chris Dennis
Next by Thread:  Re: amcheck failure "did not resolve" - SOLVED!, David Golden
Indexes:  [Date] [Thread] [Top] [All Lists]