#txt record verification for wildcard domain
11 messages · Page 1 of 1 (latest)
Linked Railway resource: f443622d / e4142c3a / 088c60c8
this affects all wildcard registers (at least for me)
and is invalid by RFC 4592, Section 2.1.1
@iron arrow
Thank you for letting me know, we will address this on a workday.
yea sry i totally forgot its weekend~ thanks 4 reply
New reply sent from Central Station thread:
I'm also having this issue trying to add *.staging.example.com. Would really appreciate the fix
You're seeing this because this thread has been automatically linked to the Central Station thread.
New reply sent from Central Station thread:
Having same problem here
You're seeing this because this thread has been automatically linked to the Central Station thread.
New reply sent from Central Station thread:
Hello,
I have verified that it is not valid, and I have since escalated this to our product team.
You're seeing this because this thread has been automatically linked to the Central Station thread.
New reply sent from Central Station thread:
This is fixed, please re-add your wildcard domains.
You're seeing this because this thread has been automatically linked to the Central Station thread.