Forums
New posts
New posts
Search forums
Market
Domains/Websites Wanted
.com Domain Market
gTLD Domain Market
ccTLD Domain Market
Web3 Domain Market
Third-Level Domain Market
Adult Domain Market
What's New
New profile posts
Latest activity
Members
Current visitors
New profile posts
Search profile posts
Account Upgrade
Premium Members Directory
Log in
Register
What's New
calendar
Search
Search
Search titles only
By:
New posts
New posts
Search forums
Menu
Log in
Register
Install the app
Install
Enjoy unlimited access to all forum features for FREE! Optional upgrade available for extra perks.
Forums
Domain Discussion
Domain Beginners and Newbies
Best Domain Availability Checking Apis?
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Reply to thread
Message
<blockquote data-quote="katherine" data-source="post: 2216850" data-attributes="member: 63835"><p>I have a trick to speed up the work <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite2" alt=";)" title="Wink ;)" loading="lazy" data-shortname=";)" /> It's a bit technical but it works like this:</p><p>rather than check domain availability the 'classic' way, you could have a script that does a DNS query against each domain.</p><p>For example: in Linux the command line</p><p>[CODE]dig -t ns domain.com[/CODE]</p><p>returns something like this:</p><p>[CODE]</p><p>; <<>> DiG 9.8.2rc1-RedHat-9.8.2-0.23.rc1.el6_5.1 <<>> -t ns domain.com</p><p>;; global options: +cmd</p><p>;; Got answer:</p><p>;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 50682</p><p>;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 0</p><p></p><p>;; QUESTION SECTION:</p><p>;domain.com. IN NS</p><p></p><p>;; ANSWER SECTION:</p><p>domain.com. 60 IN NS ns3.domain.com.</p><p>domain.com. 60 IN NS ns2.domain.com.</p><p>...</p><p>[/CODE]</p><p>It's the list of name servers defined for the domain name.</p><p></p><p>Short version:</p><p>[CODE]dig -t ns +short domain.com[/CODE]</p><p>Result:</p><p>[CODE]</p><p>ns3.domain.com.</p><p>ns2.domain.com.</p><p>[/CODE]</p><p>NS: the output may be polluted by error messages, you have to handle errors.</p><p></p><p>Two possible outcomes:</p><ol> <li data-xf-list-type="ol">at least one name server returned => the domain exists</li> <li data-xf-list-type="ol">no name servers returned => the domain does not exist OR the domain has no name servers OR the domain name is suspended, expiring OR DNS error...</li> </ol><p>You don't have to do the command line, you can use other scripts or libraries instead.</p><p>DNS queries are fast, and there are no quotas unlike whois lookups. They can (should) be performed in parallel, which will dramatically the time needed to complete the task...</p><p></p><p>Then you only have to check the domains for which no NS were returned, to double check their status. That list will be significantly shorter. You get the idea.</p></blockquote><p></p>
[QUOTE="katherine, post: 2216850, member: 63835"] I have a trick to speed up the work ;) It's a bit technical but it works like this: rather than check domain availability the 'classic' way, you could have a script that does a DNS query against each domain. For example: in Linux the command line [CODE]dig -t ns domain.com[/CODE] returns something like this: [CODE] ; <<>> DiG 9.8.2rc1-RedHat-9.8.2-0.23.rc1.el6_5.1 <<>> -t ns domain.com ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 50682 ;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 0 ;; QUESTION SECTION: ;domain.com. IN NS ;; ANSWER SECTION: domain.com. 60 IN NS ns3.domain.com. domain.com. 60 IN NS ns2.domain.com. ... [/CODE] It's the list of name servers defined for the domain name. Short version: [CODE]dig -t ns +short domain.com[/CODE] Result: [CODE] ns3.domain.com. ns2.domain.com. [/CODE] NS: the output may be polluted by error messages, you have to handle errors. Two possible outcomes: [LIST=1] [*]at least one name server returned => the domain exists [*]no name servers returned => the domain does not exist OR the domain has no name servers OR the domain name is suspended, expiring OR DNS error... [/LIST] You don't have to do the command line, you can use other scripts or libraries instead. DNS queries are fast, and there are no quotas unlike whois lookups. They can (should) be performed in parallel, which will dramatically the time needed to complete the task... Then you only have to check the domains for which no NS were returned, to double check their status. That list will be significantly shorter. You get the idea. [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
Domain Discussion
Domain Beginners and Newbies
Best Domain Availability Checking Apis?
Top
Bottom