Caching of DNS resolutions?

[GoogleCodeExporter]

* Can connect to ampache via fqdn on WiFi (resolution by local dns server)
  IE: http://ampache.myhost.com:18080/ampache/
      resolves to http://192.168.1.2:18080/ampache/
* 'Empty Response' when connecting to ampache via fqdn on EVDO, (resolution
by remote dns server)
  IE: http://ampache.myhost.com:18080/ampache/
      resolves to http://77.77.77.77:18080/ampache/
* Can connect when connecting to ampache via IP address on EVDO.
* Using the webos browser on EVDO, I _can_ get to and login to the ampache
server via the fqdn.

What version of Ampache Mobile are you using?
0.7.0

What version of Ampache Server are you using? ex: 3.5.1
3.5.3

Please provide any additional information below. (Ex. Using transcoding,
problem is specific to EVDO vs WiFi)

Does the mobile app cache DNS resolution queries?  This is really the only
thing I can think of to cause this behavior.

Original issue reported on code.google.com by blef%cod...@gtempaccount.com on 12 Feb 2010 at 5:27

[GoogleCodeExporter]

The all the App does is use the given path to create a URL (nothing is done with
DNS), any DNS caching would be handled by the OS. 

Are your ACL rules open enough to allow for EVDO login?

Original comment by bjgeiser@gmail.com on 16 Feb 2010 at 7:54

• Changed state: WontFix
• Added labels: Type-Other
• Removed labels: Type-Defect

[GoogleCodeExporter]

I tried it again and it now works using the FQDN both locally and external...  
Not
sure what changed.  I might have restarted the daemon on the server.  Thanks 
for the
quick reply/sorry for the non-issue bug.

And, of course, thanks for the free software!

Original comment by blef%cod...@gtempaccount.com on 17 Feb 2010 at 2:44