incorrect lookup results

[adammc]

Hello,
Firstly let me say thanks for a FANTASTIC script.

I am in the process of installing it, doing a few tests and came across an error in the results, this happened many times.

These came up as unavailable whilst the common (.com,.net,.org) showed up available?

googlefdsfsfsdf.com.au - View Whois View Website
googlefdsfsfsdf.net.au - View Whois View Website
googlefdsfsfsdf.org.au - View Whois View Website
googlefdsfsfsdf.id.au - View Whois View Website


Is this a problem with my AU whois server?

[Patrick]

That is likely. Try using the NS Validator tool in the admin panel to troubleshoot. You can use the tool to specifically determine what the nameserver is returning to the script (and perhaps the available unavailable words have changed or maybe the nameserver has changed altogether).

[adammc]

Thanks for the reply Patiek

I think it may have been that the whois server has blocked my for 24hrs.

[jozz]

Hi, I just wanted to see if someone has actually got the .com.au domains to return the correct results. Mine always display as available even if they are taken.

I suspect this is because the nameserver returns the value "available" or "not available", so if you do a keyword search for "available" it will still find it in both return values.

Do I assume correctly, or am I just doing something wrong.

Thanks for your help.

[Patrick]

Hi, I just wanted to see if someone has actually got the .com.au domains to return the correct results. Mine always display as available even if they are taken.

I suspect this is because the nameserver returns the value "available" or "not available", so if you do a keyword search for "available" it will still find it in both return values.

Do I assume correctly, or am I just doing something wrong.

Thanks for your help.

If that is the case, then why not just change the keyword phrase?

[jozz]

Because the results you get back from the nameserver are literally "available" if it is available and "not available" if it is not available. There are no further keywords to use.
I suspect this is because whois-check.ausregistry.net.au is not a true whois server and so only displays availability. Is there a way of still utilsing this service, as I 've heard this is the only server that handles bulk .com.au queries. (Also it is the current default for .com.au in EP-Dev whois).
Also, before I forget, its a great script!

[Patrick]

I don't understand the problem. Just make the script look for NOT "not available" (click the help link next to the keyword box in the admin page for more information). Thus, the script can look for "not available" and if not found it will assume the domain is available.

The script has had this capability for a long time now.

[jozz]

Patiek I appreciate your patience in helping me.
But it seems I still can't get it to work.
The keyword(s) to look for when querying a server.
If this is found, then the script will assume the domain is available.
So this would be the word "Available", which of course will not work as it will always be returned.

If you want to make the script assume the domain is unavailable unless the keyword is found, place !!! in front of the keyword.
And this would be the same keyword "Available" which would still have the same problem.

I can't see any information on entering a NOT "not available" request here.
And I've tried entering in every combination of "Not" "Available" and "!!!" I can think of.
How do I enter NOT "Not Available"?

[Patrick]

That is a typo in the admin panel text I think. It should read:
"If you want to make the script assume the domain is available unless the keyword is found, place !!! in front of the keyword."

[Patrick]

I have checked the script logic and it appears to all be correct.

The script checks for !!! and if found sets a $boolean which then determines whether a value is reversed or not:

// determine if available

        if (eregi($keyword, $this->whoisData))

            $this->available = true && !$opposite;

        else

            $this->available = false || $opposite; 

It is likely that you are not setting BOTH the limit keyword and the normal keyword.

According to your posts, both keywords should be set to: !!!not available