serv/mox
1
0
Fork 0
mirror of https://github.com/mjl-/mox.git synced 2024-12-26 16:33:47 +03:00
Code Issues Projects Releases Packages Wiki Activity Actions 1
mox/testdata/integration/example.zone

19 lines
543 B
Dns
Raw Normal View History

mox!
2023-01-30 16:27:06 +03:00
$ORIGIN example.
$TTL 5m
@ IN SOA dns.example. webmaster.example. (1 0m 0m 0m 5m)
@ NS dns.example.
when suggesting DNS records, leave "IN" out people will either paste the records in their zone file. in that case, the records will inherit "IN" from earlier records, and there will always be one record. if anyone uses a different class, their smart enough to know they need to add IN manually. plenty of people will add their records through some clunky web interface of their dns operator. they probably won't even have the choice to set the class, it'll always be IN.
2023-10-13 09:16:46 +03:00
moxacmepebble.mox1 A 172.28.1.10
moxmail2.mox2 A 172.28.1.20
dns A 172.28.1.30
acmepebble A 172.28.1.40
test A 172.28.1.50
localserve.mox1 A 172.28.1.60
postfixmail.postfix A 172.28.1.70
mox!
2023-01-30 16:27:06 +03:00
postfix MX 10 postfixmail.postfix.example.
when suggesting DNS records, leave "IN" out people will either paste the records in their zone file. in that case, the records will inherit "IN" from earlier records, and there will always be one record. if anyone uses a different class, their smart enough to know they need to add IN manually. plenty of people will add their records through some clunky web interface of their dns operator. they probably won't even have the choice to set the class, it'll always be IN.
2023-10-13 09:16:46 +03:00
postfixdkim0._domainkey.postfix TXT "v=DKIM1;h=sha256;t=s;k=ed25519;p=a4IsBTuMsSQjU+xVyx8KEd8eObis4FrCiV72OaEkvDY="
postfix TXT "v=spf1 ip4:172.28.1.20 -all"
Reference in a new issue Copy permalink