There's no Place Like ::1

So lately, I am having problems accessing my 0x82.com at home. This domain sits on a dynamic IP address, and I use editdns to update the DNS records.

EditDNS advertises my A record with a 0 TTL. However, I found that my ISP Sapo caches the record with a huge TTL:

0x82.com.        604800    IN    A    82.155.174.2

Before I shout “what th f0ck are wrong with this guys”, I still have to do a quick read of the relevant RFC, because I think that a 0 TTL may not be a “standard” thing…

As always, if you know something about this, please shoot! :-)

As you probably might felt, my domain was having serious DNS problems for the past week or so. In spite of the problems, I manage to get a large number of visits on a rant post with a smart title “Apple Hardware Sucks” :-)

For a while I was using the free zoneedit service. It worked for a year or so, and I recommended it to all my friends! However, one week ago, the slave NS stoped updating from the master NS. This resulted in all kind of problems when using this domain. I contacted the zoneedit admins and they were quick to anwser, saying that they were aware of the problem and their sysadmins were working on it.

Since I’m using ddclient to update my dynamic IPs, I searched the docs and the first protocol supported was dnspark. Registered, moved my NS, updated the scripts, back online :-)

Bye bye zoneedit, you served me well.