-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
w3id.org dns seems to have < 1 year to go #81
Comments
Yes, we intend to do that. It hasn't happened yet for two reasons:
|
I am more concerned about the live expectancy of the organization behind webid.org. As long as it is alive it will be able to ensure that the domain is paid in regular intervals. And if it dies it then would not even be able to ensure that the other side of a contract does what it was bound to do. I think it would be more important if webid.org users could automatically be notified by a dead man's switch in case webid.org dies or the domain is not paid in time. |
(oops - this was from @halindrome) I agree that this is a concern. But let's not over think it. Domain I DO like the idea of some sort of dead man's switch. I wonder if there is On Thu, May 7, 2015 at 9:23 AM, Andreas Kuckartz notifications@github.com
Shane McCarron |
Hi all, Well, the entire point of w3id.org http://w3id.org/ is that there are many organizations involved. It is true that the DNS registration is a well-known Achilles heel, in that one organization oversees it. So, I do not worry about the life expectancy of “the organization”, but we do need to ensure that the DNS is paid. I’ll pay it if necessary. I’m sure others would, too. Regards, Dave
|
Hey all, I'm going to take care of this today. It's the last existential issue left wrt. w3id.org, so let's just fix it. Here's what I'm going to do:
That should take care of this perceived problem. To be clear, the problem was never money or institutional longevity. It was time and making sure the money was coming from the right source (a non-profit, so that we didn't need to dip into our personal bank accounts). At this point I've spent far more time explaining to people why this isn't a problem than it would've taken to just fix the issue. So, I'm fixing the issue now. :) |
Thanks, Manu! Regards, Dave
|
Thanks! Maybe we should make a buddylist of people burdened with long-lived semweb related namespace domains, and keep in touch to ensure the relevant DNS situations are remain healthy? Dan (xmlns.com-owner-victim since 2000:) |
We can make BuddyList Group right now, and right here, via responses to this comment. Simply use Nanotation to get this going. Initial salvo: { <#BuddyGroup> <#i> If markdown is messing this up,just lookup: http://kingsley.idehen.net/DAV/home/kidehen/Public/Linked%20Data%20Documents/Nanotations/random-notes-about-w3id.ttl. Scratch statement above, it works! [1] http://linkeddata.uriburner.com/about/html/https/github.com/perma-id/w3id.org/issues/81? -- Basic Entity Description Page [2] http://linkeddata.uriburner.com/c/9C44GMFQ -- Faceted Browsing oriented Page [3] http://linkeddata.uriburner.com/c/9KPSIYX -- About BuddyList Group . |
The domain transfer is now complete... no thanks to the old provider whose domain transfer page just so happened to have a glitch in it that caused the operation to take the maximum time allowed by the rules that govern registrars. Funny how often that happens. I'll send out the new login info to the trustees of w3id.org soon-ish. I also tried renewing for 10 years and got some strange error:
So, good job on sync'ing the front-end verification code w/ the back end verification code, guys. I'll try renewing for a shorter timeframe tomorrow. |
The w3id.org domain has been renewed for 9 years (the max allowable). The w3id.org domain expires on 2024-02-14 21:17:29 |
Manu, w3id.org http://w3id.org/ is down, and it appears to be due to DNS. DNS is resolving to the registrar. Regards, Dave
|
For me it shows a webpage saying "This domain name has been registered with Gandi.net" |
Yeah, on it. I told Gandhi not to muck w/ the DNS - but it did anyway. 3 hour TTL... so it'll take a while for the domain to propagate since it's already being cached elsewhere on the net. The zone file is in place... we just need to wait for it to propagate. |
I'd just like to point out the irony that our biggest downtime for the site to date, /by far/, was due to DNS issues as a result of us trying to ensure that the site wouldn't go away due to DNS issues. :P |
:) gotta get worse before it gets better? thanks for wrestling with this! |
Hi Manu, I don’t think the zone file is necessarily correct. I flushed my local DNS cache and received the following results from dig. Note that www.w3id.org http://www.w3id.org/ and w3id.org http://w3id.org/ resolve to different IPs. Regards, Dave[[ ; <<>> DiG 9.8.3-P1 <<>> w3id.org ;; QUESTION SECTION: ;; ANSWER SECTION: ;; Query time: 2 msec Macadamia:~ dwood$ dig www.w3id.org ; <<>> DiG 9.8.3-P1 <<>> www.w3id.org ;; QUESTION SECTION: ;; ANSWER SECTION: ;; Query time: 126 msec Macadamia:~ dwood$
|
Looking into it... |
Ok, fixed... maybe - it takes a while for this stuff to propagate, so this time should work. I mistakenly set the IP to DB's public cloud instead of the Rackspace VM IP. Thankfully, @davidlehn fixed it shortly thereafter. |
Post-mortem on this tragic thread is here: https://lists.w3.org/Archives/Public/public-perma-id/2015May/0003.html |
Apologies for necroposting but as you already know this is coming up for renewal in a few months:
I'm quite sure you'll get notified and get it sorted. This update was only to mention that Inrupt's systems are monitoring the TLS certificate and domain expiry for w3id.org. Our alarms will go off if it gets to less than 10 days. (it looks as though Kingsley's buddylist didn't take off) |
If this is meant to last perpetually, shouldn't its dns be prepaid for decades rather than months?
The text was updated successfully, but these errors were encountered: