$include

[Ed Conto]

>
>>                         IN      MX      10     $include /var/named/MX
>

To get this to work, you need to start with the "$include /var/named/MX" on
the line, and in the file "/var/named/MX", you would have something like :

@	IN	MX	10 your.mx.server.
@	IN	MX	20 your.second.server.


Whenever you have a host that needs these MX records, you would add one line
to the zone file:

$include /var/domain/MX host.for.mxers
$include /var/domain/MX host2.for.mxers

This would translate into:

host.for.mxers	IN	MX	10 your.mx.server.
host.for.mxers	IN	MX	20 your.second.server.
host2.for.mxers	IN	MX	10 your.mx.server.
host2.for.mxers	IN	MX	20 your.second.server.


-Ed





-----Original Message-----
From: bind-users-bounce at isc.org [mailto:bind-users-bounce at isc.org]On
Behalf Of Doug Barton
Sent: Thursday, February 01, 2001 8:20 PM
To: Joseph S D Yao
Cc: Charles Bodley; bobvance at alumni.caltech.edu; bind-users at isc.org
Subject: Re: $include



On Thu, 1 Feb 2001, Joseph S D Yao wrote:

> I hadn't even noticed that $ORIGIN at the beginning.  IMNSHO, they are
> almost always confusing and evil.  Remove it.

	I've switched over to specifying the name explicitly instead of
using the @ sign in the SOA, unless I'm using the same zone file for
numerous zones. Two reasons, one it shows mistakes instantly if (for
example) someone copies and pastes a line from a conf file and changes the
name in one spot but not the other. The second reason is that it makes the
file more readable out of context, without resorting to nasty measures
such as $ORIGIN, comments in the file, etc.

FWIW,

Doug
--
    "Pain heals. Chicks dig scars. Glory . . . lasts forever."
        -- Keanu Reeves as Shane Falco in "The Replacements"

	Do YOU Yahoo!?