blob: e56a4aebc82d57e4a2cf24a50ab7e061b15e1e4a (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
|
---
title: "Wildcard Mx and a Dns Record Conflict"
categories:
- blog
abstract: How to have a wildcard email and same domain for a webpage?
year: 2023
date: 2023-01-15T17:43:42+01:00
draft: false
tags:
- DNS
- mx-record
- a-record
- e-mail
---
A random problem I've just encountered by discovering that my email is broken. You can have a wildcard MX record (*.domain), which will handle all subdomains not defined by other records.
> A common mistake is thinking that a wildcard MX for a zone will apply to all
hosts in the zone. A wildcard MX will apply only to names in the
zone which aren't listed in the DNS at all.
> [RFC1912](https://www.rfc-editor.org/rfc/rfc1912)
So, in this case, an A record for test.domain will break the email for test@domain. Solution: add a dedicated MX record for this domain (MX test.domain) with the same value as the wildcard. Now, even if the wildcard one is ignored, the client will fall back to the new record.
```
*.domain MX 10 addr
test.domain A 10 adddr2
test.domain MX 10 addr
```
|
