This forum uses cookies
This forum makes use of cookies to store your login information if you are registered, and your last visit if you are not. Cookies are small text documents stored on your computer; the cookies set by this forum can only be used on this website and pose no security risk. Cookies on this forum also track the specific topics you have read and when you last read them. Please confirm whether you accept or reject these cookies being set.

A cookie will be stored in your browser regardless of choice to prevent you being asked this question again. You will be able to change your cookie settings at any time using the link in the footer.

DNS MX record issue
#5
RE: DNS MX record issue
(10-15-2022, 09:52 AM)fearworks Wrote: Ok, I think I see the issue. For any record where the target is a domain name (for example the two I can see in your screenshot would be the CNAME and the MX) you have specified a domain name, but using syntax that is being interpreted as a subdomain. I would have expected this to be explained somewhere in the interface, or a warning show somewhere, but anyway, the explanation is this. Put a period (we call it a full stop here in the UK) at the end of the domain names in your target column, so instead of:

target.clickfunnels.com

and

mail.rstinternetmarketing.com

for the CNAME and the MX record, put this:

target.clickfunnels.com.

and

mail.rstinternetmarketing.com.

and do the same for any other targets that are domain names and not IP addresses. The period (full stop) should tell their DNS system to treat the domains as a full domain and not a subdomain of the current domain. The documentation here:

https://docs.hetzner.com/dns-console/dns...mx-records

suggests that this is only required for domains outside of the current domain (so is needed for the CNAME domain anyway) but it appears to be required even for the MX record, and event though it is within the same domain... not sure why but try it and then post to say you have changed it, and we'll see if the MX domain shows correctly.

Edit: I guess with the MX record, because the target is within the same domain, you should actually be able to just add:

mail

as the target without the rest fo the domain, and it should serve it up as the correct record. Try it, take another screenshot of the same page to show what you changed, and we'll see how it goes.

K

So far, so good -- it has been receiving and sending since your last post, thanks to YOU and the period/full stop!

As I said, I am using the 2.0 installation on a new server and all seems to be well. Are you hearing anything about issues, and any word on the Upgrade?
Thanks given by:


Messages In This Thread
DNS MX record issue - by rsthomas - 10-13-2022, 01:22 AM
RE: DNS MX record issue - by fearworks - 10-15-2022, 07:24 AM
RE: DNS MX record issue - by rsthomas - 10-15-2022, 09:05 AM
RE: DNS MX record issue - by fearworks - 10-15-2022, 09:52 AM
RE: DNS MX record issue - by rsthomas - 10-19-2022, 12:29 AM
RE: DNS MX record issue - by fearworks - 10-19-2022, 05:39 AM

Possibly Related Threads…
Thread Author Replies Views Last Post
managed-key permission issue Juan Pablo 15 37 ,494 04-10-2019, 12:54 AM
Last Post: Juan Pablo
Issue accessing/pinging 2nd installed domain Fudnut 9 23 ,991 03-14-2019, 04:33 PM
Last Post: fearworks
Cloudflare issue with sentora testing 3 11 ,067 11-21-2017, 07:35 PM
Last Post: Me.B

Forum Jump:


Users browsing this thread: 1 Guest(s)