Re:GoDaddy fires employee for bidding in domain name auctions
by indigodaddy on Friday March 29, 2019 @02:09AM
(#19519524)
Wouldn't whois from the command line also be sufficient to avoid potential malfeasance?
[ Parent
| on HN ]
Re:GoDaddy fires employee for bidding in domain name auctions
by Canada on Friday March 29, 2019 @07:53AM
(#19520789)
Yeah, but I find dig faster since all the whois servers decided they needed to also return 10 pages of legal bullshit, and easier to check a bunch of possible domains in a loop. Whois is probably more up to date as zone updates are batched so it's possible something returns NXDOMAIN but has actually been registered.
Re:GoDaddy fires employee for bidding in domain name auctions
by indigodaddy on Friday March 29, 2019 @06:30PM
(#19526193)
How are you constructing your dig? Is a null dig result always an indication of an unregistered domain?
Re:GoDaddy fires employee for bidding in domain name auctions
by Canada on Saturday March 30, 2019 @08:51AM
(#19529158)
Usually something like this:
cat /tmp/wants.txt | while read d; do echo -n $d:; dig $d in ns | grep '>>HEADER<<' | awk '{print $6}'; done
You get NXDOMAIN if it doesn't exist. That doesn't necessarily mean you can register it though. Maybe it's expired but in the grace period, or some other kind of exits-but-disabled state. If it does exist it might be for sale. Anyway, for quickly checking what's probably unregistered from the shell this one liner works great. A whois query usually takes about a second. Dig takes about a tenth of a second, and DNS queries aren't rate limited like WHOIS.