coolaj86
/
acme-challenge-test.js
1
0
Fork 0
Code Issues 2 Pull Requests Releases Wiki Activity

Should include TTL for DNS challenges #1

New Issue
Open
opened 2019-06-06 04:19:30 +00:00 by coolaj86 · 0 comments
coolaj86 commented 2019-06-06 04:19:30 +00:00
Owner
Copy Link

The TTL for DNS challenges should be very low. Ideally 0, but many APIs will require 300 as the minimum.

  • Update the test to set ttl: 300 whenever dnsHost is being set.
The TTL for DNS challenges should be very low. Ideally 0, but many APIs will require 300 as the minimum. * [x] Update the test to set `ttl: 300` whenever `dnsHost` is being set.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
master
refactor
v3.3.2
v3.3.1
v3.3.0
v3.2.1
v3.2.0
v3.1.3
v3.1.2
v3.1.1
v3.1.0
v3.0.5
v3.0.4
v3.0.3
v3.0.2
v3.0.1
v3.0.0
Labels
Clear labels
No items
No Label
Milestone
Clear milestone
No items
No Milestone
Assignees
Clear assignees
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: coolaj86/acme-challenge-test.js#1
No description provided.
Delete Branch "%!s(<nil>)"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?