Faster, but inaccurate. There are plenty of domains that are registered, but the DNS doesn't resolve. That doesn't mean they are available to register!
Re:How to find a short domain name
by gravitronic on Saturday March 03, 2012 @10:42AM
(#3660291)
When I wrote a domain searcher script what I did was filter first by names that return are resolvable, and then whois the remainder. Reduces load on the dependent whois server whose terms of service usually say "don't run scripts against me"
That's exactly the approach I tried to suggest: Find as many correct replies first, because there certainly are hosts which names can be resolved and try the whois-approach on everything else.
Re:How to find a short domain name
by brianbreslin on Saturday March 03, 2012 @11:02AM
(#3660329)
do you think that would return too many false-positives? many of these domain search tools use an api for whois or for searching.
Error Connecting To Server: whois.crsnic.net
Maybe you should not use "whois" but just a simple "host" or "ping" to resolve whether or not a domain is free. When in doubt, you can still do an "whois", but for a heuristic approach, it would be waaay faster.