Last night I got a new vps host and everything for fastbadger.com setup for it. The rest of my shit is down though. I haven’t setup a vps before (well once but I didn’t use it for long) and I had my first experiences with bind! oh joy!
I just hope that I don’t go over my 250Meg bandwidth limit for the month. it’s not clear from their tos if the site will shut down or if I’ll get billed. I check stats compulsively anyway so if I get close I’ll shut off what I have to.
My shared hosting place is taking their sweet time with getting my site back up. I just emailed them telling them that the problem’s site’s name servers have been changed to somewhere else so hopefully that will speed up the process.
Here’s what I learned in the last 24 hours with vps hosting:
Don’t install splunk unless you have a shit ton of ram to spare
– It ate up over 500 as soon as I started it up. I only have 768!
dnsreport.com is an AMAZING tool to help you configure bind right.
If your name servers are the same as your domain, you need to register that server’s ip’s with your domain registrar. (I knew that one but I forgot it)
When you’re given two ip’s from your hosting company, make sure they’re both in ifconfig. Add them yourself if they’re not.
multitail will have to work as my poor man’s splunk for now
I don’t think shorewall works on vps hosting in some cases. Due to how visualization is, shorewall gets picky about the interfaces.