NinerNet Communications™
System Status

Server and System Status

NC036: Update 20

8 May 2026 04:36:31 +0000

Despite long periods of silence on this blog, you should know that NinerNet still exists and still operates.

While we believe that almost all clients have followed our advice and have moved their email hosting, we ourselves have not resurrected our email on our own domain, niner.net. So it may seem that we are dead, when in fact we are actually enjoying a much-deserved holiday after thirty years, and taking time to consider our next move(s).

We will post our plans here or on our primary blog, but for now I will say that our plan is to carry on as before. This means we will continue to provide the following services:

  • Web hosting,
  • DNS hosting,
  • Domain registration and renewal,
  • Dot-zm domain registration and renewal (needed special mentioning because we are a domain registrar), and
  • Consulting.

That is, everything except email hosting. Many hosting companies have given up email hosting; we resisted for the longest time, rejecting the easy way out, but the last straw was when the mail server died on 19 March. It needs to be replaced, if only for our own email, but I refuse to take the easy way out and just outsource everything to Google, Microsoft, or even any other smaller (and well-deserving) companies, like Fastmail. I have never done anything that way, and I’m not ready to start now. Google and Microsoft are very actively in the process of setting up a duopoly, although each would (of course) prefer it was a monopoly, and all of the rules about the handling of email — particularly spam — are dictated from on high by consortia of big email providers that fund the operations of said consortia. Yes, that may sound rather conspiratorial, and it unquestionably is. On a technological level, “conspiracy” is required (it’s called cooperation to come up with the rules necessary to operate in the same environment), but on a competitive level, it obviously isn’t, and in the long term the market will rebel (or react against) the forming duopoly. How that will happen is beyond my ability to forecast, but for now it happens by people like me refusing to play ball.

However, apparently I need to provide a little education, because a lot of clients seem to have the mistaken idea that a “hosting company” is an all-or-nothing monolith, and because NinerNet’s mail server has failed, we have completely failed. That is not and has never been the case with NinerNet. It is true that we operated closer to that model in the beginning (in the mid-90s) when we were starting out, but we haven’t for years. (Our single server being hacked in 2005 taught us that lesson.) There are some hosting companies, believe it or not, that operate everything off of a single server. That means they provide all of the bulleted services above (and email) from a single control panel on a single server. That blows my mind. It concentrates all of their business into one, a single, point of failure. If that was us, we’d be dead today. As it is, our web and DNS servers are still running at 100%, continuing to serve websites and DNS.

This leads us to …

How to configure your domain

Under the assumption — which is true for most of our clients — you are hosting everything (Web, email and DNS) with NinerNet, your first choice is not to transfer your domain registration to a new company and have them manage everything according to their (not your) wishes. Sure, you can, and we’re obviously not going to stop you, but if you want to actively and thoughtfully manage your domain, that’s not necessarily your first and only choice.

The simplest thing to do, when you sign up with Company A, is to have them provide you with the new MX record (or records) they need you to use; you then enter that into your domain’s DNS in the DNS control panel, replacing your old “mx.niner.net” entry. They may require you to enter a few more records — e.g., TXT (SPF) records, etc. — which you also need to enter, probably replacing entries that were used for your NinerNet email. Under our default DNS settings (TTL, or time to live), your new entry will go live in 10 800 seconds, or three hours. As you know, if you understand DNS, this might mean your new settings may take effect immediately, or in three hours, but at most three hours.

That’s it. You don’t have to change or set anything else, unless you move your email hosting again, or your provider requires you to change your settings. In reality, the latter almost never happens.

There are other ways to do things, of course, and if your new host insists on their way or the highway, follow their instructions. Presumably you want to set up a long-term relationship with them, and part of that is taking their advice if it honestly given.

One thing we have noticed, among dot-zm domain holders, is that clients (registrants) do not seem to be aware that only “registered Zambian ISPs” are able to register dot-zm domains. This is not our rule, it is ZICTA’s. So if your South African web designer — who almost invariably doesn’t actually know how the Internet works, but only knows which shade of green looks good on your website — suggests you need to transfer your domain registration to a South African ISP, you can’t, you can only transfer it to one of about a dozen or two Zambian ISPs, and almost without exception those Zambian ISPs provide atrocious customer service. So we suggest you leave your domain registration with NinerNet/Preworx, and manage your DNS through our DNS control panel, or have us change the nameservers to your new host’s preferred nameservers, in which case you will manage your DNS through their control panel.

You have the full ability to fully manage your domain. We have always provided this ability with every domain we host. Remember, it’s your domain as long as you’ve paid to register and renew it, and you’ve kept it updated as your contact and technical information has changed.

Decommissioning of old nameserver

19 October 2019 01:41:05 +0000

We are in the process of decommissioning server NC020. Among other functions, this server is also the machine on which nameserver ns3.niner.net is hosted. Not many clients’ domains are using ns3.niner.net, and of those that are most are registered with and therefore under the control of NinerNet. For this reason we can implement this change without bothering most clients.

However, if you have chosen to register your domain with another domain registrar and we don’t have access to your domain registration, we need to ask you to remove ns3.niner.net from the list of nameservers that are authoritative for your domain. If that is the case we will contact you via email, and point you to this notice to confirm the legitimacy of our request.

This change will not have any effect on your domain and how it, its website and email work. In fact, leaving ns3.niner.net in the list of nameservers authoritative for your domain will cause a slight decrease in performance, which is why we are asking you to remove it.

If you have any questions about this please reply to the email you will receive, or contact NinerNet support. Thank-you.

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.

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: