How reply the same MX RRs list for all kind of MX request
Todd Snyder
tsnyder at rim.com
Thu Nov 26 19:50:50 UTC 2009
You can create an include file, and put it right under your SOA/NS
records. The file should start with blanks... something like:
@ IN SOA ns.example.com. root. (
2009112601 ; Serial
1h ; Refresh
20m ; Retry
1w ; Expire
1h ; Minimum
)
IN NS ns1.
$INCLUDE mx-records.include
#mx-records.include
IN MX 10 mx.example.com
that will end up putting an MX record for each zone in each zone without
needing a bunch of different lines or includes.
Hopefully that helps, or is even in the right direction.
YMMV.
Todd.
-----Original Message-----
From: bind-users-bounces at lists.isc.org
[mailto:bind-users-bounces at lists.isc.org] On Behalf Of Frank Abel Cancio
Bello
Sent: Thursday, November 26, 2009 11:20 AM
To: bind-users at lists.isc.org
Subject: How reply the same MX RRs list for all kind of MX request
Hi all,
First at all, I'm newbie in DNS, so excuse me if I'm posting something
stupid here ;)
I want DNS replying the same list of MX RRs for all MX request. I mean,
any client that want send an email and query my DNS for a MX RRs must
get the same MX RRs, not matter of what domain the client is requesting
the MX RRs. Is that possible in any way?
Thanks in advance.
Cheers
Frank Abel
_______________________________________________
bind-users mailing list
bind-users at lists.isc.org
https://lists.isc.org/mailman/listinfo/bind-users
---------------------------------------------------------------------
This transmission (including any attachments) may contain confidential information, privileged material (including material protected by the solicitor-client or other applicable privileges), or constitute non-public information. Any use of this information by anyone other than the intended recipient is prohibited. If you have received this transmission in error, please immediately reply to the sender and delete this information from your system. Use, dissemination, distribution, or reproduction of this transmission by unintended recipients is not authorized and may be unlawful.
More information about the bind-users
mailing list