Many webapps (including Zurmo) require a domain name to be set. So even when you reference it via IP, the first thing that the app does is redirect the IP to the predefined domain name. In your case obviously that domain name doesn't exist (and/or your DNS isn't giving it to you).
So what to do to work around this issue?
Well, it really depends on a number of factors re your individual circumstance:
your intentions with Zurmo
just testing it
putting it into production
the environment that you are running it in
local VM
hosted VPS
who is going to be accessing it
just you
a whole team of people
and from where
only within a LAN
anywhere online
Possibly the quickest, easiest way to get it working just for you (assuming that your Zurmo has a static IP) is to add an entry to the hosts file on your local PC (it's different depending on what OS you are using so google for relevant instructions). If you need to reset the domain name you can rerun the script that sets that:
Zurmo requires a FQDN
Many webapps (including Zurmo) require a domain name to be set. So even when you reference it via IP, the first thing that the app does is redirect the IP to the predefined domain name. In your case obviously that domain name doesn't exist (and/or your DNS isn't giving it to you).
So what to do to work around this issue?
Well, it really depends on a number of factors re your individual circumstance:
Possibly the quickest, easiest way to get it working just for you (assuming that your Zurmo has a static IP) is to add an entry to the hosts file on your local PC (it's different depending on what OS you are using so google for relevant instructions). If you need to reset the domain name you can rerun the script that sets that: