If you're only method to get users to reach the application at the DR location is by changing a DNS record, I don't consider this isn't an excellent/well designed failover/DR process.
In the lowest-cost scenario you should look into running the application live at both locations, with DNS records pointing to both (one A record can have multiple IPs)
There are also 3rd party DNS providers who can detect and failover the DNS record for you so it's not manual, and not a 24-hour wait, see: http://www.ultradns.com/Services/DNS-Traffic-Services/SiteBacker
...just one example
In a better but more costly scenario you would work with your colocation/datacenter provider to have an action plan in place (either automatic or manual failover) to re-route traffic hitting the public IP to go to the other location, or consider anycast, or a BGP fail-over implementation.