Apparently, the LIME DNS servers 220.127.116.11 and 18.104.22.168 were not answering DNS queries from the LIME Broadband network. Thus, LIME's customers could not directly query them.
This was not an Internet outage. It was a DNS outage. The problem was correctable, once known, both at end-user machines or by the Systems Administrator reconfiguring the server and appropriate network equipment. It only affected companies with a specific collection of configuration settings. It is assumed the number of affected companies was large due to the common nature of the configuration.
It would take about three (3) minutes for an end-user to be guided into working around the issue once permitted to modify the network adapter settings.
Typical Static DNS Servers Configured Systems
Traditionally, the above DNS servers were statically configured in:
- The Internet Protocol (IP) properties on on the network adapter of Windows Server machines functioning as DNS servers, Internet Security & Acceleration (ISA) servers, routers.
- Hardware routers.
- Hardware firewalls.
- Microsoft DNS server settings as the Forwarders.
- Distributed to Windows client computers via the DHCP's DNS options.
Concerns Emanating from the Outage
This outage should concern all who were affected in the following ways:
- It lasted in excess of two (2) days! Estimated outage time is a minimum of 53 hours.
- LIME's DNS servers col1.caribsurf.com [22.214.171.124] and col2.caribsurf.com [126.96.36.199] are authoritative name servers for serveral local domains (the correct term to use here is DNS zones). Whilst those servers were resolving DNS queries of international origin (according to LIME and confirmed by testing), they failed to resolve DNS queries from LIME's customers. This meant that if the customers' local caching DNS server was either, 1.) using root hints to resolve queries or 2.) using those afflicted LIME name servers as Forwarders, it would fail to communicate with any of the LIME hosted DNS zones. However, DNS zones not hosted by LIME would have been accessible with the root hints configuration.
- Whilst LIME has provisioned another caching DNS server dns.caribsurf.com [188.8.131.52], it is not an authoritative name server. That is to say it is not secondary to the primary name server for the hosted DNS zones.
- Both of the LIME Barbados' authoritative name servers (primary and secondary), as known to the public, appear to be on the same IP subnet. This makes the network path (or some part of it) a single point of failure, and thus minimizes the engineered redundancy. A failure on the upstream router to these name servers, and as was likely Feb 6th - 8th, 2012 a misconfiguration of the network policy on the upstream router can cause an outage. An outage could affect all DNS operations (authoritative and caching DNS service to the Internet) or authoritative and caching DNS operations only on the LIME network.
- On the issue of public relations by LIME during this critical network outage event, this was as absymal as usual. LIME failed to list this issue as a Service Alert . However, the single day closure of their retail outlets on Feb 10th, 2012 due to a Union meeting was important to list (see image at top of page).
 Service Alerts- LIME Barbados. http://www.time4lime.com/bb/news/service_alerts.jsp