Network Solutions Name Servers Currently Experiencing DNS Resolution Issues

Dotcom-Monitor has detected that some customers of Network Solutions using name servers such as NS46.WORLDNIC.COM and NS53.WORLDNIC.COM are experiencing intermittent issues.  Occasionally resolution attempts to the servers return improper results by pointing multiple unrelated websites to 141.8.225.31.  To see if this affects your site you can look for this result using the free DNS trace on www.dotcom-tools.com as well as in a…

I{v6Ipv4difference

Test Whether Your Website Works Across IPv6 (Now That ARIN Has Allocated the last IPv4 Address in North America)

ARIN, the American Registry for Internet Numbers is the authority in charge of distributing IP addresses in North America.  ARIN received the IPv4 blocks for North America from the IANA (Internet Assigned Numbers Authority, which is responsible for distribution of IP addresses and maintaining DNS root zones as well as managing the database of top level domains.

Yesterday, on September 24th 2015, ARIN announced that they had issued the final IPv4 address available.  This has several implications to the internet at large:

  • First of all, this does not mean that all IPv4 addresses have been used up, simply that all IPv4 addresses allocated to North America have been distributed to organizations.  For example, the pool of addresses in Europe was depleted three years ago while the AFRINIC (The Internet Numbers Registry for Africa) still has an available pool of addresses.
  • This also does not mean that IPv4 addresses have all been used up in North America.  Organizations that would like to acquire an IPv4 address may still be able to do so through secondary methods. They might either be put on a waitlist for unmet IPv4 addresses or they may purchase the addresses through the IPv4 transfer market.
  • This does mean that any existing restrictions on IPv4 transfer from one organization to another have been lifted.

SQL_Server_Monitoring

SQL Server Monitoring: A Case Study

We recently worked with a client to troubleshoot issues with a SQL Server instance.  The client was running SQL Server 2012 on a Virtual Machine.  The applications running on the SQL Server were running into issues and the client was unsure what the root cause of the issues was.

Initially, we set up web application monitoring with the client to send alerts if the web application began running slower than normal, thus letting us know the next time a problem was encountered.  By setting a timeout threshold for the page load speed, we were able to identify different time periods where the system appeared to have an issue accessing data from the SQL server.  Using the built in alerts, we received emails as soon as an issue was detected.