Originally when I started buying domains from Yahoo the cost was around 10$ per year. Then it went up to 13$ per year. Now with the recent financial crisis around the world, Yahoo has decided to tripple their yearly fees TO 34$ yer pear. I am either cancelling my domains at warp speed, or contemplating transferring them to Go Daddy for a fraction of the price. Technically I can host them from my house, but I get nervous with the dynamic IP address provided by Optimum online. I haven’t had an IP address change in a long time, and for all practical purposes without the modem being offline for a long time the IP address rarely ever changes.
Overall I am going to cancel as many domains as I can, thus eliminating many of my websites. I am going to remove the websites that do not receive many hits, ect… I will keep my main website, which I plan to have my entire life. I also will keep this domain, because I have many websites consolidated into it, as well as this blog which I cherish as a means of venting and documentation. Maybe I will transfer some domains to Go Daddy, I have a couple of things to think about before the critical date that Yahoo wants payment before it stops hosting the domains.
Share, Enjoy, and Support:
If you want your Mediawiki installation to properly display from the following example subdomain:
wiki.bgevolution.com
You will need to add the following to your LocalSettings.php configuration file:
$wgScriptPath =”";
You will also have to adjust the ANAME records of your DNS server to make sure all subdomains are forwarded to your servers IP address. Use the wildcard (*) and everthing should be find. You will also need to create a name based apache virtualhost to receive the incoming subdomain request. Something like the following works fine:
<VirtualHost *>
HostName wiki.bgevolution.com
DocumentRoot: /home/user/mediawiki/
</VirtualHost>
Share, Enjoy, and Support:
Combing through many free domain blackhole lists the following are relatively extensive, and are readily maintained.
combined.njabl.org
list.dsbl.org
dnsbl.sorbs.net
spam.dnsbl.sorbs.net
Using these blacklists in your sendmail configuration can reduce the spam received from the most common and prevailing sources. Combining these active spam prevention measures, with passive techniques spam can be greatly reduced. Passive spam prevention includes blackhole lists that are not controlled by you. You can also implement graphical active spam filtering using Mozilla Thunderbird via filters.
Share, Enjoy, and Support:
Creating subdomains is as simple as creating full domains. The easiest method is using VirtualHost blocks. The following is a VirtualHost declaration for a regular domain:
<VirtualHost *>
ServerName bgevolution.com
ServerAdmin admin@bgevolution.com
DocumentRoot /home/user/bgevolution/
</VirtualHost>
The following is a VirtualHost declaration for a subdomain:
<VirtualHost *>
ServerName bgtorch.bgevolution.com
ServerAdmin admin@bgevolution.com
DocumentRoot /home/user/bgevolution/bgtorch
</VirtualHost>
The only difference between the declarations is the addition of the subdomain in the ServerName, and the specification of the subdirectory, of the DocumentRoot, within the bgevolution folder.
Share, Enjoy, and Support:
On Fedora, the system configuration requests a domain name and a hostname separately. On Ubuntu it requests only the hostname, in which you would input your hostname.domain. On Debian it also requests only a hostname, in which you would also type hostname.domain.
On Ubuntu and Fedora you can reference your computer just by the hostname. I have noticed that on Debian, an SSH connection will show the host computer as the hostname.domain. There is nothing to be worried about, this is just some observations about the behavior of different Linux distributions.
Note that on Debian systems, you cannot use a short hostname, you need the hostname.domain to establish a FQDN (Fully Qaulified Domain Name). To set the hostname use:
sudo hostname -v hostname.domain
For instance, the web server, that produces this website, uses a hostname of web.bgevolution.com, where web is the hostname and bgevolution.com is the domain name. At one point I tried to just use the hostname as web, without the domain, and by not setting the domain, Apache was setting 127.0.0.1 as the FQDN. I dont think this is an issue at all, as Apache fully functioned properly, but none the less I dont like to see errors when I restart a computer service, therefore I set the hostname to include a domain to establish a FQDN 
Share, Enjoy, and Support:
