out of place mx records.
Barry Margolin
barmar at alum.mit.edu
Thu Oct 28 02:15:36 UTC 2010
In article <mailman.575.1288226936.555.bind-users at lists.isc.org>,
Sten Carlsen <stenc at 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 suggest you try it, and you'll see that you guessed wrong.
>
> I don't see how they could belong to each subdomain, to do that there
> should be a"@..." to set a new origin?
@ doesn't set a new origin, $ORIGIN does. @ is simply a special token
that gets replaced with the current origin.
When you begin a record with blank space, it means that it uses the
owner name from the previous line. So:
mail02 IN A 192.168.x.x
IN MX 10 mcvpemr01
IN MX 10 mcvpemr02
is equivalent to:
mail02 IN A 192.168.x.x
mail02 IN MX 10 mcvpemr01
mail02 IN MX 10 mcvpemr02
>
>
>
> 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 at lists.isc.org
> > https://lists.isc.org/mailman/listinfo/bind-users
--
Barry Margolin, barmar at alum.mit.edu
Arlington, MA
*** PLEASE don't copy me on replies, I'll read them in the group ***
More information about the bind-users
mailing list