Eggs
Eggs for breakfast YAY!
Eggs for breakfast YAY!
Excellent link here about using jgit to publish your git repo's to amazon s3 ...
http://blog.spearce.org/2008/07/using-jgit-to-publish-on-amazon-s3.html
Very useful indeed this ... it stores your /etc/ directory in a git repo and even stores changes before apt-get runs!
Wow, what a useful tip!
Now I can have my local syntax highlighting and .vimrc options whilst editing files on any one of our servers without having to push any of my vim config!
http://vim.wikia.com/wiki/Edit_remote_files_locally_via_SCP/RCP/FTP
Ok, this post is about the local DNS server I setup for myself. the motivation behind this was three-fold...
One problem I have is that whilst we have forward and reverse internal DNS setup for all our servers in the data canters (our config management system relies on it), many of the reverse zones are not delegated to the office DNS and as such, reverse lookups fail when records exist. I can point my resolv.conf elsewhere (data-centre DNS servers), but then lookups for office-based stuff fails.
Secondly, we use a Cisco VPN at work, which I have been connecting to via vpnc. Although only traffic destined for servers on the VPN actually travels down the tunnel (with other web traffic avoiding it) ... vpnc (unless told not to) overwrites /etc/resolv.conf, which in turn means ALL DNS queries go down the VPN. This is so that DNS lookups of server addresses in our internal TLD (.tmcs) actually get resolved.
Thirdly, I often use my laptop out and about and it doesn't make me feel hugely comfortable to (in most cases) have my DNS queries hit some LAN resolver which logs queries and suchlike.
So, I decided I would run my own local caching DNS server and configure different DNS server destinations for different domains. Then, when I have finished working from home, forget to close the VPN connection, and then browse to www.a-dodgy-website.com, there's no trail left of my visit there left in the VPN logs etc. Also, I want to force my system to ALWAYS use 127.0.0.1 for lookups, and configure my DNS resolver to use the OpenDNS DNS servers for their non *.tmcs lookups.
Read on for how it's done!