Well my problem is, we have 2(ABC and XYZ company) internet connection and sometimes,
the ABC connection is not active and we're disconnected for about 2-4 minutes interval to get the XYZ internet connection online.
My question is - Is there a software that will automatically set the XTZ internet connection to active? Something like if the ABC connection is down, the XYZ will supply internet connection right away.
I'm not a server admin, but help my client with basic it tasks...we built their website for them and just sort of fell into helping them out when they need it. My client has a vps with knownhost, the vps is only used for hosting the email for their domain, the website is hosted on another server. 4 days ago, I logged in and checked the mail queue and found thousands of emails in the queue that were phishing emails trying to get passwords from the recipients for a service called moneybookers.com. According to knownhost, the hacker had guessed the password of one of the email accounts and had started sending mail through it. The hacked account was deleted that day as it was a test account and was not needed anyways. As soon as the account was deleted, the phishing mails stopped being sent. Knownhost reassured us the server hadn't been breached, but we changed the root password anyways. Around 15k to 20k emails were sent in a 14 hour period. Since that time we have appeared on a few blacklsts and have a negative senderbase score and so any company that uses senderbase is obviously rejecting our mail... My client has just hired assuretymail services to get accredited and has invested a lot of money into streamlining mail delivery, so this is obviously devastating to them.
Today I logged in and again found 1000's of email in queue, yet again, and this time they were paypal phishing emails. I immediately changed the passwords of all 50 of the email accounts, including the root. It looks like around 14k or so emails were sent.
Trying to understand how this could happen yet again, knownhost is saying that, yet again the account "test", the same account used last time was used for sending out emails. I was confused by how a previously deleted account could be used to again begin sending emails even though it was deleted 4 days ago. According to knownhost "[FONT='Verdana','sans-serif']The only reasonable explanation for this activity would be that exim cached credentials for system user "test" and didn't refresh its internal cache since the moment when "test" account was removed. To force exim to refresh the cache exim mail server was restarted on your system, so it shouldn't be possible to use that (non-existent) account again to relay the mail through your system."[/FONT]
[FONT='Verdana','sans-serif'][/FONT] [FONT='Verdana','sans-serif']Being that I'm not a server admin and I rely on knownhost for server admin basics, am I out of line thinking that knownhost dropped the ball here? I mean is it obvious that a restart was in order after the first hack or is this just a bad chance scenario. Is the scenario they are describing plausible?[/FONT]
I want to add a DNS Failover automated service at my server, in order that when it goes down, the DNS Failover enters in action and it will redirect all the traffic to a second backup/failover server (hosted at a different location).
So in order to do this i have been looking around and i have found dnsmadeeasy, and i found their offer interesting.
But i still have some question and doubts on how a dns failover service works. So maybe someone can expalin it to me.
My question and doubts:
1 - If i use for example the DNS failover from dnsmadeeasy, i would have to buy 2 servers where one is the principal server and the other is a backup/failover server, so when my main server goes down, the dnsmadeeasy will detect in a automatic way, and redirect all the traffic to my backp/failover server. After my principal server goes back online, dnsmadeeasy will automatic redirect all the traffic to the principal server.
Im i correct? Or i understound wrong how this works?
2 - I use my own Nameservers and i want to continue to use my own nameservers. So if i use dnsmadeeasy services, i will be able to continue to use my nameservers as ns1/ns2 and then i will add the dnsmadeeasy ns3/ns4...as the following example: ns1.mynameservers.com ns2.mynameservers.com ns3.dnsmadeeasy.com ns4.dnsmadeeasy.com ns5.dnsmadeeasy.com ns6.dnsmadeeasy.com
In making my plans for my web hosting business I plan to start, I've thought about a failover but wanted to know the best way to set it up.
I would ideally like to start with something like getting a small shared hosting solution (not reseller, just shared) at a reliable hosting company. On this hosting plan, I will host a simple 1 page site that says my company is having technical difficulties, reminds people that data is safe, and provides any contact information accessable (like e-mail/phone/etc...).
I already have DNS setup offsite.
I would like that if my server(s) go down for any reason, whatsoever, that DNS automatically starts serving the temp site.
so if my server suddenly goes down, [url]or [url]suddenly goes to the offsite shared hosting plan.
This would not provide customer site redundancy. This would only ensure that if anything happens to my service, customers have a page available that explains what is happening and has information to contact us to get more details.
We have 2 Cisco PIX 515's in a failover configuration (7.1 series IOS). We have available both a serial failover cable and adequate switch capacity to allow using either the serial or LAN-based approach. We have no current plans to locate the firewalls physically apart.
We have plenty of info on how to configure either, but no recommendation on which is the better choice.
I have a reseller account with a company that often has spontaneous DNS errors, and this, as you know looses us money. I also have a dedicated server running a panel exclusively via IIS. Is there a way I can set up my dedicated (Windows) box and my reseller account in a mirror way, so if one of them fails, the other will take over.
There are no file changes often, more database then anything. Is this possible? Main necessities are:
(Or, if a shared hosting company can accommodate this somehow and is relatively inexpensive.
Basically have 2 hosting accounts at different providers...each set-up for the same domain name...and then somehow wtih DNS make it so if host #1 goes down traffic goes to host #2 (which would basically be a splash screen explaining that host #1 is down and will be back soon).
DNS isn't my strong point, but I do know you can do this with MX records...so if the first server fails it tries the next until it gets a working one or reaches the end of the list. I'd just like to do it is A records.
It wouldn't be as simple as setting the nameservers like this would it?
Assume, a DNS failover service would change the DNS from server 1 to server 2 when the first one is offline. This will be changed quite fast, however isn't it true that some visitors still experience a downtime of a couple of hours (saying that the main server will be offline for 6 hours) as their ISP might not update DNS that frequently?
So basically, what is the added value of a failover service?
What happens if your primary nameserver goes down? Meaning that it goes completely off the net, not even denying dns requests but completely ignoring them.
I'd guess that resolvers would query the secondary NS after a specified timeout, but what is that timeout set to? Does it differ from ISP to ISP? How much of a slowdown are we looking at for end users?
We want to provide failover service at our server using dnsmadeeasy service.
So we have already buy the "failover server" (running linux/plesk), and now we are looking to find the most adequate / best way in order to keep the 2 servers sincronized, in order that if "main server" goes down, all the traffic can be redirect to the "backup server" using dnsmadeeasy.
on scripts/software to keep 2 linux servers sincronized in a failover setup?
I'm working for a client who has an e-commerce site currently hosted on a shared hosting solution.
He is now looking for 100% uptime (as near as), so I have suggested that we get 2 VPS and use DNS monitoring to switch servers as required (from DNSmadeEasy).
This is all fine, and the websites files/images do not change often, so I can use rsync every so often to sync these. Not a problem.
What does change frequently is the mySQL db for the site.
I've been looking at MySQL replication, but this seems to be no good. If one server goes down, then the other one takes over, they don't automatically sync themselves after they come back up. It seems MySQL cluster is best, but this needs 3 servers and they all need to be on the same LAN.
I've read you can set MySQL replication to MASTER-MASTER so that it acts like a cluster, and resyncs itself as required.
I have been searching and searching for a solution. We are currently using one single vps to host some of our clients. We are finding more and more that we need to have some redundancy.
I have looked at using DNS failover using RSYNC/mysql replication etc with two servers, but just dont like the idea.
I have also looked at hosts like imountain etc that use h-sphere. I dont like this setup because services are split onto single machines. For example mail is done on one single server, therefor if that server is down, mail is down.
What I am looking for:
I am trying to stay in a budget of 150/month or less.
I would like to get one of the two options here:
option 1: two vps's or dedi's that technically act as one(a true cluster) then on top of that is OS and control panel and done. This solution doesnt allow for whole datacenter outages, or network issues.
option 2: Two geographically placed vps or dedi's that are somehow either load balanced, or failover.
Ultimately our goal is to have high uptime, but we dont really have much server load.
Basically failover is ok as loads are always low anyway, but if we are paying big $$ it would be nice to have it load balanced.
Please let me know if my expectations are way to high or my price is way too low. I need to find a solution here somehow and if I cant find anything will most likely just go with DNS failover.
I want to setup a failover approach in which if after a particular timeout say 10secs the load shifts to some other website like Refer.com | The world. The timeout should be in Proxy Pass and if timeout occurs it shifts to Refer.com | The world
im looking to add failover protection at my main server, in order that if it goes offline, all the traffic can be in a automatic way redirect to a failover / backup server.
For the failover server i was looking to buy a low-cost dedicated server located in other datacenter and have my dns be run at this failover server, but now i have been looking at Cloud Hosting, like Amazon or Mosso CloudServers and as it seems a very stable network, im thinking if it will be best to have setup/running my DNS at a Cloud Host...
So what do you think it would be best:
Option A: 1 main server 1 failover dedicated server 1 cloud (amazon/mosso) virtual server to run DNS
Option B: 1 main server 1 failover dedicated server (running the DNS)
So, there is my example. I have two servers in different locations. First one is the main server with all the data and the second one has just simple notice like "We will be back soon".
Now, if I set the primary DNS server on main server and secondary DNS on second one (but with different A records), will users actually get the server two if main server is down?
Will this work or not? I want 100% access to the site, at least to the server with only notice (I don't need data from main server). I can set the round robin, but I don't need load balancing (actually I want access only main server), but just if main server is down to go on the second one.
We have a 1 server setup. Right now all dns, web, and email are hosted from this single box.
We wish to bring in a server2 and have dns cluster setup, this would also host mirrors of email and web sites from server1.
What i want to know is what is the best way to setup the DNS cluster/nameservers?
would it be
ns1.domain.com pointing to server1 dns ns2.domain.com pointing to server2 dns?
if that is the case and lets say server 2 goes down, wouldnt that mean the 50% of hits to the web site would be denied as ns2 is down? The reason i ask this is that to my understanding nameservers do not have priority, they are randomly hit.
I am trying to provide some small bit of redundacy.
I am trying to do a fail over solution with round robin dns. Our dns is served by windows and our web servers are setup with Linux..
I know round-robin does not by default do a fail over, however my understanding is that a script can be used to remove the failed server for dns, is anyone aware of something that will do this for windows?
UA Speedy Host is a majorperformer of web hosting. We are providing quality web hosting at affordable price. We have given a new trend to web hosting business. Our web hosting packages cater needs of all sizes of companies. Why go for 100 MB or 500 MB or 1 GB web hosting packages as many web hosting companies offer when UA Speedy Host provides unlimited space at fraction of cost. You can compare us with other web hosting companies and you will find UA Speedy Host most competitive in all web hosting companies. UA Speedy Host is an ecommerce gate way for all sizes of companies.
To Know More Please Visit Below Link:
General Features General Features: Linux Package Windows Package Failover Package Disk Space Unlimited Unlimited Unlimited
Bandwidth Unlimited Unlimited Unlimited
Free Domain Domains Host Unlimited 1 1
Park / Alias Domains Unlimited Unlimited Unlimited
Sub Domains Unlimited Unlimited Unlimited
Hosting Panel Cpanel Plesk Plesk
Uptime 99.9% 99.9% 100%
To Know More Please Visit Below Link:
Cheap Reseller Web Hosting Packages:
Our Reseller Web Hosting Account give you freedom to host unlimited domain at your own price and brand. Complete transparency in every aspect allows our each reseller to fulfill their services without the worry of being discovered as our reseller. All of this is designed so you can concentrate on selling and making money while we do all of the hard technical work behind the scenes.
As our reseller, you are free to resell each account under your own brand name and charge your customers whatever you want. This allows you to have the look and feel of your own hosting company. All resellers will can also create their own private name servers (ns1.anydomain.com & ns2.anydomain.com). All end user customers of the reseller will be using that assigned name servers. Host Unlimited domains with complete security. Website and E-commerce builder tools are included freely.
To Know More Please Visit Below Link:
General Features: Linux Reseller Windows Reseller Linux + Windows Reseller
Disk Space Unlimited Unlimited Unlimited
Bandwidth Unlimited Unlimited Unlimited
Hosting Billing Software
Domains Host Unlimited Unlimited Unlimited
Park / Alias Domains Unlimited Unlimited Unlimited
I run a site with about 1,000,000 unique visitors per month and recents server failures made me decide to get a failover server to minimize downtime. My goal wasn't to get 99.999% uptime but to be able to be back on track after a failure in a "reasonable" amount of time. After evaluating several solutions, I decided to go with DNS failover. Here's how the setup work:
1) mydomain.com points to main server with a very low TTL (time to live) 2) failover server replicates data from main server 3) when main server goes down, mydomain.com is changed to point to failover server
The drawback is the DNS propagation time since some DNS servers don't honor the TTL and there is some caching happening on the user's machine and browser. I looked for empirical data to gauge the extent of the problem but couldn't find any so I decided to setup my own experiment.
The Experiment ==============
I start with mydomain.com pointing to the main server with a TTL of 1800 seconds (1/2 hour). I then change it to point to the failover server which simply port forwards to the main server. On the main server, I periodically compute the percentage of requests coming from the failover server which gives me the percentage of people for which the DNS change has propagated.
I made the DNS change at exactly 16:04 on 06/21/06 and here are the percentage of propagated users:
So even after 18 hours, there is still a certain percentage of users going to the old server so DNS failover is obviously not a 99.999% uptime solution. However, since more than 90% of the users are propagated in the first hour, the solution works well enough for me.