|
Post by eye on May 23, 2012 18:46:13 GMT -6
Link to download master You have to replace the full Master because more has been changed on the master then just the master IPS ok For those that wont know how to copy and paste app.box.com/s/el1t9rthxwnfhatyfa1q
|
|
|
Post by eye on Aug 29, 2012 11:06:52 GMT -6
//AUTHOR - who cares //This is the master.cs file for //eye's Master Server. //Long Live Starsiege !!!
$Inet::Master1 = "IP:starsiege.noip.us:29000"; // Eye's Master Server $Inet::Master2 = "IP:southerjustice.dyndns-server.com:29000"; // southerjustice Master Server $Inet::Master3 = "IP:dustersteve.ddns.net:29000"; // DusterSteve's Master Server ( $Inet::Master4 = "IP:starsiege.from-tx.com:29000";
//$Inet::Master1 = "IP:ss1m1.masters.dynamix.com:29000"; // original //$Inet::Master2 = "IP:ss1m2.masters.dynamix.com:29000"; // original //$Inet::Master3 = "IP:ss1m3.masters.dynamix.com:29000"; // original
//$inet::IPBroadcast1 = "IP:broadcast:29001"; //$inet::IPXBroadcast1 = "IPX:broadcast:29001";
# times here are in ms $pref::maxConcurrentPings = 30; $pref::pingTimeoutTime = 600; $pref::pingRetryCount = 3; $pref::maxConcurrentRequests = 10; $pref::requestTimeoutTime = 300; $pref::requestRetryCount = 2;
|
|
|
Post by eye on Mar 4, 2013 14:13:13 GMT -6
ok The Newest update on master is now ready for you all. I noticed on win7 and vista you may need too( cut your old master out ) because for some strange reason it doesn`t allow the changes to happen . So cut old one out , - Then copy new master and paste it into the script folder Link to download master You have to replace the full Master because more has been changed on the master then just the master IP`S ok For those that wont know how to copy and paste app.box.com/s/el1t9rthxwnfhatyfa1q
|
|
|
Post by eye on Jul 1, 2014 14:11:53 GMT -6
We want to update all our loyal customers about the service outages that many of you are experiencing today. This is NOT A TECHINCAL ISSUE WITH NO-IP. This morning, Microsoft served a federal court order and seized 22 of our most commonly used domains because they claimed that some of the subdomains have been abused by creators of malware. We were very surprised by this. We have a long history of proactively working with other companies when cases of alleged malicious activity have been reported to us. Unfortunately, Microsoft never contacted us or asked us to block any subdomains, even though we have an open line of communication with Microsoft corporate executives.
We have been in contact with Microsoft today. They claim that their intent is to only filter out the known bad hostnames in each seized domain, while continuing to allow the good hostnames to resolve. However, this is not happening. Apparently, the Microsoft infrastructure is not able to handle the billions of queries from our customers. Millions of innocent users are experiencing outages to their services because of Microsoft’s attempt to remediate hostnames associated with a few bad actors.
Had Microsoft contacted us, we could and would have taken immediate action. Microsoft now claims that it just wants to get us to clean up our act, but its draconian actions have affected millions of innocent Internet users.
Vitalwerks and NoÂIP have a very strict abuse policy. Our abuse team is constantly working to keep the No-ÂIP system domains free of spam and malicious activity. We use sophisticated filters and we scan our network daily for signs of malicious activity. Even with such precautions, our free dynamic DNS service does occasionally fall prey to cyber scammers, spammers, and malware distributors. But this heavy-handed action by Microsoft benefits no one. We will do our best to resolve this problem quickly. This is a letter I received from noip to who I have my noip for starsiege and this is what caused trouble for us all .
I pay for my connect and microsoft walked all over my rights ..
Formal notice of outage caused by Microsoft takedown
We are working through the night on an alternative solution to resolve these issues. Please know that we are on your side with this issue and are doing everything we can to resolve it as quickly as possible. You can also read our formal response on our blog.
After you read it, please to share it on Twitter and tag your responses with #FreeNoIP.
Have any questions or comments? Please do not hesitate to open a Support Ticket or give us a call at 775.853.1883.
|
|