UtterlyBoring.com is produced by Jake Ortman (e-mail, resume), a 31-year-old dad, percussionist, freelance Web designer, consultant and jack-of-all-trades computer geek, living in Bend, Oregon. He created this so that his expensive journalism and technology degree isn't getting totally wasted. In addition to editing this site in his free time, he is the IT Director and Ad Designer at both Sunray and Discover Sunriver. He has LinkedIn, MySpace, Facebook profiles if you're trying to stalk him.
Opinions and comments on this site are the opinions of the author, not the author's employer, family, friends or pets.
This site is powered by Movable Type and is hosted by orty.com. Internet connection provided by BendBroadBand. Since December 1st, 2002, there have been 5529 entries. Visitors to this blog have posted 18149 comments.
If you're reading this, you have too much time on your hands.
Last night I transferred Bend Blogs and this site to a new Web server (after getting my new servers all setup). If you're reading this, you're reading it on the new server. The server's running PHP 5, Apache 2.2 and MySQL 5.1 while the old server was running PHP 4, Apache 1.x and MySQL 4.1. It's also a much meatier server than before, and Bend Blogs seems to render much quicker than before (the rumors were that PHP 5 would help that a lot).
If you notice any weirdness, comment here or email utterlyboring [at] gmail [dot] com.
Update at 11:30PM on 6/16: DNS issues suck, you know that?
Anyway, after struggling figuring out why CentOS5's BIND implementation and cPanel 11 didn't want to play nice (which caused some traffic to the new server to get lost today), I found this forum thread which I'd had to find before, but couldn't remember how I found it, so I'm bookmarking it here.
Long story short, if you're running CentOS 5 and cPanel and you find that name server lookups are getting refused even though BIND is up and running fine, run this command: "/scripts/fixnamedviews --force". Quick, simple fix. And I've linked to it before, but for some stupid reason I couldn't find it. So the more places I bookmark it so that I can make sure to fix its lame nameservers, life will be good.
Jake said on 06/16/08 @ 03:38 PM: Hmmm...that sounds like something funky on your end, Barn, as it works fine for me. If you're able to hit utterlyboring.com w/out the www, you're obviously hitting this server.
Do me a favor: run an nslookup from the command line: nslookup utterlyboring.com and then nslookup www.utterlyboring.com, and let me know if they give you different IP addresses.