# Admin e-mail voor nieuwe installatie

**URL:** https://meta.discourse.org/t/admin-email-for-new-installation/257624
**Category:** Self-hosting
**Tags:** email
**Created:** [9 maart 2023 om 16:55 UTC](https://meta.discourse.org/t/admin-email-for-new-installation/257624 "2023-03-09T16:55:16Z")
**Posts on this page:** 5
**Page:** 1

<div class="post-metadata">

### Author: ![milespearce](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/milespearce/32/297689_2.png) [@milespearce](https://meta.discourse.org/u/milespearce)
#### Post date: [9 maart 2023 om 16:55 UTC](https://meta.discourse.org/t/admin-email-for-new-installation/257624/1 "2023-03-09T16:55:16Z")

</div>

I have just installed my first discourse forum on a digital ocean droplet. I read here [discourse/docs/INSTALL-email.md at main · discourse/discourse · GitHub](https://github.com/discourse/discourse/blob/main/docs/INSTALL-email.md) that “you _must_ verify and use the subdomain, e.g. `discourse.example.com`. If you verify the domain only, e.g. `example.com`, mail will not be configured correctly.”

My problem is that I can’t figure out how to set up email hosting for [admin@discourse.mydomain.com](mailto:admin@discourse.mydomain.com). My domain name is hosted at namecheap, and I created an A record for the discourse subdomain to Digital Ocean, but I’m not sure how to point the email DNS for my subdomain to a different IP address using namecheap DNS settings.

---

<div class="post-metadata">

### Author: ![Stephen](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/stephen/32/95011_2.png) [@Stephen](https://meta.discourse.org/u/Stephen)
#### Post date: [9 maart 2023 om 17:05 UTC](https://meta.discourse.org/t/admin-email-for-new-installation/257624/2 "2023-03-09T17:05:08Z")

</div>

Hey @milespearce

Your ‘a’ record points to the server which hosts your Discouse instance.

A different type of DNS record called an ‘mx’ or Mail eXchange will point to the whereabouts of your email.

If you’re using the mail receiver then your MX record would point at the FQDN (Fully Qualified Domain Name) of your Discourse instance, otherwise it will point at the mail provider you’ve selected.

---

<div class="post-metadata">

### Author: ![milespearce](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/milespearce/32/297689_2.png) [@milespearce](https://meta.discourse.org/u/milespearce)
#### Post date: [9 maart 2023 om 17:11 UTC](https://meta.discourse.org/t/admin-email-for-new-installation/257624/3 "2023-03-09T17:11:52Z")

</div>

Thank you @Stephen! I did add an MX record pointing the discourse subdomain to my hosting account at Cloudways, but when I tried to create the email address using their rackspace addon it says “(!) [discourse.mydomain.com](http://discourse.mydomain.com) already exists as a domain or alternate domain” and does not allow me to create the email address.  
✏ Edit: realizing now that I only updated one of the DNS records required by Rackspace, and not the MX records. I’ll try this again.  
Edit2: I updated the 2 MX records and the TXT record from these instructions [https://docs.rackspace.com/support/how-to/set-up-dns-records-for-cloud-office-email/](https://docs.rackspace.com/support/how-to/set-up-dns-records-for-cloud-office-email/) and am still getting the same error.

---

<div class="post-metadata">

### Author: ![milespearce](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/milespearce/32/297689_2.png) [@milespearce](https://meta.discourse.org/u/milespearce)
#### Post date: [9 maart 2023 om 17:48 UTC](https://meta.discourse.org/t/admin-email-for-new-installation/257624/4 "2023-03-09T17:48:18Z")

</div>

Success! I started a chat with Cloudways support and they solved the problem almost immediately.

---

<div class="post-metadata">

### Author: ![system](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/system/32/443519_2.png) [@system](https://meta.discourse.org/u/system)
#### Post date: [8 april 2023 om 17:48 UTC](https://meta.discourse.org/t/admin-email-for-new-installation/257624/5 "2023-04-08T17:48:37Z")

</div>

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.
