Certain DNS services (Duck DNS) only allow a single TXT record for a
domain and all subdomains. So the last TXT value will overwrite all
early values. To support such a service, setting TXT records
must be done in the challenge loop. That way the TXT record is set and
immediately checked before going on to the next one.
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.
## 📋 Pull Request Information
**Original PR:** https://github.com/dehydrated-io/dehydrated/pull/553
**Author:** [@jandryuk](https://github.com/jandryuk)
**Created:** 4/30/2018
**Status:** ❌ Closed
**Base:** `master` ← **Head:** `deploy-challenges`
---
### 📝 Commits (1)
- [`548757a`](https://github.com/dehydrated-io/dehydrated/commit/548757ab46bf1eaf38966eb9d2bc8b1113b988c4) Move hook challenge deployment into loop
### 📊 Changes
**1 file changed** (+5 additions, -8 deletions)
<details>
<summary>View changed files</summary>
📝 `dehydrated` (+5 -8)
</details>
### 📄 Description
Certain DNS services (Duck DNS) only allow a single TXT record for a
domain and all subdomains. So the last TXT value will overwrite all
early values. To support such a service, setting TXT records
must be done in the challenge loop. That way the TXT record is set and
immediately checked before going on to the next one.
---
<sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
📋 Pull Request Information
Original PR: https://github.com/dehydrated-io/dehydrated/pull/553
Author: @jandryuk
Created: 4/30/2018
Status: ❌ Closed
Base:
master← Head:deploy-challenges📝 Commits (1)
548757aMove hook challenge deployment into loop📊 Changes
1 file changed (+5 additions, -8 deletions)
View changed files
📝
dehydrated(+5 -8)📄 Description
Certain DNS services (Duck DNS) only allow a single TXT record for a
domain and all subdomains. So the last TXT value will overwrite all
early values. To support such a service, setting TXT records
must be done in the challenge loop. That way the TXT record is set and
immediately checked before going on to the next one.
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.