Bristol indymedia site under state attack again as ISP served court order by UK police 02:11 Sep 02 2 comments Blog Feeds
Public InquiryInterested in maladministration. Estd. 2005RTEs Sarah McInerney ? Fianna Fail supporter? Anthony Joe Duffy is dishonest and untrustworthy Anthony Robert Watt complaint: Time for decision by SIPO Anthony RTE in breach of its own editorial principles Anthony Waiting for SIPO Anthony
Human Rights in IrelandPromoting Human Rights in Ireland
Lockdown Skeptics
The War on Fertiliser Comes to Britain Wed Nov 13, 2024 09:00 | Chris Morrison
Starmer and Miliband ?Show Leadership? at COP29 But No One is Following Wed Nov 13, 2024 07:00 | Ben Pile
News Round-Up Wed Nov 13, 2024 01:01 | Richard Eldred
Experts Slam the World Health Organisation?s Advice to Set Central Heating at a Chilly 18°C Tue Nov 12, 2024 20:08 | Will Jones
Labour Should ?Do to Farmers What Thatcher Did to Miners?, Tony Blair Aide Says Tue Nov 12, 2024 17:30 | Will Jones
Voltaire NetworkVoltaire, international editionTrump's re-election redistributes the cards , by Thierry Meyssan Wed Nov 13, 2024 04:05 | en Voltaire, International Newsletter N°107 Sat Nov 09, 2024 14:52 | en Russia's view of the situation in Ukraine Sat Nov 09, 2024 14:34 | en The Voltaire Network website heavily attacked! Thu Nov 07, 2024 04:31 | en Israeli-Iranian auctions mask the reorganization of alliances in the Middle East... Tue Nov 05, 2024 06:52 | en |
Indymedia Server Outages
national |
indymedia ireland |
news report
Tuesday March 27, 2007 20:01 by Chekov - 1 of IMC
In the last few days, some users will have experienced trouble accessing the indymedia website. This was due to a problem with the domain's DNS configuration - the system which turns domain names (indymedia.ie) into computer addresses. We believe that we have now fixed the problem and we apologise for the service interruptions. Technically, what happened was that our parent nameserver lacked a glue entry for our domain nameservers. This did not pose a problem as our nameservers were using an old reverse DNS name, which refered to a different domain. However, over the weekend, this DNS entry expired and, although we changed our DNS entries to the new hostname of our servers, we lacked a glue entry and so DNS servers were incapable of resolving the circular dependencies (the domain nameservers were on the domain itself). |
View Comments Titles Only
save preference
Comments (8 of 8)
Jump To Comment: 1 2 3 4 5 6 7 8still on GMT
back-dated too.
I was sorry about the glue spilt into your computers by the altar servers.
Still I imagine the arms caches are now all emptied what with the peace process and all. I find a handy tip is to use lemon juice on the net curtains and stack dead rams on by the fireplace wall, provided they don't overflow.
Hope that heps
Alan
Oh yea I know how painful DNS can be. Finding out what was wrong must have been a very frustrating effort.
Thanks to the person who gave up their weekend to solve that one.
I never noticed. doesn't matter - nothing happened anyway. Well done you techno people. Yet again you've proved you're up to glue, filling out forms &ensuring the problem goes away & never comes back. Will we ever be getting that freephone help-line now?
I've just spent this afternoon surfing and much was my frustration when, for much of the afternoon, I couldn't access Indymedia.ie. Towards the end of the session I changed browser (from Firefox to Netscape) out of a sense of curiosity and then, mirabile dictu, I could access Indymedia first go and no delay! I wonder are there browser-specific problems that the IMC are aware of (here I have to add that I sometimes have had trouble in the past year accessing Indymedia.ie via Firefox), and whether these are fixable or not. I'd hate to think that the Indymedia-using community would have to resort to using such work-arounds permanently.
I don't think the problem is related to what browser you are using. It sounds like firefox has simply cached the old DNS results for indymedia.ie (browsers do this sort of thing) and it will eventually work again. You could try to select "clear private data" from the firefox tools menu and select "cache" from the box.
Let us know if you still have a problem after trying that.
Followed what you said Chekov works like a dream now. Thanks.