<?xml version="1.0" encoding="ISO-8859-1"?>
<!-- generator="FeedCreator 1.7.2" -->
<rss version="2.0">
    <channel>
        <title>DNS Park System Status</title>
        <description>Up to date status information for DNS Park</description>
        <link>http://status.dnspark.net/</link>
        <lastBuildDate>Fri, 09 May 2008 08:51:26 +0100</lastBuildDate>
        <generator>FeedCreator 1.7.2</generator>
        <image>
            <url>http://www.dnspark.com/images/dnspark.png</url>
            <title>DNS Park logo</title>
            <link>http://www.dnspark.net/</link>
            <description>DNS Park system status update for all important events. Feed mirrored at http://status.dnspark.com/ and http://status.dnspark.net/.</description>
        </image>
        <copyright>Copyright 2007</copyright>
        <item>
            <title>Mail Pathfinder Upgrades</title>
            <link>http://status.dnspark.net/#281</link>
            <description>MAIL PATHFINDER CUSTOMERS PLEASE READ&lt;br /&gt;
All customers who have firewalled off their mailservers to Mail Pathfinders' servers need to add the following hostnames/IPs to their allow lists as soon as possible.  We will be adding these servers to the Mail Pathfinder pool soon to increase capacity.&lt;br /&gt;
&lt;br /&gt;
wa140-pf1.mx.dnspark.net  67.228.192.140&lt;br /&gt;
wa141-pf1.mx.dnspark.net  67.228.192.141</description>
            <pubDate>Fri, 11 Apr 2008 20:00:00 +0100</pubDate>
        </item>
        <item>
            <title>Mailpathfinder update</title>
            <link>http://status.dnspark.net/#279</link>
            <description>We are currently working to resolve mail delays through Mail Pathfinder.&lt;br /&gt;
&lt;br /&gt;
Our engineers are actively monitoring the mail queues and taking specific action where appropriate to remove bottlenecks.&lt;br /&gt;
&lt;br /&gt;
Additionally, we will be adding capacity to the Mail Pathfinder system to prevent further delays from occurring.  We will update you via an Announcement, the Status Page, and an email of the new hostnames/IPs.</description>
            <pubDate>Fri, 11 Apr 2008 17:23:00 +0100</pubDate>
        </item>
        <item>
            <title>System Upgrade Complete</title>
            <link>http://status.dnspark.net/#278</link>
            <description>Last night we introduced a major upgrade to our back-end systems that will result in quicker updates to our nameservers, more reliable dynamic updates and also set the stage for several new features that will be released in the future.&lt;br /&gt;
There were some minor issues to deal with resulting from the upgrade, but they have been resolved now and all systems are functioning as expected.</description>
            <pubDate>Tue, 08 Apr 2008 19:48:00 +0100</pubDate>
        </item>
        <item>
            <title>System Upgrade Issues</title>
            <link>http://status.dnspark.net/#277</link>
            <description>We're currently experiencing some issues from a network upgrade last night that are randomly affecting some domains on some of our nameservers.  Our staff is working to resolve the situation as soon as possible.  We will post back here when we have more information.</description>
            <pubDate>Tue, 08 Apr 2008 16:00:00 +0100</pubDate>
        </item>
        <item>
            <title>Mail Pathfinder Service Fully Restored</title>
            <link>http://status.dnspark.net/#274</link>
            <description>Yesterday, we identified an issue with one of our Mail Pathfinder servers and removed it from the server pool while our staff investigated and corrected the issue.  That issue has been addressed and the server is back in the production pool, bringing Mail Pathfinder back to full capacity.</description>
            <pubDate>Tue, 04 Mar 2008 07:00:00 +0100</pubDate>
        </item>
        <item>
            <title>dnspark.net service restored</title>
            <link>http://status.dnspark.net/#272</link>
            <description>Service to dnspark.net has been restored.  Again, we apologize for the inconvenience.</description>
            <pubDate>Sun, 24 Feb 2008 22:45:00 +0100</pubDate>
        </item>
        <item>
            <title>dnspark.net</title>
            <link>http://status.dnspark.net/#270</link>
            <description>Our engineers are currently working on an issue with dnspark.net, so accessibility may be intermittent while we get it resolved.  We regret this inconvenience and are working to restore functionality as quickly as possible.</description>
            <pubDate>Sun, 24 Feb 2008 19:04:00 +0100</pubDate>
        </item>
        <item>
            <title>All Systems Back Online</title>
            <link>http://status.dnspark.net/#269</link>
            <description>All systems are functioning normally.  We apologize for the inconvenience.  Please open a Support Ticket if you experience any issues specific to your account or domains.</description>
            <pubDate>Fri, 22 Feb 2008 15:45:00 +0100</pubDate>
        </item>
        <item>
            <title>System Maintenance Update</title>
            <link>http://status.dnspark.net/#267</link>
            <description>We are continuing to work on resolving some issues related to last night's maintenance window.  If you are having problems updating records in your zone, please check back here periodically for updates.  We apologize for any inconvenience.</description>
            <pubDate>Fri, 22 Feb 2008 13:00:00 +0100</pubDate>
        </item>
        <item>
            <title>System Maintenance</title>
            <link>http://status.dnspark.net/#266</link>
            <description>We will be performing some maintenance that will require us to set the system in a read-only mode. You will be able to view your records, but not modify them. The maintenance should take approximately one hour to complete.&lt;br /&gt;
