In Dynamics 365 we need to be able to authenticate our domain for sending marketing emails. We have followed the advice in the Microsoft article below and now need to add the DNS records.
The TXT record it gives in the configuration is for the top level domain of our organisation. That is the one we want to authenticate. The thing is that our DNS already has a TXT record with the '@' symbol. I understand that this is a shortcut to the top level domain. If I were to add the additional value to that existing record of the key given in Dynamics 365, will that cause any issues? Is it safe to do that?
The text record already has values for SPF and some other keys.
Most of the semi-common things that store values in TXT records at the root are smart enough to have some kind of identifier in the record, or just accept all the TXT records and just look through them for the value they want.
Common TXT types that with some identifiers. SPF TXT record will start with
v=spf1
. DMARC withv=DMARC1;
Google site verifications will start withgoogle-site-verification=
.From your link
The
d365mktkey=
part is used to define this record is for dynamics.Anyway, nothing should break by adding another TXT record.
It's safe to have multiple values in a single TXT record.
Route53 (AWS DNS service) for example will not allow multiple TXT records for a specific value in a zone. Other DNS providers will allow you to break them out, but if you dig for TXT records you'll get all of them back anyway so there really isn't a reason to break them up.