On Thu, 9 May 2002, Matthew Daubenspeck wrote:
> On Thu, May 09, 2002 at 01:50:36PM -0400, Dave C. wrote:
[..]
> > >
> > > The backup then tries to contact the main server and fails, then
> > > contacts the backup (itself) and delivers the message. Then the new
> >
> > Thats your problem. The backup isnt recognizing that it should just hold
> > on to the message if it cant contact the primary server. How are the MX
> > records set up, do they point at the primary hostname of the servers,
> > so that the backup server can recognize its own address?
>
> ordeal:/home/mellofone# dig oddprocess.org MX
[..]
> oddprocess.org. 5202 IN MX 0 oddprocess.org.
> oddprocess.org. 5202 IN MX 5 daubnet.dns2go.com.
>
> The main server is oddprocess.org, and the backup is
> daubnet.dns2go.com.
>
> The backup server /etc/hosts has
> 192.168.0.4 daubnet.dns2go.com
Here is what I get for that name. I think that has something to do
with your problem. (Im fairly certain exim queries the DNS directly and
ignores /etc/hosts)
daubnet.dns2go.com. 6 IN A 151.201.155.118
>
> So it should know its own addresss..
>
--
