[Mageia-sysadm] [257] add MX records for ml.mageia.org

[Michael Scherer]

Le mercredi 17 novembre 2010 à 02:55 +0100, Michael Scherer a écrit :
> Le mercredi 17 novembre 2010 à 02:28 +0100, Dexter Morgan a écrit :
> > On Tue, Nov 16, 2010 at 4:44 PM,  <root at mageia.org> wrote:
> > > Revision 257 Author boklm Date 2010-11-16 16:44:23 +0100 (Tue, 16 Nov 2010)
> > >
> > > Log Message
> > >
> > > add MX records for ml.mageia.org
> > >
> > > Modified Paths
> > >
> > > puppet/modules/bind/templates/zones/mageia.org.zone
> > >
> > > Modified: puppet/modules/bind/templates/zones/mageia.org.zone
> > > ===================================================================
> > > --- puppet/modules/bind/templates/zones/mageia.org.zone	2010-11-16 13:11:13
> > > UTC (rev 256)
> > > +++ puppet/modules/bind/templates/zones/mageia.org.zone	2010-11-16 15:44:23
> > > UTC (rev 257)
> > > @@ -3,7 +3,7 @@
> > >  ; $Id$
> > >  $TTL	3D
> > >  @       IN      SOA     ns0.mageia.org.   root.mageia.org.  (
> > > -        2010111000	; Serial
> > > +        2010111600	; Serial
> > >          21600		; Refresh
> > >          3600		; Retry
> > >          2419200		; Expire
> > > @@ -17,6 +17,9 @@
> > >  @   IN      MX 10   mx0.zarb.org.
> > >  @   IN      MX 20   mx1.zarb.org.
> > >
> > > +ml  IN      MX 10   alamut.mageia.org.
> > > +ml  IN      MX 20   krampouezh.mageia.org.
> > > +
> > >  ; MX
> > >  ;@	IN	MX	10 mx0.zarb.org.
> > >
> > 
> > Hi,
> > 
> > i just have commented those 2 lines for the moment because it breaked
> > alamut and breaks name resolution.
> 
> Can you explain a little bit more ?

So it turn out the zone was incorrect :

 $ /usr/sbin/named-checkzone mageia.org ./mageia.org.zone 
dns_master_load: ./mageia.org.zone:77: ml.mageia.org: CNAME and other
data
zone mageia.org/IN: loading from master file ./mageia.org.zone failed:
CNAME and other data
zone mageia.org/IN: not loaded due to errors.

Ie, we cannot mix CNAME and MX for the same entry in the dns. So I have
moved this to use a A and AAAA record for ml.mageia.org .

I propose to add a check for dns zone in svn that will prevent this
issue next time. ( we do have a working one at zarb that I will cut and
paste ).


-- 
Michael Scherer