For security and efficiency reasons, a hosting system DNS server should not answer recursive queries (solve DNS requests for domains it is not authoritative for).
However, the DNS server needs to accept recursive queries for the services hosted on the same system for these services to work correctly and be able to resolve forward and reverse hosts/IPs.
In some instances using the ISP’s DNS service is not desirable. Maybe for speed or maybe for privacy concerns a trusted DNS provider is preferred instead.
While the DNS settings can be manually changed after each (re)connection, applying a permanent solution requires a bit of file fiddling.
Data always piles up and on a small VPS the storage space can quickly get consumed by leftover or unused programs.
When things get too crammed it’s time to use the available tools and clean up some of the unwanted things.
Linux generally keeps multiple versions of the kernel installed. This is done to maintain backwards stability and allow the selection of an older (tried and tested) kernel if the latest update fails in any way.
On a small system all these kernel versions can quickly add up and waste valuable space. In such case keeping only the needed versions (the latest and the one currently booted, if different) is an acceptable risk to take.
You’ll need a fairly recent operating system distro (CentOS is too conservative and failed for me, but Ubuntu 16.04 LTS worked fine) and a couple of programs and packages.
By default Apache displays information about itself in the server signature included with reply headers and sometimes auto-generated pages. This information can give away important clues, like the exact version number of a module or Apache itself.
While obscurity never increases security since exploits can be attempted on the service regardless, knowing exact version information and running modules certainly provides a potential hacker with useful clues and eases the task.
I had to look for an alternate VPN system to use when I need to dial back to my home network while on the move to access my media library or when I require a trusted connection or a whitelisted IP.
The next best thing (and least complicated to set up going from PPTP) is IPSec/L2TP, which has built-in support in most current operating systems (including Windows, Linux and Android). Due to its double-encapsulation nature (L2TP performs the tunnelling of data and IPSec provides the encrypted channel), L2TP/IPSec has a more complex setup and configuration procedure, both for the server and the client.
In lack of better or more specialized tools, a disk’s read and write speed can be quickly and roughly tested using Linux’s built-in dd tool.
CentOS is a conservative server operating system, choosing stability over features. Because of this the major versions of PHP it usually includes are several numbers behind the current release.
However, there are plenty of good third party repository out there that provide newer releases for these packages.
There are times when typing the same password over and over again gets cumbersome, or odd instances where typing a password isn’t even possible.
These are the cases where password-less login – also known as public-key authentication – is the solution.
I make the assumption that you’re running PHP 5.3 (the currently newest PHP version officially available in CentOS 6) or perhaps PHP 5.4.
The switch can, theoretically, be done on live system – just prepare yourself for a bit of hiccups here and there (or perhaps even serious downtime).
There are plenty of TVs to chose from and nowadays they all know DVB-C so why go through all the trouble of building a TV player with a Raspberry PI?
Well… because it’s fun and because of the freedom of being able to watch your favourite TV channel on any of your devices – even when away.
