NinerNet Communications™
System Status

Server and System Status

Update for domains still using the virgodesign.ca nameservers

17 July 2010 22:11:15 +0000

We’ve contacted all clients still using the virgodesign.ca nameservers. While all domains still using these old nameservers are working again, it is imperative that, if your domain is not using ns1.niner.net and ns2.niner.net, you update your domain through your domain registrar to use these nameservers.

Please contact support if you need help with this. Thank-you.

Situation with former VirgoDesign.ca domains partially resolved

17 July 2010 19:59:32 +0000

We’ve found and fixed the cause of the problem with the domains that are still using the ns1.virgodesign.ca and ns2.virgodesign.ca nameservers. However, due to DNS caching, most of these domains will still be down to most people who have tried to load them in the last 24 hours or so. We’re continuing to work on this and will post more here within the next two hours.

Some former VirgoDesign.ca domains down

17 July 2010 19:13:23 +0000

Domains formerly hosted by VirgoDesign.ca who had not changed their nameservers in response to our email of about six weeks ago are down at this moment. We’re looking into the cause and will report back here within the hour.

Relay server back online

15 July 2010 02:13:28 +0000

The relay server is back online. We have blocked the source of the spam and are continuing our investigation.

Just to be clear, server NC020 has been online at all times. Only the mail server was taken offline. It was taken offline at 01:32 UTC and put back online at 02:08 UTC.

If you have any questions or concerns about this incident, please contact support. Thank-you.

Relay server offline

15 July 2010 01:37:41 +0000

Server NC020 (widely known as the the relay server) has been taken offline while we investigate reports of spam being sent through the server. We will post an update within the hour.

Relay server configuration change

13 July 2010 08:33:56 +0000

We’ve made some configuration changes to the relay server to make it more secure. If you are using the relay server and there was a chance that these changes might have affected you, you would have been contacted by your service provider through which you have access to the relay server.

If you are trying to use the relay server and find that you are getting “relaying denied” error messages, please contact your service provider to ensure that they have included your IP address in the whitelist.

Problems with delivery to kcm.co.zm domain

12 July 2010 11:37:39 +0000

We have had ongoing problems with delivery to the kcm.co.zm (Konkola Copper Mines) domain since time immemorial. Konkola appears to host their own mail server over a very slow Zamtel connection. This means their connection appears to be extremely limited in what it can handle. While sporadic small emails without attachments generally go through within a day or two (yes, that’s days, not seconds, minutes or even hours), larger emails with attachments either stall or take so long to deliver that they affect delivery of other emails.

That is the case today. Three large emails from two clients to over one hundred kcm.co.zm email addresses effectively plugged up the mail server while it waited for the kcm.co.zm mail server to accept delivery, preventing delivery of hundreds of other emails. We had no choice but to delete these emails. As soon as we did, the backlog of several hundred emails that had built up over the course of about an hour were successfully delivered within minutes.

If you email people on the kcm.co.zm domain, please consider reducing the sizes of attachments and reducing the number of kcm.co.zm email addresses you include in your distribution lists. You might also want to point them to this post so that they might become aware of the problem and therefore do something to fix it.

Email to Microlink delayed

5 July 2010 18:18:22 +0000

It appears that email to microlink.zm email addresses is experiencing delays at the moment. We have quite a few emails queued on the server at the moment going back to 3 July. It seems that the Microlink mail server is currently down.

NinerNet home page

Systems at a Glance:


Loc.SystemStatusPing
Server NC023, London, United Kingdom (Relay server), INTERNAL.NC023InternalUp?
Server NC028, Vancouver, Canada (Monitoring server), INTERNAL.NC028InternalUp?
Server NC031, New York, United States of America (Web server), INTERNAL.NC031InternalUp?
Server NC033, Toronto, Canada (Primary nameserver), OPERATIONAL.NC033OperationalUp?
Server NC034, Lusaka, Zambia (Phone server), INTERNAL.NC034InternalUp?
Server NC035, Sydney, Australia (Secondary nameserver), OPERATIONAL.NC035OperationalUp?
Server NC036, Amsterdam, Netherlands (Mail server), OPERATIONAL.NC036OperationalUp?
Server NC040, Toronto, Canada (Web server), INTERNAL.NC040InternalUp?
Server NC041, New York, United States of America (Web server), OPERATIONAL.NC041OperationalUp?
Server NC042, Seattle, United States of America (Status website), OPERATIONAL.NC042OperationalUp?

Subscriptions:

RSS icon. RSS

Twitter icon. Twitter

Search:

 

Recent Posts:

Archives:

Categories:

Links

Tags:

.co.zm domains .com.zm domains .zam.co domains back-up bounce messages browser warnings connection issues control panel database dns dos attack dot-zm domains down time email email delivery error messages ftp hardware imap mail mailing lists mail relay mail server microsoft migration nameservers network networking performance php phplist pop reboot shaw shaw communications inc. smtp spam spamassassin ssl ssl certificate tls tls certificate viruses webmail web server

Resources:

On NinerNet: