Strav's blog

OK - I went ahead and set up the other 3 DNS sites as secondary servers. I had a bit of trouble with vcsweb, (strav.com, strav.net, and egiveit.com showed errors, but zilliox.us didn't even though they were all set up the same). I sent an e-mail to support at vcsweb and they responded quickly that they were confused as well and that zilliox.us should be displaying the same errors. These errors should disappear once the delegation (registration of name servers at the registrar level - Dotster in my case) is complete. So, within 72 hours, I should have 8 nameservers from 5 different companies for each of the sites. That should pretty much eliminate outages from DNS attacks. :)

OK - Back to the DNS issues for my zones. After jumping through hoops at the "Public DNS" (granitcanyon), I've spent over a week making nameserver changes to whois and mucking around with settings within Zoneedit. I've made some progress, but not nearly enough and I'm tired of dealing with it. Tonight, I tried to work with it more, but granitecanyon's help newsgroups were non-responsive (i.e. not available). I did a little more searching and wound up at twistedforlife. I had them completely set up and running as a (free) secondary nameserver for all 4 of my sites in less than 1/2 hour. I can't recommend them enough!!!! Here is a list of some others which I may try to add as additional secondaries in the near future:


Free DNS Hosting Services


freeDNS.afraid.org
Vcsweb

xname

Yet another thing that drives me nuts about XP. I'm sick of having to tell the system over and over that I actually DO want to run the program that I just executed. This will prevent that dialog box from popping up every time you try to run a new file on the system.


Run gpedit.msc, and go to
Local Computer Policy
 ->User Configuration
  ->Administrative Templates
   ->Windows Components
    ->Attachment Manager
Enable "Default risk level for file attachments"
Enable "Inclusion list for low risk file types"
Add the file extensions that you want to open without being bothered.

I'll update this list if I make additions to it.

Ack!!!! I finally figured out why udev wasn't working on the laptop. It turns out that the symlink I made from the /etc/udev/rules.d directory to the network.rules file was named 010_network_rules. That '_' before the 'rules' in the symlink needed to be a '.' so apparently the file was never read by udev. Such a simple solution to something which has consumed many hours, not to mention the elevated stress levels. Ah well, at least it's working again. Now I can get back to moving over to the new wireless router.

Doing a chroot with udev is a little trickier than it was before udev. Here are the steps:

mount /dev/sda1 /mnt/linux/boot
mount -t none /dev /mnt/linux/dev -o bind
chroot /mnt/linux/boot
mount /proc
mount /sys