&lt;br /&gt;
UPDATE: Maintenance was completed at 20:00 and changes can be made to your records again.</description>
            <pubDate>Fri, 22 Feb 2008 01:39:32 +0100</pubDate>
        </item>
        <item>
            <title>DNS-O-Matic</title>
            <link>http://status.dnspark.net/#264</link>
            <description>If you use &lt;a href=&quot;http://www.opendns.com&quot;&gt;OpenDNS&lt;/a&gt; for your recursive DNS needs, the new &lt;a href=&quot;http://www.dnsomatic.com&quot;&gt;DNS-O-Matic&lt;/a&gt; has just been released to help you dynamically update your information at one location. By using one of many software solutions (&lt;a href=&quot;https://www.dnsomatic.com/wiki/software&quot;&gt;https://www.dnsomatic.com/wiki/software&lt;/a&gt;) you simply make one update to the DNS-O-Matic and it will update your dynamic DNS hosts here at DNS Park. In your OpenDNS settings make sure you specify your dynamic DNS username and password and not your normal login information. We hope you find this a useful addition just as the &lt;a href=&quot;http://www.opendns.com&quot;&gt;OpenDNS&lt;/a&gt; folks do.</description>
            <pubDate>Mon, 03 Dec 2007 15:39:18 +0100</pubDate>
        </item>
        <item>
            <title>ns1.dnspark.net ONLINE</title>
            <link>http://status.dnspark.net/#262</link>
            <description>ns1.dnspark.net is back online.  We are working with the datacenter staff to determine the cause of the network outage and reduce the probability of it occurring again.  Thanks for your patience.</description>
            <pubDate>Sat, 20 Oct 2007 15:11:00 +0100</pubDate>
        </item>
        <item>
            <title>ns1.dnspark.net Unavailable</title>
            <link>http://status.dnspark.net/#260</link>
            <description>At approximately 7:52EDT, ns1.dnspark.net became unavailable.  Our monitoring systems detected the event immediately and alarmed.  We are working with our datacenter staff to restore connectivity as soon as possible.  All testing indicates the server itself is online, but there is a network routing problem preventing the public internet from reaching the server.</description>
            <pubDate>Sat, 20 Oct 2007 13:52:00 +0100</pubDate>
        </item>
        <item>
            <title>Control Center Updates</title>
            <link>http://status.dnspark.net/#259</link>
            <description>Several new changes have gone into the control center. The largest of which is a revamped shopping cart. Many other small changes have been put in as well fixing various bugs or improving application security. Please contact support if you have any trouble.&lt;br /&gt;
