Possibility to configer DKIM and DMARC on shared IP-address
Until now all our instances are on shared IP. We have a large base of customers, about 1.2 mln (on one instance). And separately some small instances with a lot less contact records.
We would like to have the DMARC and DKIM settings in place on a shared IP. This because of 3 main reasons:
1) Moving with a contact record base that large is hard. Warming up the IP takes at least 5-6 weeks, but possibly more in order to build a good / solid reputation (sender score).
2) The instance has to send a certain amount of constant e-mail volume in order to keep the IP warm. We do not have a constant e-mail volume on all our instances. And second of all: Once every year we have to e-mail all contact records in less then one hour (high volume sender).
3): By buying an Eloqua license we expect Oracle as a supplier to monitor and manage the reputation of the IP-address. For us that is a way of risk management.
If something is going wrong when we are on a dedictaed IP we cannot change anything in a split second. It will always impact our deliverability and buisness e-mail planning. Ultimately, if we have to move to another IP address it takes at least 24-48 hours to get the DNS changes done. Our configuration is not flexible anymore. Because we have to send some legal e-mails at a certain time every year, for us it is very important we can assure the deliveriability is 100% OK.
If I look at other (also smaller) competitors on the market I see that some of them are able to configure it. It would be great if Eloqua would be able to manage it too. DKIM and DMARC are important settings for many reasons.
All the best,
Configure DKIM and SPF before configuring DMARC. DKIM and SPF should be authenticating messages for at least 48 hours before turning on DMARC.
- Have the text file or line that represents your policy record ready.
- Sign in to the management console for your domain host.
- Locate the page where you update DNS records.
- Add a DNS TXT record, or modify an existing record, by entering your record in the TXT record for _dmarc:
- TXT record name: In the first field, under the DNS Hostname, enter: _dmarc.solarmora.com
- Important: Some domain hosts automatically add the domain name after _dmarc. After you add the TXT record, you can verify the DMARC TXT record name to make sure it's formatted correctly.
- TXT record value: In the second field, enter the text for your DMARC record, for example:
v=DMARC1; p=none; rua=mailto:[email protected]
- The field names might be different for your provider. DNS TXT record field names can vary slightly from provider to provider. The domain used here is an example domain. Replace solarmora.com with your own domain.
- Save your changes.
Thank you for your comment. We know how to get things done on our side. Nevertheless, we would like to raise a topic about a proper high volume e-mail sender config. We cannot arrange this without the help of Oracle.
We are on the shared pool and not on dedicated IP at this moment. We would like to make the transition with our excisting Eloqua environments but only if we are equipt with a proper high volume e-mail sender config. In order to set this up Oracle has to configure certain domain related settings in order to set-up DKIM and DMARC for us. This is not IP related. What we would like to have is up-to-date deliverability settings while using the shared pool. At this moment that seems not possible policywise. Ideally we would like to see a dedicated IP with a permanent shared pool fallback that has identical deliverability settings (SPF, DKIM and DMARC) enabled on all excisting environments in order to be fully in control during warm up and in case if something wents wrong on dedicated IP occasionally while working on our buisness goals.