On 13 Oct 2020, at 15:02, Fred Morris wrote:
Hello. Real example of someone with this setup, and all records for
the FQDNs in question, or it didn't happen.
Waving at Fred...
billmail.scconsult.com. 10800 IN MX 0 clues.scconsult.com.
billmail.scconsult.com. 10800 IN MX 10 grumpy.scconsult.com.
scconsult.com. 86400 IN MX 10 sc1.scconsult.com.
scconsult.com. 86400 IN MX 1 toaster.scconsult.com.
On Tue, 13 Oct 2020, @lbutlr wrote:
On 13 Oct 2020, at 12:03, Fred Morris <m3...@m3047.net> wrote:
Notwithstanding, any "fully qualified domain name" (FQDN) can have
email sent to it; typically only the FQDN immediately below the zone
cut, and also the subject of SOA and NS records, has MX records.
Pretty sure it is prefect fine to have different MX records for
subdomains.
example.com MX 10 mail.example.com.
foo MX 10 mail.sub1.example.com.
Bar MX 10 mail.sub2.example.com.
Universities used to often have different MX servers for different
departments/machines, though now it seems they are using external
services for MX (maybe lucky, I checked five and all were using
google or outlook for MX).
Nothing here says that they haven't delegated e.g. foo.example.com.
Here, like this:
MariaDB [DNS]> SELECT name, type FROM Resource WHERE name IN (select
name from Resource where name like '%.washington.edu.' and type =
'MX') GROUP BY name, type ORDER BY name, type;
+---------------------------+------+
| name | type |
+---------------------------+------+
| marge.cac.washington.edu. | A |
| marge.cac.washington.edu. | MX |
| marge.cac.washington.edu. | NS |
| math.washington.edu. | MX |
| math.washington.edu. | NS |
| staff.washington.edu. | MX |
| staff.washington.edu. | NS |
| u.washington.edu. | MX |
| u.washington.edu. | NS |
| www.atmos.washington.edu. | A |
| www.atmos.washington.edu. | MX |
| www.atmos.washington.edu. | NS |
+---------------------------+------+
--
Fred Morris
--
Bill Cole
b...@scconsult.com or billc...@apache.org
(AKA @grumpybozo and many *@billmail.scconsult.com addresses)
Not Currently Available For Hire