&lt;br /&gt;
Additional changes are on the horizon including many new resource record types that have been requested. Stay tuned.</description>
            <pubDate>Fri, 28 Sep 2007 03:15:31 +0100</pubDate>
        </item>
        <item>
            <title>NS3 Issue Resolved</title>
            <link>http://status.dnspark.net/#257</link>
            <description>NS3 has been restored and is currently advertising.  We will be monitoring the server closely for the next 24-48 hours to ensure it is running optimally.</description>
            <pubDate>Wed, 29 Aug 2007 07:19:00 +0100</pubDate>
        </item>
        <item>
            <title>NS3 Unavailable</title>
            <link>http://status.dnspark.net/#255</link>
            <description>ns3.dnspark.net is currently unavailable and our Support Staff is working with the datacenter to determine the nature of the issue and to bring the server back online as soon as possible&lt;br /&gt;
&lt;br /&gt;
We will post back when we have more information.</description>
            <pubDate>Wed, 29 Aug 2007 03:44:00 +0100</pubDate>
        </item>
        <item>
            <title>Merchant Gateway Back Online</title>
            <link>http://status.dnspark.net/#253</link>
            <description>Our Merchant Gateway is back online and credit card orders can be processed without issue.</description>
            <pubDate>Tue, 28 Aug 2007 03:33:00 +0100</pubDate>
        </item>
        <item>
            <title>Merchant Provider Outage</title>
            <link>http://status.dnspark.net/#251</link>
            <description>The Merchant Provider that DNS Park uses for credit card transactions is currently experiencing a network outage.&lt;br /&gt;
&lt;br /&gt;
We are unable to process credit card purchases due to this outage and are working with our provider to restore the service as soon as possible.&lt;br /&gt;
&lt;br /&gt;
Please open a Support Ticket if this outage inhibits you from renewing expiring services.  Otherwise, we will update this announcement when the problem is resolved and you can proceed with purchases then.</description>
            <pubDate>Mon, 27 Aug 2007 22:49:00 +0100</pubDate>
        </item>
        <item>
            <title>NS2.DNSPARK.NET Update</title>
            <link>http://status.dnspark.net/#249</link>
            <description>ns2.dnspark.net is back online with new hardware.</description>
            <pubDate>Mon, 30 Jul 2007 20:22:34 +0100</pubDate>
        </item>
        <item>
            <title>NS2.DNSPARK.NET Maintenance</title>
            <link>http://status.dnspark.net/#247</link>
            <description>ns2.dnspark.net is down temporarily due to a hardware failure.  The system is being rebuilt and should be available shortly.</description>
            <pubDate>Mon, 30 Jul 2007 16:20:00 +0100</pubDate>
        </item>
        <item>
            <title>Nameserver Upgrades Complete</title>
            <link>http://status.dnspark.net/#245</link>
            <description>The scheduled upgrades for ns2.dnspark.net and ns4.dnspark.net are complete. Please let us know if you have any questions or concerns.&lt;br /&gt;
&lt;br /&gt;
As a reminder:&lt;br /&gt;
The old ns2.dnspark.net will be taken offline July 20, 2007. &lt;br /&gt;
The old ns4.dnspark.net will be taken offline July 27, 2007.</description>
            <pubDate>Sat, 14 Jul 2007 05:23:35 +0100</pubDate>
        </item>
        <item>
            <title>Nameserver Upgrades</title>
            <link>http://status.dnspark.net/#243</link>
            <description>&lt;b&gt;NOTICE&lt;/b&gt;:If you have not been receiving this information via email, please ensure your spam filters are allowing messages from @dnspark.com. This is simply a recap of messages previously sent.&lt;br /&gt;
