On 25.10.2001 14.51 Uhr, "ahall AT secureworks DOT net" <ahall AT secureworks 
DOT net>
wrote:

> Please disregard.  I figured it out.
> 
> Thanks anyways.
> 
> Drew
> ---------- Forwarded message ----------
> Date: Thu, 25 Oct 2001 15:39:29 -0400 (EDT)
> From: ahall AT secureworks DOT net
> To: amanda-users AT amanda DOT org
> Subject: ip not in list
> 
> Hello,
> 
> I have question that is probably really easy.
> 
> I am receiving the error (i have changed the hostname):
> 
> ERROR: hostname.net: [ip address 192.168.254.244 is not in
> the ip list for hostname.net]
> 
> The host in question has two ips that it round robins between.  This is
> necessary and can not change.  They are 192.168.254.244 and
> 192.168.253.244.  For some odd reason if the client received the .254.244
> ip as the servers ip it returns the above error.   Forward and reverse DNS
> for this IP work.  I have both ips in the /etc/hosts on the client, and
> the client is setup to check hosts then dns.
> 
> TIA.
> 
> 
> Andrew
> 
> 

I ran into the same problem.  I found out that the server (and perhaps the
client) need to have the forward and reverse Ips in DNS.  These particular
systems had entries in forward DNS, but since they are multi-homed hosts,
also needed all the IP addresses in reverse DNS.

I added both server and client entries into reverse DNS for all IP addresses
that were bound to the primary interfaces and voila - it's working.  I'm not
certain if this was the entries being added for the server or both.

I would suppose it would be prudent to add both the server and clients to
DNS.  I just thought I'd post this as a follow-up for everyone.

Hope this helps someone.
-- 
 
Kyle Allender