|
|
Posted by Gordon Burditt on 08/19/07 21:07
>really? the job of a name server is to be queried. do you have info on the
A whois server is not a name server. It is possible that both are
hosted on the same machine, but they are not the same thing. I
would expect that a name server would have 100 - 1000 times the
queries that a whois server would.
>'cut off' that 'most' ns servers use?
Worry about the cutoff that whois servers use, if any.
Note that, at least on my system, whois queries come with a terms
of use that does not allow high-volume automated electronic queries
except for the purpose of registering or modifying registrations
of domains, which geolocation isn't.
>i'm not saying a local db isn't a good
>idea, however see that you've avoided anything in doing so. you may well be
>able to pull out geo info from your db, but nothing's to say your local db
>isn't out of sync with actual ns server data. there's a whole bunch of
>background coordination you'd have to do in order to make sure you were in
>sync. to me, that seems more impracticle than just going to the source...at
>least until you justify your claim of 'cut off' and 'most'.
I don't know how much traffic YOU intend putting on the whois
servers, especially if you might do more than one lookup on a given
user per session (especially if they don't do cookies). It seems
to me you could reduce that a lot by putting the data in a local
db, and only going to the outside servers if, say, the age of the
local data is more than, say, 7 days from when you last got it from
a whois server. The data really shouldn't change that fast.
You should also be aware of the possibility that your web site
becomes inoperable (or just way too slow) should the whois servers
go down or become unreachable.
Navigation:
[Reply to this message]
|