1. 09 Jan, 2020 1 commit
  2. 02 Dec, 2019 1 commit
  3. 10 Aug, 2019 1 commit
  4. 09 Aug, 2019 3 commits
  5. 13 Jan, 2017 1 commit
  6. 12 Jan, 2017 1 commit
  7. 29 Oct, 2016 1 commit
  8. 23 Jun, 2016 1 commit
  9. 15 Jun, 2016 1 commit
  10. 07 Jun, 2016 3 commits
  11. 03 Jun, 2016 1 commit
  12. 01 Jun, 2016 1 commit
  13. 31 May, 2016 3 commits
  14. 27 May, 2016 1 commit
  15. 26 May, 2016 2 commits
  16. 06 Feb, 2016 1 commit
  17. 04 Aug, 2015 1 commit
  18. 03 Aug, 2015 1 commit
  19. 29 Jul, 2015 10 commits
  20. 27 Jul, 2015 1 commit
  21. 26 Jul, 2015 1 commit
  22. 20 Jul, 2015 1 commit
  23. 18 Jul, 2015 1 commit
  24. 02 Jul, 2015 1 commit
    • Peter Todd's avatar
      Fix negative responses · 5eca8e26
      Peter Todd authored
      Previously if the resolver was asked for a record it didn't have, it would
      return a response with a NS record in the authority section.  This is
      incorrect, as the lack of answer indicates to the resolver that it should try
      that NS record as the next step, resulting in a loop:
      
          $ dig @8.8.8.8 rbf-seed.btc.petertodd.org TXT +trace
      
          <snip>
      
          rbf-seed.btc.petertodd.org. 300 IN      NS      rbf-seed-ns1.btc.petertodd.org.
          rbf-seed.btc.petertodd.org. 300 IN      NS      rbf-seed-ns2.btc.petertodd.org.
          ;; Received 141 bytes from 205.251.193.174#53(ns-430.awsdns-53.com) in 426 ms
      
          rbf-seed.btc.petertodd.org. 40000 IN    NS      rbf-seed-ns2.btc.petertodd.org.
          ;; BAD (HORIZONTAL) REFERRAL
          ;; Received 88 bytes from 185.52.1.173#53(rbf-seed-ns2.btc.petertodd.org) in 108 ms
      
          rbf-seed.btc.petertodd.org. 40000 IN    NS      rbf-seed-ns2.btc.petertodd.org.
          ;; BAD (HORIZONTAL) REFERRAL
          ;; Received 88 bytes from 185.52.1.173#53(rbf-seed-ns2.btc.petertodd.org) in 108 ms
      
          <snip>
      
          rbf-seed.btc.petertodd.org. 40000 IN    NS      rbf-seed-ns2.btc.petertodd.org.
          ;; BAD (HORIZONTAL) REFERRAL
          dig: too many lookups
      
      The correct response in the authority section of a negative response is a SOA
      record, which indicates that the answer is authoritative and the resolver can
      consider the record missing and stop looking for it:
      
          $ dig @8.8.8.8 rbf-seed.btc.petertodd.org TXT +trace
      
          <snip>
      
          rbf-seed.btc.petertodd.org. 300 IN      NS      rbf-seed-ns1.btc.petertodd.org.
          rbf-seed.btc.petertodd.org. 300 IN      NS      rbf-seed-ns2.btc.petertodd.org.
          ;; Received 141 bytes from 205.251.196.185#53(ns-1209.awsdns-23.org) in 740 ms
      
          rbf-seed.btc.petertodd.org. 40000 IN    SOA     rbf-seed-ns1.btc.petertodd.org. pete.petertodd.org. 1435846201 604800 86400 2592000 604800
          ;; Received 128 bytes from 104.236.95.174#53(rbf-seed-ns1.btc.petertodd.org) in 31 ms
      
      There have been a few reports of problems resolving seed domains on some
      ISPs - hopefully this was the root cause.
      5eca8e26