New answers tagged


A large point of HTTPS is to make sure that the server you're talking to has a certificate for the name you used to reach it (that is, the name visible in the browser's URL bar). So no, you can't use a default certificate and your own name. If you could, that'd be a security problem. You need to get a certificate that has your domain name in it.


Some rootserver provider offer routable ip adresses (failover ip); that way you can set up two servers prepared to use the same routable ip address (additional to their static primary ip). To keep both servers synced you may use a network file system like drbd and/or db replication. When the primary server goes down, you can automatically reroute the domains ...


What you might want to achieve is a LOAD BALANCING/CACHE infrastructure. There are several ways to do this. What you have to decide first is how to implement it and where will your Load Balancers be hosted. Option #1 - Load Balance using DNS Round Robin Technically not Load Balancing in the most real sense of the term. You can achieve this by adding 2 or ...


If this isn't you, then it must be somebody else... It's common for the web to have Bots, Spiders and Crawlers. Check your log files for the IP to see where the request is coming from. These crawlers usually just use "common" URL paths in the hope that you're using them. If they are just crawling you, then that is not an immediate security threat. But if ...


When you create a root domain at 1&1, another domain is created alongside of the format or etc. This second domain acts as CNAME record for the root domain or any subdomains, when using a third party name server.

Top 50 recent answers are included