Force enable tracking to bypass DNS detection issues #2529
deefdragon
started this conversation in
Feature suggestions
Replies: 1 comment 3 replies
-
That is interesting, I didn't know that it checks the DNS status. postal/lib/postal/message_parser.rb Line 11 in 2f62baa It looks like the code records the error in the database, can you confirm what the error message recorded is? postal/app/models/track_domain.rb Lines 54 to 70 in 2f62baa I imagine the problem is that the code is explicitly looking for a CNAME and I believe cloudflare proxying probably emits A records. Is there any reason you're using proxying for this? |
Beta Was this translation helpful? Give feedback.
3 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Describe the bug
I'm having some issues with cloudflare and setting up the DNS for tracking in postal. Whenever I get it correctly detected, it will eventually disable itself and stop tracking because of DNS failures.
Id like the ability to force tracking even if postal thinks the DNS is incorrect.
It would also be nice to get some better errors on the "check DNS" button as even checking the logs I dont get anything, and debugging is mostly me just trying things until they work.
To Reproduce
Set click.mydomain and track.postal.mydomain in cloudflare, both proxied.
Expected behaviour
Better erroring on the check DNS to explain what is incorrect, and the ability to override if its functioning through all other testing.
Environment details
Beta Was this translation helpful? Give feedback.
All reactions