&lt;br /&gt;
ns2.dnspark.net upgrades and ns4.dnspark.net upgrades&lt;br /&gt;
&lt;br /&gt;
ns2.dnspark.net and ns4.dnspark.net are in the process of being upgrade. &lt;br /&gt;
As part of the upgrades in network infrastructure and system hardware &lt;br /&gt;
we are changing IP addresses for these hosts. Most customers will not be &lt;br /&gt;
affected in any way by these changes. The changes will happen seamlessly &lt;br /&gt;
without service interruption.&lt;br /&gt;
&lt;br /&gt;
The new servers are online and ready to answer queries. These systems&lt;br /&gt;
have an identical configurations to the current systems with the &lt;br /&gt;
exception of IP addressing.&lt;br /&gt;
&lt;br /&gt;
Customers with secondary nameservers that perform zone transfers from&lt;br /&gt;
ns2.dnspark.net should note the new IP address. The new IP address of&lt;br /&gt;
ns2.dnspark.net is 83.170.90.100. Please update your configuration to &lt;br /&gt;
reflect the new IP address.&lt;br /&gt;
&lt;br /&gt;
Customers with secondary nameservers that perform zone transfers from&lt;br /&gt;
ns4.dnspark.net should note the new IP address. The new IP address of&lt;br /&gt;
ns4.dnspark.net is 209.160.66.110. Please update your configuration to &lt;br /&gt;
reflect the new IP address.&lt;br /&gt;
&lt;br /&gt;
DNS Rescue customers will need to update configuration if you have&lt;br /&gt;
IP based access controls setup for zone transfers, or have firewall rules&lt;br /&gt;
setup to restrict zone transfers from a limited number of addresses. Zone&lt;br /&gt;
zone transfers will take place from 83.170.89.43 and 209.160.65.32. Please &lt;br /&gt;
add these addresses to your ACLs and firewall rules where appropriate. &lt;br /&gt;
If you rely on TSIG security to restrict zone transfers you should not need &lt;br /&gt;
to make any changes.&lt;br /&gt;
&lt;br /&gt;
Customers with branded DNS hosting services that are paid and up to date, &lt;br /&gt;
please contact us for new IP address assignments. You will be required to &lt;br /&gt;
update your host records for the branded nameserver IP and update your &lt;br /&gt;
domain registrars information.  Please contact us soon.&lt;br /&gt;
&lt;br /&gt;
All customers should have any configurations updated no later than July 6, 2007.&lt;br /&gt;
&lt;br /&gt;
The official cut-over time for ns2.dnspark.net is &lt;br /&gt;
July 6, 2007 11:00pm-02:00am CDT (GMT-5).  &lt;br /&gt;
The current ns2.dnspark.net will be taken offline July 20, 2007. &lt;br /&gt;
&lt;br /&gt;
The official cut-over time for ns4.dnspark.net is&lt;br /&gt;
July 13, 2007 11:00pm-02:00am CDT (GMT-5).  &lt;br /&gt;
The current ns4.dnspark.net will be taken offline July 27, 2007. &lt;br /&gt;
</description>
            <pubDate>Thu, 05 Jul 2007 17:57:21 +0100</pubDate>
        </item>
        <item>
            <title>Mail Pathfinder Status - Normal</title>
            <link>http://status.dnspark.net/#241</link>
            <description>All Mail Pathfinder services have returned to normal.</description>
            <pubDate>Tue, 19 Jun 2007 23:00:00 +0100</pubDate>
        </item>
        <item>
            <title>Mail Pathfinder Delays</title>
            <link>http://status.dnspark.net/#239</link>
            <description>One of our Mail Pathfinder servers was causing delays in mail delivery, but we have identified the problem and removed that server from production until it is resolved.</description>
            <pubDate>Tue, 19 Jun 2007 17:44:00 +0100</pubDate>
        </item>
        <item>
            <title>NS1.DNSPARK.NET Online</title>
            <link>http://status.dnspark.net/#237</link>
            <description>Power has been restored to the system and it is fully operational again.</description>
            <pubDate>Wed, 13 Jun 2007 22:48:55 +0100</pubDate>
        </item>
        <item>
            <title>NS1.DNSPARK.NET Unavailable</title>
            <link>http://status.dnspark.net/#235</link>
            <description>At approximately 15:00, ns1.dnspark.net became unavailable.  Our monitoring systems detected the event immediately and alarmed.  We have been working with the Datacenter staff to determine the source of the problem.  The server itself is functioning, but we've been told there was a massive hail storm that took out a portion of the power to the Datacenter, and apparently the back-up power systems have failed as well.  They are working to restore power and connectivity.  We don't believe Datacenters should have power problems, so rest assured, when the problem is resolved we will be escalating this issue as far as we need to in order to ensure this does not happen again.</description>
            <pubDate>Wed, 13 Jun 2007 21:58:00 +0100</pubDate>
        </item>
        <item>
            <title>Services Restored</title>
            <link>http://status.dnspark.net/#233</link>
            <description>As of approximately 04:30 CDT (09:30 GMT) services were restored for ns4.dnspark.net. All services are fully operational at this time. Thank you for your patience as we work to further improve our response capabilities to these types of attacks.</description>
            <pubDate>Sat, 02 Jun 2007 16:57:40 +0100</pubDate>
        </item>
        <item>
            <title>DNS Services Update</title>
            <link>http://status.dnspark.net/#229</link>
            <description>We have been working internally and with our upstream providers to mitigate the DDoS attack we've been experiencing.  Throughout the day, we've taken various steps and at this time connectivity has been restored to NS1, NS2, NS3, &amp; NS5.  We are working with the datacenter that NS4 is located in to bring that back as soon as possible.&lt;br /&gt;
