Trying to think of domain hacks: hos.tel is the only one that comes to mind. Maybe dontaskdont.tel?
in.tel ?
on a slightly related note: If you really want a free iphone steve.jobs is not registered :-)
.Tel Them Where to Find You
11–20 of 24 posts
Re: .Tel Them Where to Find You
#12I'm no expert on DNS, but this struck me: Individuals can also choose to display their location, allowing their contacts to see where they are at any given time and opening the door for location-based services. As far as I know DNS takes up to 24 hours to update all nameservers, rendering this service completely useless. Am I wrong on this?
Now I could be wrong on this, but I believe that's at the EXTREME end of things, I would say with the way DNS is updated now it usually takes under an hour at most. At least that's my personal experience.
Thanks for clarifying :-)
But under an hour still kills the concept of location based services.
Re: .Tel Them Where to Find You
#13I'm no expert on DNS, but this struck me: Individuals can also choose to display their location, allowing their contacts to see where they are at any given time and opening the door for location-based services. As far as I know DNS takes up to 24 hours to update all nameservers, rendering this service completely useless. Am I wrong on this?
Sort of. Depending on where this is actually stored it can be instantaneous -- at work we have a pair of servers that serve DNS via MySQL replication, and time from putting data into the master and seeing it in DNS is well under one second.
If they're suggesting you update the .tel TLD servers with your information, the sky's the proverbial limit, but it would be possible for them to keep it pretty tight.
The real problem with this is that there's no notion of ACLs or multiple viewports in DNS -- I reeeeeeeeeeeeeeally don't want any spammer who can find me@iigs.tel to be able to spam me with data from GPS me.iigs.tel records.
Re: .Tel Them Where to Find You
#14Trying to think of domain hacks: hos.tel is the only one that comes to mind. Maybe dontaskdont.tel?
# cat /usr/share/dict/words | grep -i tel$ | wc -l
95
hotel, motel, cartel, hostel are the ones that most people would recognize. The rest are pretty weak.
Re: .Tel Them Where to Find You
#15This is incredibly stupid. I can add any record I like to my DNS. If things start querying DNS for those records, fine. But... what is .tel bringing to the party? My DNS server which happens to be at a .org can serve any records it likes!
As CompanyX, why would I want to buy companyx.tel, instead of just sticking those records on my existing companyx.com?
Re: .Tel Them Where to Find You
#16I'm no expert on DNS, but this struck me: Individuals can also choose to display their location, allowing their contacts to see where they are at any given time and opening the door for location-based services. As far as I know DNS takes up to 24 hours to update all nameservers, rendering this service completely useless. Am I wrong on this?
You can set the TTL (time to live) of a zone to whatever value you like including zero to force every lookup to go to the authoritative servers (do not do this, it will make your site slow for users and your network administrators grouchy). Most dynamic dns providers have a default of 60 seconds.
From the article it's hard to tell exactly what they are talking about, but it sounds like any of a number of schemes for abusing DNS as a federated database.
Re: .Tel Them Where to Find You
#17Trying to think of domain hacks: hos.tel is the only one that comes to mind. Maybe dontaskdont.tel?
196 words found in http://www.instantwordsearch.com/ for tel occurring anywhere in the word.
Re: .Tel Them Where to Find You
#18Re: .Tel Them Where to Find You
#19Great idea but DNS is not exactly the most secure of protocols. Also, the current domains can already do this through arbitrary records (as has been mentioned already).
Re: .Tel Them Where to Find You
#20Earlier quoted context omitted.
Now I could be wrong on this, but I believe that's at the EXTREME end of things, I would say with the way DNS is updated now it usually takes under an hour at most. At least that's my personal experience.
Thanks for clarifying :-) But under an hour still kills the concept of location based services.
Under an hour still works for 'who is in London for dinner tonight'.