×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
Adam Glauser wrote:
Sounds like it's trying to resolve '62.243.123.106' as though it's a DNS
name. I haven't used HTTPAPI, but I'd guess that there is either a
parameter or different procedure that allows connection directly by IP.
No. GEOIP is supposed to take an IP address and tell you where (which
city/country) that IP address is located in.
It does that by contacting a web service, passing the 62.243.123.106 to
the web service, and getting back a response.
The web service is NOT looked up by IP address (nor should an HTTP URL
ever be done by IP address, IMHO! That disables virtual hosting!)
Anyway...
Anyway, the reason it's giving you an host name failure is almost
certainly because you haven't defined any DNS servers for your system i
to use when looking up internet host names. That's not a problem with
HTTPAPI -- it's a problem with your system.
More info here:
http://www.scottklement.com/httpapi/dns.html
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
