gutsy fails to resolve own ip address during boot-up

I use Condor (http://www.cs.wisc.edu/condor/) to run jobs on a cluster of machines. Condor runs a daemon on the client machine to enable two-way communication with the cluster-managing machine. When this daemon starts, it determines its own IP address and passes it to the cluster-manager. This worked perfectly in Breezy, Dapper, Edgy, and Feisty, but now in Gutsy it fails to resolve its own IP address during the boot-process. If, however, I restart this daemon after the machine has fully booted, it succeeds at resolving its own IP address. It appears, therefore, that something has changed between Feisty and Gutsy that makes the Condor daemon unable to resolve its own IP address until later in the boot process. I tried hard-coding my machine's IP address in /etc/hosts, but this makes no difference.