Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix CNAME record in zone avnss.is-cool.dev #1883

Merged
merged 1 commit into from
Dec 26, 2024

Conversation

avengermsoft
Copy link
Contributor

Fix CNAME record in zone avnss.is-cool.dev

Requirements

  • You have completed your website.
  • The website is reachable.
  • The CNAME record doesn't contain https:// or /.
  • There is sufficient information at the owner field.
  • There is no NS Records (Enforced as of Sepetember 4th, 2024)

Fix CNAME record in zone avnss.is-cool.dev
@avengermsoft avengermsoft requested a review from a team as a code owner December 24, 2024 10:39
@open-domains
Copy link

open-domains bot commented Dec 24, 2024

All contributors have signed the CLA ✍️ ✅
Posted by the CLA Assistant Lite bot.

@open-domains open-domains bot added the CLA Required Contributor has not signed the CLA. label Dec 24, 2024
@avengermsoft
Copy link
Contributor Author

I have read the CLA Document and I hereby sign the CLA

@avengermsoft
Copy link
Contributor Author

recheck

open-domains bot added a commit to open-domains/cla that referenced this pull request Dec 24, 2024
@open-domains open-domains bot added CLA Signed Contributor has signed the CLA and removed CLA Required Contributor has not signed the CLA. labels Dec 24, 2024
@DEV-DIBSTER DEV-DIBSTER merged commit b6818be into open-domains:main Dec 26, 2024
5 checks passed
@open-domains
Copy link

open-domains bot commented Dec 26, 2024

Pull Request Merged

Buy Me a Coffee


What's next?

Just follow the steps below and you can start using your domain!

GitHub Pages

  • Go to your GitHub repository that you use for your domain.
  • Click on the Settings tab.
  • Click on the Pages link in the sidebar.
  • In the custom domain option, enter the domain you registered.
  • Check the Enforce HTTPS checkbox.
  • Give your domain some time (~24 hours) for the changes to propagate.
  • Enjoy your domain!

Server Owners

For HTTPS, you will have to configure an SSL certificate to allow the new subdomain to work (here's why).


Need help with your domain? If you have troubles setting up your domain, please create an issue and we will try and help you as soon as possible!

Made a mistake in the records? Don't worry, you can create a new pull request with the corrections.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
CLA Signed Contributor has signed the CLA
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants