X.Org Appears To Be Back Up
We now have some official information about X.Org going down, as in the project's one-letter domain.
At last night's X.Org Board of Directors meeting they discussed the X.Org issue. It turns out that their expo.x.org server died and that's what is causing the issues with resolving X.org. Fortunately, the organization was working to retire that server anyhow and they were able to transfer over all of the contents in time.
Unfortunately, as the X.Org Foundation still doesn't have direct control over their domain name, they aren't able to promptly update the DNS information for the new server. Thus they were waiting on the individual no longer involved with X.Org Foundation to update the record, which still boils down to the same issue they had recently in almost losing their domain name but it got renewed on time.
Earlier this week the foundation then resorted to using www.xorg-foundation.org as their temporary address. More details via the X.Org BoD meeting log. However, as of this morning, it appears x.org is back to resolving, so it looks like the issue may now be addressed.
At last night's X.Org Board of Directors meeting they discussed the X.Org issue. It turns out that their expo.x.org server died and that's what is causing the issues with resolving X.org. Fortunately, the organization was working to retire that server anyhow and they were able to transfer over all of the contents in time.
Unfortunately, as the X.Org Foundation still doesn't have direct control over their domain name, they aren't able to promptly update the DNS information for the new server. Thus they were waiting on the individual no longer involved with X.Org Foundation to update the record, which still boils down to the same issue they had recently in almost losing their domain name but it got renewed on time.
Earlier this week the foundation then resorted to using www.xorg-foundation.org as their temporary address. More details via the X.Org BoD meeting log. However, as of this morning, it appears x.org is back to resolving, so it looks like the issue may now be addressed.
10 Comments