Dear Sam,
maybe we're missing the point or I see a problem where no problem is:
auth.smtp.kundenserver.de is a CNAME for mrelayng.kundenserver.de
auth.smtp.kundenserver.de canonical name = mrelayng.kundenserver.de
mrelayng.kundenserver.de has 2 A records:
mrelayng.kundenserver.de internet address = 212.227.126.160
mrelayng.kundenserver.de internet address = 212.227.126.162
212.227.126.160 and 212.227.126.162 have PTR records to
auth.smtp.kundenserver.de
I suppose the provider may change the names and A records of his mailrelays
as he likes. He just has to make sure that the CNAME
auth.smtp.kundenserver.de is an alias of some existing mailrelay and that
the corresponding PTR records are set correctly. The actual A records
shouldn't be of interest.
This is why I think esmtpauthclient should also work with the CNAME instead
of the A record of a mailrelay.
Regards
Manfred
----- Original Message -----
From: "Sam Varshavchik" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, May 14, 2002 10:35 PM
Subject: [courier-users] Re: esmtpauthclient and load balancing providers
> MH - Entwicklung writes:
>
> >
> > ----- Original Message -----
> > From: "Sam Varshavchik" <[EMAIL PROTECTED]>
> > To: <[EMAIL PROTECTED]>
> > Sent: Tuesday, May 14, 2002 3:36 PM
> > Subject: [courier-users] Re: esmtpauthclient and load balancing
providers
> >
> >
> >> The problem here is the CNAME record. Use mrelayng.kundenserver.de
> > instead
> >> of auth.smtp.kundenserver.de
> >>
> >
> > But the official name is auth.smtp.kundenserver.de. This may resolve as
a
> > completely different host (e.g. mrelayng2.kundenserver.de) some days
later.
> > Everytime the Provider changes something, I will have to enter the new A
>
> Well, if the provider changes their DNS, and updates the zone file, it is
> reasonable to expect anyone using the DNS to update their corresponding
> configuration as well.
>
> > different host I have a busy hotline.
> > I've seen providers doing this pretty often - I think for load balancing
and
> > availability reasons.
>
> Load balancing is typically done by simply providing multiple A records.
> Any change to the actual DNS zone requires a complete DNS server reload
with
> the new zone, so it's not really a sane way to do load balancing.
>
>
> --
> Sam
>
>
> _______________________________________________________________
>
> Have big pipes? SourceForge.net is looking for download mirrors. We supply
> the hardware. You get the recognition. Email Us: [EMAIL PROTECTED]
> _______________________________________________
> courier-users mailing list
> [EMAIL PROTECTED]
> Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
>
_______________________________________________________________
Have big pipes? SourceForge.net is looking for download mirrors. We supply
the hardware. You get the recognition. Email Us: [EMAIL PROTECTED]
_______________________________________________
courier-users mailing list
[EMAIL PROTECTED]
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
