Years ago, the epel.io domain redirected to the EPEL wiki page. That redirect no longer works. I would like to see that working again, but pointing to the EPEL docs home page this time (which the wiki also redirects to).
There is no deadline for this. It's not blocking any other work, it's just a nice to have for project discoverability and to easily share with new community members.
@kevin Do we even own epel.io?
Metadata Update from @zlopez: - Issue tagged with: epel
WHOIS search results Domain Name: epel.io Registry Domain ID: 8a95a97348ff4e75a8616765149cd951-DONUTS Registrar WHOIS Server: whois.comlaude.com Registrar URL: http://www.comlaude.com Updated Date: 2023-09-09T23:25:07Z Creation Date: 2017-10-04T14:18:53Z Registry Expiry Date: 2024-10-04T14:18:53Z Registrar: Nom-iq Ltd. dba COM LAUDE Registrar IANA ID: 470 Registrar Abuse Contact Email: abuse@comlaude.com Registrar Abuse Contact Phone: +44.2074218250 Domain Status: clientDeleteProhibited https://icann.org/epp#clientDeleteProhibited Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited Domain Status: clientUpdateProhibited https://icann.org/epp#clientUpdateProhibited Registry Registrant ID: REDACTED FOR PRIVACY Registrant Name: REDACTED FOR PRIVACY Registrant Organization: Red Hat, Inc. Registrant Street: REDACTED FOR PRIVACY Registrant City: REDACTED FOR PRIVACY Registrant State/Province: NC Registrant Postal Code: REDACTED FOR PRIVACY Registrant Country: US Registrant Phone: REDACTED FOR PRIVACY Registrant Phone Ext: REDACTED FOR PRIVACY Registrant Fax: REDACTED FOR PRIVACY Registrant Fax Ext: REDACTED FOR PRIVACY Registrant Email: Please query the RDDS service of the Registrar of Record identified in this output for information on how to contact the Registrant, Admin, or Tech contact of the queried domain name. Registry Admin ID: REDACTED FOR PRIVACY Admin Name: REDACTED FOR PRIVACY Admin Organization: REDACTED FOR PRIVACY Admin Street: REDACTED FOR PRIVACY Admin City: REDACTED FOR PRIVACY Admin State/Province: REDACTED FOR PRIVACY Admin Postal Code: REDACTED FOR PRIVACY Admin Country: REDACTED FOR PRIVACY Admin Phone: REDACTED FOR PRIVACY Admin Phone Ext: REDACTED FOR PRIVACY Admin Fax: REDACTED FOR PRIVACY Admin Fax Ext: REDACTED FOR PRIVACY Admin Email: Please query the RDDS service of the Registrar of Record identified in this output for information on how to contact the Registrant, Admin, or Tech contact of the queried domain name. Registry Tech ID: REDACTED FOR PRIVACY Tech Name: REDACTED FOR PRIVACY Tech Organization: REDACTED FOR PRIVACY Tech Street: REDACTED FOR PRIVACY Tech City: REDACTED FOR PRIVACY Tech State/Province: REDACTED FOR PRIVACY Tech Postal Code: REDACTED FOR PRIVACY Tech Country: REDACTED FOR PRIVACY Tech Phone: REDACTED FOR PRIVACY Tech Phone Ext: REDACTED FOR PRIVACY Tech Fax: REDACTED FOR PRIVACY Tech Fax Ext: REDACTED FOR PRIVACY Tech Email: Please query the RDDS service of the Registrar of Record identified in this output for information on how to contact the Registrant, Admin, or Tech contact of the queried domain name. Name Server: ns02.fedoraproject.org Name Server: ns05.fedoraproject.org Name Server: ns-iad01.fedoraproject.org Name Server: ns-iad02.fedoraproject.org
I thought it should have been in the dns database and the ansible named/bind role...
Metadata Update from @phsmoura: - Issue priority set to: Waiting on Assignee (was: Needs Review) - Issue tagged with: low-gain, low-trouble, ops
I’ve looked into this a little:
epel.io
master/epel.io
SOA
NS
A
playbooks/include/proxies-websites.yml
If I get this right, these two things need to be changed to fulfill the request:
CNAME
I haven’t done anything regarding either DNS or proxy redirects on our infra before, so I’d appreciate if someone experienced checked my assumptions and maybe walk me through this.
PS: looked into https://docs.fedoraproject.org/en-US/infra/sysadmin_guide/dns/ and it’s scary. 😉
/cc @phsmoura @patrikp @kevin
yeah, we deliberatly do not have A records for a lot of the domains so we don't get people trying to use them and reporting ssl cert problems or other issues.
So, yep. You have it pretty right there as to what we need to do:
Add A records for it in dns
Add a website entry for it in playbooks/includes/proxies-websites.yml This needs to enable letsencrypt so we get a ssl cert for it.
Add a redirect for it in playbooks/includes/proxies-redirects.yml.
Then, run proxies playbook, wait several hours and it's good. :) Alternately, you can include a ansible tag on the website / redirect entries and run proxies playbook with -t tagname to avoid hours of waiting. :)
The proxy needs to redirect to the EPEL wiki page instead of the root site.
The EPEL wiki page actually redirects to the EPEL docs homepage. So to avoid multiple redirects, it would be best to have epel.io redirect directly to the docs.
i.e. not this
epel.io -> https://fedoraproject.org/wiki/EPEL -> https://docs.fedoraproject.org/en-US/epel/
but rather this
epel.io -> https://docs.fedoraproject.org/en-US/epel/
Metadata Update from @nphilipp: - Issue assigned to nphilipp
Trying my luck…
Commit f77c5fdd fixes this issue
Log in to comment on this ticket.