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

On Tuesday 29 August 2006 16:10, Chris Dennis wrote: > 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. > Ye

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

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 identif

Re: amcheck failure "did not resolve"

Chris Dennis wrote: Frank Smith wrote: Chris Dennis wrote: Hello Amanda People I can't find any reference on the web to this error message which started occurring a couple of days ago: WARNING: cherry2000: selfcheck request failed: cherry2000.mydomain.org.uk: did not resolve to cherry2000.

Re: amcheck failure "did not resolve"

Frank Smith wrote: Chris Dennis wrote: Hello Amanda People I can't find any reference on the web to this error message which started occurring a couple of days ago: WARNING: cherry2000: selfcheck request failed: cherry2000.mydomain.org.uk: did not resolve to cherry2000.mydomain.org.uk Runn

Re: amcheck failure "did not resolve"

Chris Dennis wrote: > Hello Amanda People > > I can't find any reference on the web to this error message which > started occurring a couple of days ago: > >WARNING: cherry2000: selfcheck request failed: > cherry2000.mydomain.org.uk: did not resolve to cherry2000.mydomain.org.uk > > Running

amcheck failure "did not resolve"

Hello Amanda People I can't find any reference on the web to this error message which started occurring a couple of days ago: WARNING: cherry2000: selfcheck request failed: cherry2000.mydomain.org.uk: did not resolve to cherry2000.mydomain.org.uk Running 'host cherry2000.mydomain.org.uk' give