&lt;br /&gt;
Additionally, we've already begun reviews internally to determine actions we need to take to minimize the probability of an event like this occurring in the future.  Our discussions have ranged from increased reliability from our providers, to internal policies, to more effective communications with you, our customer, during events like this.&lt;br /&gt;
&lt;br /&gt;
Please continue to check this page for current status updates.</description>
            <pubDate>Fri, 01 Jun 2007 18:58:00 +0100</pubDate>
        </item>
        <item>
            <title>DDoS Update</title>
            <link>http://status.dnspark.net/#225</link>
            <description>Earlier this morning, our remaining servers came under attack as well, in addition to new IPs we began routing through yesterday.  Our staff is continuing work with our own systems and our upstream providers to get all systems back online as soon as absolutely possible.  NS5 is currently responding to queries and we expect to have NS3 &amp; NS1 online soon.  Rest assured, we are doing everything we can to keep your zones available.</description>
            <pubDate>Fri, 01 Jun 2007 13:33:00 +0100</pubDate>
        </item>
        <item>
            <title>The Good, The Bad, and The Ugly</title>
            <link>http://status.dnspark.net/#221</link>
            <description>The Good: ns3.dnspark.net is fully operational.&lt;br /&gt;
&lt;br /&gt;
The Bad: ns2.dnspark.net and ns5.dnspark.net are still degraded by the ongoing attack.&lt;br /&gt;
&lt;br /&gt;
The Ugly: A new DDoS attack has begun on the web guiding service. Our systems saw some slight delays initially, but are fully operational now that we've engaged all of our anti-ddos hardware against the attack. When it rains, it pours.</description>
            <pubDate>Fri, 01 Jun 2007 00:40:57 +0100</pubDate>
        </item>
        <item>
            <title>UPDATE: DDoS Attack on NS2, NS3, &amp; NS5</title>
            <link>http://status.dnspark.net/#217</link>
            <description>The distributed denial of service (DDoS) attack is still in progress. We have rerouted traffic for each of the nameservers to backup locations to resume service while the attack continues. There may be some continued delays for the next few hours, but services should be operational.</description>
            <pubDate>Thu, 31 May 2007 14:56:07 +0100</pubDate>
        </item>
        <item>
            <title>ALERT: DDoS Attack on NS2, NS3, &amp; NS5</title>
            <link>http://status.dnspark.net/#213</link>
            <description>At this time we are the victim of a distributed denial of service attack. ns2.dnspark.net, ns3.dnspark.net, and ns5.dnspark.net are being targeted. If you are experiencing problems and your domain is on one or more of these nameservers, please open a ticket and we will work with you to get your domain back online as quickly as we can.  To help use serve you most efficiently, please include the specific domain(s) the ticket pertains to.</description>
            <pubDate>Thu, 31 May 2007 09:30:00 +0100</pubDate>
        </item>
        <item>
            <title>www.dnspark.net unavailable</title>
            <link>http://status.dnspark.net/#209</link>
            <description>www.dnspark.net was unavailable for a period early this morning due disk problems on the shared storage device. The problems were cleared up and everything is back online.</description>
            <pubDate>Fri, 06 Apr 2007 13:00:15 +0100</pubDate>
        </item>
        <item>
            <title>DoS attack against Web Guiding Service</title>
            <link>http://status.dnspark.net/#205</link>
            <description>One of our Web Guiding servers has become a target of a DoS attack. We are in the process of rerouting all Web Guiding customers to another of our Web Guiding servers.</description>
            <pubDate>Mon, 12 Feb 2007 18:10:00 +0100</pubDate>
        </item>
        <item>
            <title>Dynamic DNS Changes</title>
            <link>http://status.dnspark.net/#201</link>
            <description>In response to customer feedback and after going through an internal audit for security weaknesses, we have taken multiple steps to better secure our system from outside attacks. &lt;br /&gt;
