---
title: "Update on status of nameservers"
type: "post"
post_id: "14797"
slug: "update-on-status-of-nameservers"
canonical: "https://easydns.com/blog/2006/11/01/update-on-status-of-nameservers/"
markdown_url: "https://easydns.com/blog/2006/11/01/update-on-status-of-nameservers.md"
json_url: "https://easydns.com/blog/2006/11/01/update-on-status-of-nameservers.json"
txt_url: "https://easydns.com/blog/2006/11/01/update-on-status-of-nameservers.txt"
published: "2006-11-01T04:39:21+00:00"
modified: "2024-11-13T18:14:26+00:00"
author: "easydnssupport"
categories:
  - "status"
tags:
site_name: "easyDNS"
publisher: ""
language: "en-US"
generator: "easyPress Markdown"
generator_version: "1.0.3"
---
For the most part, things have levelled out on the DOS attack. Again, I note that most of the pain was felt by members using third party registrars who didn’t have the full 6 nameservers in their DNS delegation.

Status as follows, all servers are functioning normally except certain parts of the net may have limited visibility to one of the following:

**n1.easydns.com** – up, but being null routed by shaw.ca, people on shaw or transiting across shaw can’t see ns1

**remote2.easydns.com** – up but being null routed by cogent, we also changed the IP address of remote2 during the attack, it was switched from 205.210.42.20 to 205.210.42.19, but will respond on either IP.

**ns6.easydns.org** – null routed by rackspace and now renumbered onto the prolexic network temporarily.

We expect the null routes to begin clearing over the course of the day wednesday.

**ns2.easydns.com remote1.easydns.com** and **ns3.easydns.org** are all up and functional at the time of writing.

Many thanks to our members for being patient and commenting constructively.