This information has moved onto our wiki: http://mapme.at/wiki/Tracking/dns
Pingback: The Future of Online Location Tracking? « blog.mapme.at
Pingback: Place based locating « blog.mapme.at
Hi there, i cant understand this. Could you help me?
This is what i did..
I typed in my browser’s address bar L12D34567.L45D67891.1319473887..dns.mapme.at
and i ended up with :
Oops! Google Chrome could not connect to l51d50326.l-0d11968.1319473887..dns.mapme.at
Could you please help me how to use this feature?
Even loading dns.mapme.at results in the same.
Please note that i used my code between timestamp and dns.mapme.at
Hi Stuart, the DNS request currently returns 127.0.0.1 as the IP address which isn’t much use, it should still have made a DNS request though and therefore logged your location. I just tried to email you a longer explanation but the email address you gave with your comment didn’t seem to work. Let me know if you’re still having problems and I’ll look into it further. We recognise that we could improve the experience when its used in a browser tho.
Thank you very much John! Your above post helped me a lot!
I now understood how it works!
Is there any limitation on how many requests can be made in a given time. I have developed an app that updates location every 2 hours, but everytime it updates 10 to 12 times in quick succession. Is it okay from your end?, so that i dont wanna end up losing my account 🙂
Hi, Sounds like it should be fine, and if we have problems, we know who to contact now!
You must be logged in to post a comment.