&lt;br /&gt;
As a result, we will no longer allow your login user to control dynamic DNS updates. All users wanting to dynamically update hosts must create one or more new dynamic DNS user(s). Dynamic updates will fail until you have created at least one dynamic DNS user in your account. You can create new DDNS users from directly in your account at &lt;a href=&quot;https://www.dnspark.net/dynamicusers.php&quot;&gt;https://www.dnspark.net/dynamicusers.php&lt;/a&gt;&lt;br /&gt;
&lt;br /&gt;
We apologize for any inconvenience this may cause, but we strongly believe this will further strengthen the security of your account to prevent unauthorized access and provide you with additional flexibility to use multiple usernames and passwords for dynamic DNS update clients.</description>
            <pubDate>Wed, 10 Jan 2007 00:19:00 +0100</pubDate>
        </item>
        <item>
            <title>All Services Fully Restored after DDOS Attack</title>
            <link>http://status.dnspark.net/#189</link>
            <description>We already utilize multiple anti-ddos hardware technologies upstream at several facilities to help us mitigate these types of attacks and we were not able to stop the most recent attacks effectively. Our upstream providers could only provide limited filtering due to the distributed nature of the attacks. All of the facilities we co-locate equipment in and/or lease equipment from are fully gigabit connected and bandwidth is generally not the bottleneck but rather the rate at which our servers can process the information.&lt;br /&gt;
