[dns-operations] about list's MX

[Keith Mitchell]

As per the presentation on OARC systems at the Warsaw workshop:

	https://indico.dns-oarc.net//getFile.py/access?contribId=32&resId=0&materialId=slides&confId=19

OARC's e-mail, including the mailman mailing lists, is the one last
thing we need to migrate from the legacy decade-old server to our new
platforms. So any rationale for the current configuration is likely lost
in the depths of time, and it's probably best not to read too much into,
or tinker with, it, not least as it works just fine.

William will be migrating our e-mail/mailman platform to our new server
(to join everything else that has already been migrated) over the next
2-3 weeks, and will be doing any appropriate config clean-up, including
to DNS records if needed, as part of that process.

Keith


On 05/27/2014 09:49 PM, RL Vaughn wrote:
> Being an ancient academic, I am seldom sure about anything except the
> inevitability of uncertainty ;)
> 
> _And_ I can't be certain about openstack.org, but for dns-operations
> my "spidey sense" combined with the mail headers:
> X-Original-To: dns-operations at lists.dns-oarc.net
> Delivered-To: dns-operations at dns-oarc.net
> along with
> lists.dns-oarc.net. 30 IN CNAME mail.dns-oarc.net.
> 
> tell me not to expect a separate MX record for lists.dns-oarc.net.
> 
> All that said, everybody else pointed out the appropriate RFCs etc.
> 
> 
> 
> 
> 
> On 5/27/14, 7:38 PM, hua peng wrote:
>> Are you sure? I meant the list adddress, not the mailbox of the domain itself.
>>
>>> Dig this:
>>> ## dig dns-oarc.net MX
>>>
>>> ; <<>> DiG 9.8.3-P1 <<>> dns-oarc.net MX
>>> ;; global options: +cmd
>>> ;; Got answer:
>>> ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 57215
>>> ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0
>>>
>>> ;; QUESTION SECTION:
>>> ;dns-oarc.net.            IN    MX
>>>
>>> ;; ANSWER SECTION:
>>> dns-oarc.net.        30    IN    MX    0 mail.dns-oarc.net.