This repository was archived by the owner on May 14, 2024. It is now read-only.
Repository navigation
This repository was archived by the owner on May 14, 2024. It is now read-only.
change ldapjs.org dns record #679
Description
The ldapjs.org dns needs to be updated. I updated the gh-pages and got this error by email:
The custom domain for your GitHub Pages site is pointed at an outdated IP address.
You must update your site's DNS records if you'd like it to be available via your custom domain.
It looks like the dns should point to
185.199.108.153
185.199.109.153
185.199.110.153
185.199.111.153
@jsumners do you know who controls the domain name?
Activity
jsumners commentedon Nov 13, 2020
Ugh. That's a thing we never got around to dealing with. Technically Joyent still owns all of that. I'll reach out to people and see if we can get it moved somewhere else. But it may be that we just need to kill of the domain.
UziTech commentedon Nov 13, 2020
We could just use
ldapjs.github.ioby moving the gh-pages branch to the repoldapjs/ldapjs.github.iojsumners commentedon Nov 13, 2020
Yeah, that sounds like a good solution.
UziTech commentedon Nov 13, 2020
I created the repo and set up https://ldapjs.github.io/ I think it would be better if we could work something out with Joyent to keep the domain, but if not we will just need to point everything to the new domain.
jsumners commentedon Dec 16, 2020
@melloc do you have any opinions about managing DNS for
ldapjs.org?Personally, I'm of the opinion that we should just let the domain die. Maybe add a year to it and set it up as a 301 to
ldapjs.github.io. It'll be far easier to maintain as an organization going forward. If we were to try to keepldapjs.orgthen someone would have to keep it paid for, and the org will always be wondering if that person will keep up with it or just disappear and be stuck without the domain.jsumners commentedon Feb 22, 2023
👋
On February 22, 2023, we released version 3 of this library. As a result, we are closing this issue/pull request.
Please see issue #839 for more information, including how to proceed if you feel this closure is in error.