&lt;br /&gt;
We are looking at other technologies to further globally distribute our systems to limit any failures to geographic locales while allowing other areas to remain fully operational. Additionally we are reviewing our existing hardware capacity to determine if we can handle loads many times our normal operating loads.&lt;br /&gt;
&lt;br /&gt;
In the short term we have updated all those affected to utilize all 5 of our nameservers. The attacks were centered around only 3 of the 5 this time around. Our customers using the two unaffected nameservers saw a slight degredation in performance but not a complete outage. By adding the additional nameservers to all of our customers we should be able to provide a better footprint of servers for everyone while we add additional technologies on the backend in preparation for future attacks.&lt;br /&gt;
&lt;br /&gt;
If you are an existing customer and wish to have your domain listed on all of our nameservers, please contact support and we can get the remaining nameservers added.&lt;br /&gt;
&lt;br /&gt;
Please let us know if you have any questions and we'll be glad to answer them for you.</description>
            <pubDate>Fri, 01 Dec 2006 05:21:41 +0100</pubDate>
        </item>
        <item>
            <title>ns1.dnspark.net back online</title>
            <link>http://status.dnspark.net/#185</link>
            <description>ns1.dnspark.net is back online though still under attack. We have noticed some delays in response but we expect to have that cleared up shortly.</description>
            <pubDate>Wed, 29 Nov 2006 14:55:34 +0100</pubDate>
        </item>
        <item>
            <title>ns3.dnspark.net back online</title>
            <link>http://status.dnspark.net/#181</link>
            <description>ns3.dnspark.net is back online and fully operational. We are still working on ns1.dnspark.net to resolve the final issues.</description>
            <pubDate>Tue, 28 Nov 2006 04:12:32 +0100</pubDate>
        </item>
        <item>
            <title>DDOS Update</title>
            <link>http://status.dnspark.net/#177</link>
            <description>As an update, we have been continually working with our providers to contain the distributed denial of service attack. The ongoing attack is extremely large and from thousands of sources. ns1.dnspark.net and ns3.dnspark.net are still affected by the attack. If you are experiencing any delays, please feel free to contact us and we will be glad to help. Please include the specific domain(s) the problem pertains to so we can efficiently help each of you.</description>
            <pubDate>Sun, 26 Nov 2006 23:13:30 +0100</pubDate>
        </item>
        <item>
            <title>ns5.dnspark.net back online</title>
            <link>http://status.dnspark.net/#173</link>
            <description>As of 15:42 CDT the attack has ceased against ns5.dnspark.net. We are still working to restore service to ns1.dnspark.net and ns3.dnspark.net.</description>
            <pubDate>Sun, 26 Nov 2006 22:48:14 +0100</pubDate>
        </item>
        <item>
            <title>ALERT: DDOS Attack on ns1, ns3, and ns5</title>
            <link>http://status.dnspark.net/#169</link>
            <description>At this time we are the victim of a distributed denial of service attack. ns1.dnspark.net, ns3.dnspark.net, and ns5.dnspark.net are being targeted. If you are experiencing problems and your domain is on one or more of these nameservers, please open a ticket and we will work with you to get your domain back online as quickly as we can.  To help use serve you most efficiently, please include the specific domain(s) the ticket pertains to.</description>
            <pubDate>Sun, 26 Nov 2006 11:41:30 +0100</pubDate>
        </item>
        <item>
            <title>Mail Pathfinder and Guiding Delays</title>
            <link>http://status.dnspark.net/#161</link>
            <description>We are currently experiencing delivery delays for Mail Pathfinder and Mail Guiding. We are aware of the problem and actively working to resolve it.</description>
            <pubDate>Wed, 01 Nov 2006 00:42:05 +0100</pubDate>
        </item>
        <item>
            <title>All services restored!</title>
            <link>http://status.dnspark.net/#157</link>
            <description>All DNS services are fully operational at this time.</description>
            <pubDate>Wed, 25 Oct 2006 18:37:11 +0100</pubDate>
        </item>
        <item>
            <title>DOS Attack Resolved.</title>
            <link>http://status.dnspark.net/#153</link>
            <description>We have mitigated the initial attack and services have been restored at this point. We are still working with one facility to restore ns2 to full capacity.</description>
            <pubDate>Wed, 25 Oct 2006 16:50:36 +0100</pubDate>
        </item>
        <item>
            <title>Denial of Service Attack</title>
            <link>http://status.dnspark.net/#149</link>
            <description>We are currently experiencing a severe degredation of services due to a denial of service attack. We are working to restore services as quickly as possible.</description>
            <pubDate>Wed, 25 Oct 2006 16:33:18 +0100</pubDate>
        </item>
        <item>
            <title>Credit Card Processing Problems</title>
            <link>http://status.dnspark.net/#145</link>
            <description>We are currently experiencing problems with our credit card processor. We are working to resolve the problem and hope to have everything back online shortly.</description>
            <pubDate>Fri, 07 Jul 2006 16:46:28 +0100</pubDate>
        </item>
        <item>
            <title>Hardware Replacement</title>
            <link>http://status.dnspark.net/#197</link>
            <description>The failed hardware is being replaced and services should be coming back&lt;br /&gt;
online by 11:30 CST (GMT -5). The Web Guiding and Web Camping services&lt;br /&gt;
will be the first services brought up and tested, followed by the DNS&lt;br /&gt;
Park websites.&lt;br /&gt;
&lt;br /&gt;
We thank you for your patience. We are already working to reschedule&lt;br /&gt;
hardware and infrastructure upgrades planned later for this year to&lt;br /&gt;
ensure this doesn't happen again in the future.&lt;br /&gt;
&lt;br /&gt;
If you have any questions you can contact us at parkrangers@dnspark.com.&lt;br /&gt;
We will get to each request as quickly as possible. Additional&lt;br /&gt;
notifications will be sent out as services are brought back online.</description>
            <pubDate>Tue, 07 Feb 2006 17:25:00 +0100</pubDate>
        </item>
        <item>
            <title>Hardware Failure - Web Services Unavailable</title>
            <link>http://status.dnspark.net/#193</link>
            <description>February 7, 2006 03:30 CST&lt;br /&gt;
