NinerNet Communications™
System Status

Server and System Status

Issues with some .com.zm domains explained

16 August 2010 10:18:52 +0000

It turns out that this is not a technical problem, but a billing issue. When the reports started to roll in we naturally suspected a technical problem, but then we realised that not all .com.zm domains were down. We contacted Coppernet about the domains that are down, and were informed that some of these clients have apparently not paid for their domain registrations since as far back as 2004! As a result, their sleepy accounts receivable department woke up for the first time in the better part of a decade, and cancelled these domains today.

Of course, this is clearly a Coppernet billing issue, not delinquency on the part of the clients, and this much was admitted by the customer service manager at Coppernet. However, until the millions of kwachas owing on these domains have been paid to Coppernet by the domain owners, these domains will remain offline.

This is a very interesting turn of events, because we have very recently started to offer an alternative Zambian top-level domain (TLD) for those clients who would like to use a domain that identifies them as Zambian, but who are sick and tired of the problems from both Zamnet and Coppernet with .co.zm, .com.zm and other dot-zm domains. The alternative TLD is .zam.co — i.e., you can register yourname.zam.co. Because we haven’t officially launched it yet we don’t have a website developed yet. However, you may check on the availability of and order .zam.co domains by contacting support, and it will be up and running immediately.

Pricing for .zam.co domains is a lot more palatable at only US$12 per annum too.

Problems with .com.zm domains

16 August 2010 08:26:17 +0000

We are receiving reports that multiple .com.zm domains are down today. This problem is traceable to Coppernet, who are ultimately responsible for .com.zm domains. All of our systems are operating normally.

We’re looking into this and will post updates here as we learn what is going on.

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.

Server NC020 IP address removed from Spamhaus PBL

15 November 2009 08:54:33 +0000

The IP address of server NC020 has been removed from the Spamhaus Policy Block List. All email issues are resolved, and server configurations will return to normal.

If you have any questions concerning this incident, please contact support. We appreciate your patience.

Temporary resolution of Spamhaus PBL issue

15 November 2009 03:23:58 +0000

While the IP address of server NC020 is still in the Spamhaus PBL, we have made a number of configuration changes to all of our mail servers which address three of the four issues mentioned in our original post on this matter:

  • All email sent through server NC020 (known as “the relay server” to those of our clients who use it as such) is now routed to server NC018 before finally being delivered to destination mail servers. This means that email will no longer be delayed or rejected by destination mail servers.
  • All email is (and has been since the first post on this matter) flowing from server NC020 to NC018.
  • We are once again using the PBL to block spam on server NC018, so spam defences are back at 100%. We have simply exempted server NC020 from this block.
  • Mail to domains using NC020 as a secondary mail server is still a concern. We’ll be monitoring this and reacting as necessary.

Server NC020 is also used for some custom mailing lists. Email sent to these lists will also be handled as detailed in the first bullet point above.

We still anticipate that the IP address of server NC020 will be removed from the PBL at some point, at which point the configurations of all mail servers will revert to what they were before this incident. Further details will be posted here as necessary.

Update on server NC020 in the Spamhaus PBL

14 November 2009 20:42:44 +0000

Server NC020’s IP address is still in the Spamhaus PBL. We have been unable to make any progress on having it removed yet. This may be because it’s the weekend, or it may be that we’re just one of thousands of companies that have been affected by this action, and so we just have to be patient. In the meantime, we are trying to have our case looked at sooner rather than later.

We’re also going to take steps to have mail from server NC020 routed through NC018 as a temporary measure. We will post here again when this has been put into place.

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), SHUT DOWN.NC036Shut downUp?
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: