Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
DreamHost Provider only works if root domain is set with an A or AAAA record
See original GitHub issueI’m using Lexicon to generate certificates an environment where DNS is my only accessible option, but I’ve noticed an odd behavior. It appears that it’ll only successfully authenticate a domain if the @ entry has an A or AAAA record defined in DNS. This is a bit problematic in my environment as I have a CNAME pointed towards hashnode setup for that entry.
Is there any reason why a CNAME would not be regarded as valid for the purposes of authenticating the domain? You can see the behavior defined below.
Issue Analytics
- State:
- Created 2 years ago
- Comments:6 (6 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
A follow-up from Dreamhost confirmed that the APIs that we are using (dns-add_record and dns-remove_record and dns-list_records) are still working.
I’ll update the code and include CNAME
Closed with #1110