Txt record not propagating with the byfleet servers, all other servers are OK

Website, Application, Performance DNS & Network
1

What is the name of the domain?

pnddistribution.com

What is the error message?

Emails not being received for [email protected]

What is the issue you’re encountering

I have recently moved my DNS records from Justhost to Cloudflare and set up the DNS records in Cloudflare as described by Justhost. One server site in Byfleet, UK, is not resolving the record, even though it has been 6 days since the submission of the record. I contacted Justhost, and they advised me to push the record again. Previous support requests by others indicated there was no need to push the records again, so I am uncertain about the appropriate action.

What steps have you taken to resolve the issue?

Yesterday, I edited the previous record and resubmitted it, but there is still no resolution, as shown in this screenshot.

What feature, service or problem is this related to?

DNS not responding/updating

What are the steps to reproduce the issue?

Create dns server enquiry on the dns checker server to show resolution.

Screenshot of the error

DNS txt record not resolving 20241124.png
DNS txt record not resolving 20241124.png892×712 101 KB

2

You do not have an MX record for gdswr. You need to create one if you want to receive emails on that subdomain.

Also, the target of your MX record needs to be set to DNS-Only. It is currently set to proxied (mail.gdswr.pnddistribution.com).

4 Likes
3

All my emails go through a spam check so there is no individual mx record for mail.gdswr>

4

An MX record tells the sender where email for your domain is supposed to go. Without it, you will not receive emails.

It was probably working before switching to Cloudflare because many senders try the A record of your domain as a backup destination. As this now points to Cloudflare, it no longer works.

5 Likes
5

No it is a new email address and the current mx record covers it. You are right, the no PTR appears the problem. As a result it is on the UCEPROTECT level 3 block list because I had no reverse DNS setting. rDNS is now set and I am just waiting on the mandatory 7 days requirement that UCEPROTECT use, before they take it off the blocklist.

6

This shows the current MX records which are working for my email addresses.

CloudFare mx records
CloudFare mx records570×136 9.25 KB

7

No, it does not.

If you have cannot receive email deliveries to “@gdswr.pnddistribution.com”, you need to check the MX records for “@gdswr.pnddistribution.com”, and/or consult the email provider you have, for those MX records.

These are the MX records are only valid for @pnddistribution.com email addresses.

You will need MX records in the Dashboard, that are showing up with the name "gdswr", if they should work for the “”@gdswr.pnddistribution.com"" host name, as @Laudian indicated above.

Your A/AAAA records on “gdswr.pnddistribution.com” are currently Proxied (:orange:), so there is NO WAYS AT THE MOMENT, to deliver messages towards the “@gdswr.pnddistribution.com” host name.

With no MX records, and the A/AAAA records being Proxied (:orange:), other email servers that are following the standards, will currently try to deliver messages to Cloudflare’s HTTP Proxies, when sending email to “@gdswr.pnddistribution.com” email addresses, @Laudian also referred to.

Are you having issues with receiving emails, as indicated in your first post?

Or are you having issues, with getting the emails you’re sending, delivered to somewhere else?

And what error code(s)/message(s) do you see?

As you mentioned Level 3, I think you need to read their listing (and de-listing) policies again.

If there still appears to be issues on the IP range (Level 2), or ISP (Level 3) you’re a part of, you will not get out of Level 2 nor Level 3 blocking after 7 days.

Fixing Level 2 and Level 3, is NOT just about waiting, but will require your ISP to mitigate the alleged issues, such as e.g. by kicking off the alleged abusers from their networks.

3 Likes
8

Thanks I am working on the separate issue of the UCEPROTECT level 3 issue. This problem may be related to the DNS cache, how does Cloudflare flush the DNS cache?

9

I am talking about flushing the DNS cache for the Byfleet servers in the UK, because all the other servers have resolved the DNS propagation but not Byfleet.(refer to image above). It has been over 7 days now!

10

You can’t work on that issue. There’s literally nothing you can do except find a new email service, unless you want to count complaining to your existing provider.

A level 3 listing is punitive in nature - companies using UCEPROTECT level 3 accept that they block large amounts of legitimate email in order to apply pressure to network operators that don’t act against spammers.

Stop wasting your time and ignore this “issue”. it is completely meaningless, your DNS is working fine.

It does not look like you have implemented any of the advice given, so you should not expect anything to change until you do.

2 Likes
11

I do not understand my email provider says I have the required mx records set up correctly and because they go through a spam checking for the parent company first as shown below?

CloudFare mx records
CloudFare mx records570×136 9.25 KB
.
Also if this is not set up correctly why have the other servers accepted the txt records? Please help me understand?

12

I have set the A records and cname records to DNS only.

13

What exact email address(es) are we talking about, that you believe aren’t working?

  1. [email protected]

or

  1. [email protected]

With your current set up, - #2 will work, but #1 will NOT work, because #1 is NOT set up properly, with MX records.

Both @Laudian and I have already mentioned how to fix number #1 from above, according to the way you are explaining the issue.

If you’re just ignoring the advice we’re giving you, … then we cannot help you.

2 Likes