They prevent people who start a potentially rogue mailserver to receive mails. I.e. You centralize mails and make sure only your authorized mailserver receives them when you dont have full control over these boxes.
-mat On Oct 28, 2010, at 8:48 AM, Sten Carlsen <st...@s-carlsen.dk> wrote: > To me it looks redundant, "named-compilezone -o - zone file" should show you > how bind interprets these. > My guess is that they will be listed only once in the output. > > I don't see how they could belong to each subdomain, to do that there should > be a"@..." to set a new origin? > > > > On 28/10/10 2:14, Ian Manners wrote: >> >> Hi Gregory, >> >>> mail02 IN A 192.168.xx.xx >>> IN MX 10 mcvpemr01 >>> IN MX 10 mcvpemr02 >>> nelson IN A 202.xx.xx.1 >>> IN MX 10 mcvpemr01 >>> IN MX 10 mcvpemr02 >> >>> My question is why would "IN MX 10 mcvpemr01" and "IN MX >>> 10 mcvpemr02" be repeated trough the zone file surely this is >>> redundant ? >> It looks like an old way of specifying the MX for each subdomain. >> >> Cheers >> Ian Manners >> http://www.os2site.com/ >> >> _______________________________________________ >> bind-users mailing list >> bind-users@lists.isc.org >> https://lists.isc.org/mailman/listinfo/bind-users > > -- > Best regards > > Sten Carlsen > > No improvements come from shouting: > > "MALE BOVINE MANURE!!!" > _______________________________________________ > bind-users mailing list > bind-users@lists.isc.org > https://lists.isc.org/mailman/listinfo/bind-users
_______________________________________________ bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