&lt;br /&gt;
An unexpected hardware failure in one of our firewalls has caused all&lt;br /&gt;
web services to become unavailable. We are actively working on restoring&lt;br /&gt;
services and should have a solution in place within the next few hours.&lt;br /&gt;
During this time Web Guiding, Web Camping, Dynamic DNS Updates, and the&lt;br /&gt;
DNS Park websites will be unavailable.&lt;br /&gt;
&lt;br /&gt;
Earlier there were delays in mail delivery initially caused by the&lt;br /&gt;
firewall failures, but those delays have been remedied and mail services&lt;br /&gt;
are passing mail at normal rates.&lt;br /&gt;
&lt;br /&gt;
Since our online support ticket system is unavailable, please contact us&lt;br /&gt;
at parkrangers@dnspark.com if you have questions. We will get to each&lt;br /&gt;
request as quickly as possible. Notifications will be sent out as&lt;br /&gt;
services are restored.</description>
            <pubDate>Tue, 07 Feb 2006 10:30:00 +0100</pubDate>
        </item>
        <item>
            <title>Website maintenance announcement</title>
            <link>http://status.dnspark.net/#137</link>
            <description>Over the next several weeks we will be upgrading multiple areas of the web-based control center to resolve several bugs and enhance the ease of management. The control center may be unavailable at times during our maintenance windows to in order to perform the upgrades. If you have any questions or concerns, please feel free to contact us via the support system.  Thank you for your patience as we make these improvements.</description>
            <pubDate>Tue, 24 Jan 2006 22:14:39 +0100</pubDate>
        </item>
        <item>
            <title>Credit Card Processing Problems</title>
            <link>http://status.dnspark.net/#133</link>
            <description>At this time our credit card merchant is having problems and causing purchases to fail with an 'unknown database error'. If you are having trouble purchasing services you may use PayPal or you may contact us at billing@dnspark.com and we can issue and invoice for the services that can be paid later.</description>
            <pubDate>Tue, 24 Jan 2006 20:29:16 +0100</pubDate>
        </item>
        <item>
            <title>Merry Christmas!</title>
            <link>http://status.dnspark.net/#129</link>
            <description>We hope everyone had a blessed Christmas and New Year with their families. We look forward to another great year.&lt;br /&gt;
&lt;br /&gt;
The DNS Park Team</description>
            <pubDate>Mon, 02 Jan 2006 15:49:01 +0100</pubDate>
        </item>
        <item>
            <title>Credit Card Processing Problems</title>
            <link>http://status.dnspark.net/#125</link>
            <description>Our credit card merchant is currently having problems with their system and credit card purchases are not working at this time. We are working to see the problem resolved as quickly as we can.</description>
            <pubDate>Thu, 10 Nov 2005 15:02:48 +0100</pubDate>
        </item>
        <item>
            <title>ns1.dnspark.net IP address change</title>
            <link>http://status.dnspark.net/#121</link>
            <description>We are being forced to change the IP address of ns1.dnspark.net and ns1.dnspark.com since our service provider is reallocating addresses. Effective October 31st ns1 will only answer to the new IP address. The new addresses are as follows:&lt;br/&gt;&lt;br /&gt;
&lt;br/&gt;&lt;br /&gt;
ns1.dnspark.net - 64.34.197.141&lt;br/&gt;&lt;br /&gt;
ns1.dnspark.com - 64.34.209.236&lt;br/&gt;&lt;br /&gt;
&lt;br/&gt;&lt;br /&gt;
All DNS Rescue customers should ensure that we can continue to perform zone transfers from their master if they are using IP based restrictions.</description>
            <pubDate>Sat, 15 Oct 2005 16:06:33 +0100</pubDate>
        </item>
        <item>
            <title>Hurricane Rita Evacuation - Support Delays</title>
            <link>http://status.dnspark.net/#117</link>
            <description>DNS Park is in the process of moving some of our support staff out of our Houston, Texas area. We do not expect any delays in getting to support requests, but there may be some delays since part of our staff are in transit to other areas and others ready themselves for the approaching hurricane Rita. Thank you for your support. We will keep your critical services running throughout the storms in our area. We do not expect any service interruptions in any of our data centers.</description>
            <pubDate>Thu, 22 Sep 2005 18:43:25 +0100</pubDate>
        </item>
    </channel>
</rss>
