Okay, I'm installing aegir (0.4alpha6) on my desktop (running Ubuntu 9.10 (Desktop edition)).
I have thus far followed the install.txt.
Now I am at the point of installing the hostmaster profile. After the page where I create uid 1 access information (and other general site information) then I get an error message:
Could not resolve IP address of gandalf.travisnanek.com:8080. Either set the server name to a FQDN (Fully Qualified Domain Name) or hardcode the IP here.
The thing is, this is for my home router, not an actual domain. My house has a number of ports mapped to other ports internally (this is at the router level). In this specific case, the ip I'm using to access the computer's port 80 is the router's port 8080. I would like AEgir to interpret everything as being port 80 (for cron runs for instance) though when I create sites (with aliases to be where they will be accessed as subsites like gandalf.travisnanek.com/intranet). This should work with LAMP well, and to my knowledge it should also work with drupal multisites well, since that starts at the specific site, and gets broader and broader as it doesn't find the settings folder.
I've changed my local hosts file to use gandalf.travisnanek.com as my home router. This is ideally a way around having to set up BIND (or similar DNS management software) on each of my computers, since no matter how many guides I try to follow for that, it never quite works as it should.
The odd thing about the error message is that it says I have to set the server name to a FQDN or IP address - yet it doesn't expose any fields at all. This is on the Getting Started page.
I'm going to continue going through the installation, since there's no clear way to follow those instructions - I shall be commenting here on any thing I do that's not as per the install.txt file.

Comments
Database settings
The database settings were defaultly not able to be used - I was getting errors that it wasn't able to connect to the database as the aegir_root user.
I changed the server information to get the FQDN issue dealt with (took the information from the url I was accessing it at - changed it to 127.0.0.1).
That still didn't help matters directly anyway, so I then went to my platform settings and changed the name to exlude the port number (though this really shouldn't have any impact).
Still failed for the same reason of master database unable to be accessed - so I changed my database password (it started with an @ symbol prior) and it worked after that. Currently importing the site itself.