Answers: <p>When I lookup your domain thuijls.net on <a href="https://mxtoolbox.com/SuperTool.aspx?action=a%3Athuijls.net&amp;run=toolpage#" rel="nofollow noreferrer">MXToolBox</a> I get the following messageL</p>
  
  <p><strong>Dns record not found</strong></p>
  
  <p>They explain this to mean:</p>
  
  <blockquote>
    <p>More Information About Dns Record Published<br/>
    We did not find a SPF (TXT) record for the domain. Either you are using the deprecated type "SPF" record (in which case you will see a warning message for this alongside this message) or no record exists.</p>
    
    <p>For a SPF record to be valid, it must at least contain v=spf1</p>
  </blockquote>
  
  <p>A TXT lookup for thuijls.net yeilds: </p>
  
  <p><code>Type   Domain Name     TTL     Record</code><br/>
  <code>TXT    thuijls.net     5 min   v=spf1 include:spf.messagingengine.com ?all</code></p>
  
  <p>The problem is the ?all - you probably copy-pasted this from somewhere and the (non-standard) hyphen became a question mark.</p>
  
  <p>Edit your TX record to read <code>v=spf1 include:spf.messagingengine.com -all</code> and all will be good.</p>
  
  <p>Then you can add a 2nd TXT entry for your  <code>"protonmail-verification-da....."</code> setting.</p>
  
Answers: CC BY-SA 4.0
Answers: 2019-10-02T09:32:13.203Z
Answers: 2019-10-02T09:32:13.203Z
Answers: Danny Schoemann
Body: <p>Last week, my TXT and other DNS records on Route53 stopped resolving:</p>
  
  <p><a href="https://dnschecker.org/#TXT/thuijls.net" rel="nofollow noreferrer">https://dnschecker.org/#TXT/thuijls.net</a></p>
  
  <p>The entries are set like:</p>
  
  <p><a href="https://i.sstatic.net/J1keG.png" rel="nofollow noreferrer"><img src="https://i.sstatic.net/J1keG.png" alt="enter image description here"></a></p>
  
  <p>What else could be missing here? As far as I'm aware, nothing has changed in the last week yet most of the entries are not being picked up. The domain was automatically extended earlier september if that makes a difference.</p>
  
Tags: <amazon-web-services><dns>
Title: Route53 DNS records stopped resolving
UserDisplayName: Jorg
ThreadText: # Route53 DNS records stopped resolving
  
  (Asked by: username_0 on 2019-10-01)
  
  Last week, my TXT and other DNS records on Route53 stopped resolving:
  
  <https://dnschecker.org/#TXT/thuijls.net>
  
  The entries are set like:
  
  [![enter image description here](https://i.sstatic.net/J1keG.png)](https://i.sstatic.net/J1keG.png)
  
  What else could be missing here? As far as I'm aware, nothing has changed in the last week yet most of the entries are not being picked up. The domain was automatically extended earlier september if that makes a difference.
  
  **Tags:** amazon-web-services, dns
  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_1 on 2019-10-02. Score: 1
  
  When I lookup your domain thuijls.net on [MXToolBox](https://mxtoolbox.com/SuperTool.aspx?action=a%3Athuijls.net&run=toolpage#) I get the following messageL
  
  **Dns record not found**
  
  They explain this to mean:
  
  > More Information About Dns Record Published  
  > We did not find a SPF (TXT) record for the domain. Either you are using the deprecated type "SPF" record (in which case you will see a warning message for this alongside this message) or no record exists.
  >
  > For a SPF record to be valid, it must at least contain v=spf1
  
  A TXT lookup for thuijls.net yeilds:
  
  `Type Domain Name TTL Record`  
  `TXT thuijls.net 5 min v=spf1 include:spf.messagingengine.com ?all`
  
  The problem is the ?all - you probably copy-pasted this from somewhere and the (non-standard) hyphen became a question mark.
  
  Edit your TX record to read `v=spf1 include:spf.messagingengine.com -all` and all will be good.
  
  Then you can add a 2nd TXT entry for your `"protonmail-verification-da....."` setting.
  
  
  ---
  
  