Moving Registrars

I’m switching registrars so I can leave GoDaddy. There should be no issues since only the registrar data is changing. While this technically touches the DNS system, it’s only updating the registrar data at Internic and leaving the DNS servers the same (including the Start of Authority server). However if something does go wrong, now you know why.

This is the first step in a reorganization of some of the technical assets that I use worldwide. I’m cooking up some really cool things that I hope will leverage WordPress in an incredibly awesome way and also let me move away from Facebook.

Why I Won’t See ‘Untraceable’ or What Code Doesn’t Do

The advertisements for ‘Untraceable’ are pretty exciting. Some sick schmuck kills his victims using a web site. The more people visit the site, the faster the victims die.

From movies.nytimes.com:

You may view “Untraceable,” as I do, as a repugnant example of the voyeurism it pretends to condemn. Or you may stand back and see it as a cleverly conceived, slickly executed genre movie that ranks somewhere between “Seven” and the “Saw” movies in sadistic ingenuity.

Here’s my issue though: the concept is fatally flawed from the get go. In short, all our heroine needs to do is yank the DNS entry for the site and the game is over.

I might let something like this slip if technology were more accurately represented on a regular basis, but it’s not.

Matthew Inman has nice round up of the top 10, What code DOESN’T do in real life (that it does in the movies):

From www.drivl.com:

10. Most code is not inherently cross platform
Remember in Independence Day when whatshisface-math-guy writes a virus that works on both his apple laptop AND an alien mothership? Bullshit!
If real life were like film I’d be able to port wordpress to my toaster using a cat5 cable and a bag of glitter.

It’s All About the DNS

Domain Name Servers (DNS) might be considered the single most important aspect of the Internet, yet many people don’t know what they are and those that do probably don’t know how they work. In the end, this ends up being a good thing. But over the last week or so, they’ve unknowingly been the bane of my internship.

Domain Name Servers really serve a single purpose: they take a domain name (such as AndrewFerguson.net) and return an IP address (such as 70.96.188.33). In reality, there are many DNS which talk with each other and share information and (usually) ensure that you get to the website you’re trying to reach.

But what happens if a DNS goes down? Or actually: What happens if the person responsible for add the names of a half dozen DNS to your TCP/IP settings fails to do this? Short answer is: You can’t do any work. Long answer is: you spend days trying to figure out why you don’t have permissions to access a network share despite the fact that permissions aren’t the issue.

So yea, all fixed now. Today was probably one of my most productive days yet. I started playing around with some code to get a proof-of-concept design for DeIcer and made some great headway on that.

Java’s so weird.

In case you really want to learn more about DNS, check out HowStuffWorks and Wikipedia.