August 26th 2008 to Monday
September 8th - Reconfiguration of Seanet DNS servers
ONGOING
A flaw in the DNS protocol has
forced us to reconfigure our DNS servers in order to protect our customers
from being directed to malicious websites and having their emails routed
through unauthorized servers. For most of our customer's no action
needs to be taken, we have already pointed dynamic DNS requests to our new
server. If you have statically configured DNS on your network, it is
vital that you update the settings immediately or risk
the consequence of malicious attacks or loss of internet on Monday
September 8th. This action must be completed by Monday
September 8th, at this time we are going to disable requests to
the unprotected servers. We have sent an email out to customers' who
are using our old DNS servers, which contains a link to a page detailing
the action nescessary in order to protect your privacy and security on the
World Wide Web. August 11th
2008 - Web Server DDoS Attack Resolved UPDATE: The sites
which are affected by the DDOS attack have been moved to a new IP address. At approximately 9:10
on August 11th one of our web servers (control.seanet.com) started
experiencing a Distributed Denial of Service attack which floods the
server with packets of data. Because the website under attack is on
a shared IP, we had to disable that IP in order to keep most websites up. August 8th
2008 - Intermittent DSL connectivity Verizon/Quest PPPoE
RESOLVED Customers may be experiencing packet loss which is expressed
through intermittent connectivity. One of our internal routers seems
to be causing this issue and we are currently aware of the problem and
taking steps to resolve this. July 3rd
+ July 22nd - DSL
connectivity for Verizon customers
Resolved
Final Update: Verizon replaced the DS3 card in
their central office and we have noticed no problems since. The
status is now resolved.
3rd Update: We appreciate your patience during this
prolonged Verizon network problem. We have been in contact with our
Verizon representative and been informed that they will be replacing some
of their equipment in the central office tonight. Initially when we
reported our troubles we were informed there were no problems with the
Verizon network. Our administrators are monitoring the situation and
will update this page as information becomes available.
2nd Update: There has been a reoccurrence of the DSL problem we
experienced on July 3rd. We are currently investigating to find what
is the cause for the current connectivity problem.
UPDATE: The problem seemed to be due to some malformed packets from
outer sources entering our hardware. We have implemented a filter on
our systems to prevent this in the future and are monitoring the current
status continuously. One of our internal routers, which handles traffic for many DSL
customers, is producing errors which may result in intermittent loss of
connectivity. We are aware of this problem and are in the process of
configuring a new router to handle DSL requests. This is a
complicated process and we need to do some testing to make sure the switch
does not result in a complete loss of connectivity so we appreciate your
patience. We will update this page with more information early next
week.
New anti-spam policy
implemented on outgoing server mx.seanet.com February
29th- All outgoing mail through mx.seanet.com must contain a reply-to
address in Seanet database IMPLEMENTED Due to the
spam attack noted below on February 27th Seanet has implemented a new
policy on outgoing mail server. It is intended to help to reduce spam
coming from us. We had to do this to prevent our customers being
banned from emailing common addresses such as Hotmail, Comcast, Excite
and Google. New outgoing mail servers will only accept messages
with sender's address accounted in our database as either Seanet mail
account, a virtual mail, or a domain name. We allow sender's address
as:
john@seanet.com (login <john> must be accounted in database)
john@john.seanet.com (if login <john> has static IP)
john@orca.net (if there is a virtual mail <john> configured for
domain <orca.net> in database)
john@acme.com (if there is a catch all for domain <acme.com> in
database)
Senders who are using a domain that is not accounted for on their
account will not be able to send mail using that address. We
realize this may inconvenience customers in the short-term, but this
policy will help alleviate problems caused by spammers. If you
wish to still use mx.seanet.com to send outgoing mail using an address
Seanet does not have record of you may call our Technical Support Team
and add this domain to your account free of charge.
February 27th- Spam email asking for
your Seanet webmail password Restored It has come to
our attention that there are messages purporting to come from
seanetmanagement@seanet.com
with the subject "Confirm Your Seanet Webmail Account". In this
message, it asks for your password and states that if this is not done
immediately your account will be removed. Seanet will NEVER ask
for your password via email and you should not reply to this message.
If you have already responded we recommend you call our technical
support staff to assist you with changing your password immediately.
|
