🕹 Manage Hack Club's DNS through a GitHub repository
Find a file
2022-01-08 21:51:30 -05:00
.github/workflows Attempt to use Python 3 2021-02-15 18:07:45 -05:00
bin Initial commit 2018-02-26 14:06:01 -08:00
config add dino.icu to production.yaml (#601) 2021-11-11 17:36:09 +08:00
.gitattributes Mark YAML files as Linguist-detectable (#632) 2021-12-17 09:37:59 -08:00
bulckcah.com.yaml proxy.servers.hackclub.com -> proxyparty.hackclub.com 2021-11-23 16:16:19 -05:00
dino.icu.yaml Added normie.dino.icu to yaml file (#631) 2021-12-22 12:42:59 -08:00
dinosaurbbq.org.yaml Remove extra space 2021-10-06 16:43:22 -04:00
hack.af.yaml draw.hack.af 2021-12-20 00:01:56 -05:00
hackclub.app.yaml Clear hackclub.app ACME challenges 2022-01-08 21:51:30 -05:00
hackclub.com.yaml Update hackclub.com.yaml (#635) 2022-01-04 10:43:20 -05:00
hackclub.io.yaml proxy.servers.hackclub.com -> proxyparty.hackclub.com 2021-11-23 16:16:19 -05:00
hackclub.org.yaml proxy.servers.hackclub.com -> proxyparty.hackclub.com 2021-11-23 16:16:19 -05:00
hackedu.us.yaml proxy.servers.hackclub.com -> proxyparty.hackclub.com 2021-11-23 16:16:19 -05:00
hackfoundation.org.yaml Add the.hackfoundation.org 2021-09-30 13:32:55 -04:00
README.md Update README.md 2021-10-15 16:40:22 +08:00

Hack Club's DNS

test deploy

This repository is used for managing Hack Club's DNS configuration through OctoDNS. Please see its documentation for more information.

Domains are available for all clubs and projects related to Hack Club.

Adding a subdomain

  1. Create a fork of this repository.
  2. In your fork open the hackclub.com.yaml file and add the following alphabetically based off the subdomain name:
SUBDOMAIN_NAME:
  - ttl: 1
    type: CNAME
    value: SOURCE_DOMAIN_OR_IP.
  1. Replace SUBDOMAIN_NAME with the name of the sub-domain. So if the name was hello then the subdomain would be hello.hackclub.com.
  2. Replace SOURCE_DOMAIN_OR_IP with the domain or IP address of the website you want the subdomain to go. If you are using an IP address change type: CNAME to type: A. Remember to leave that . at the end!
  3. Commit your changes and create the PR!

That's it! Someone with contributor access to the repo will then review your PR.