DNS Problem within Firstspot

[alan]

There is probably a problem in the FirstSpot DNS (didn't I say "might"?). But your test doesn't help the situation. Again, we need the nslookup output (that shows there is an error).
_________________
~ Patronsoft Limited ~

[Crusher]

Sorry, but I don't think it is up to me to do your testing for you. I reported what I believe to be an error within Firstspot, and I found a work-around that bypasses the Firstspot DNS server that is likely causing the problem. That really puts an end to my involvement in this issue, and it would be up to you guys to do the testing and find a solution for the problem.

[alan]

We will look into this problem. If you enconter this error again, please make sure you capture the client nslookup (set d2) output. It will certainly help us to narrow down your issue.
_________________
~ Patronsoft Limited ~

[alan]

BTW, what is your Windows version and SP that FirstSpot currently installs on?
_________________
~ Patronsoft Limited ~

[Crusher]

I have Firstspot running on Windows 7 Home Premium 32 bit.

I'll try to capture a nslookup if the problem happens again but I doubt I will be able to do it. As I mentioned, I changed the Visitor Network DNS IP and I now never see this error. Plus, even if I change back to the Firstspot DNS server IP, it always finds the correct site when you hit the "Try Again" button, so if I get an error and then do a nslookup, I suspect it will see this as a "Try Again" and not show any error. It is almost as if Firstspot has fallen asleep and needs a nudge with the second attempt.

Glad to see you are now looking into this. If I can provide further information, I would be happy to do so.

[alan]

Can you recall when was this problem first appears? In particular, did you change any setting just before this problem appear?
_________________
~ Patronsoft Limited ~

[Crusher]

I changed to a new machine running Windows 7 on April 19 and, if I remember correctly, I upgraded to the latest version (6.0.6) at the same time. The problem started immediately after that.
No, I did not change any settings from the default.

[Crusher]

Well, here we go again. I set up Firstspot on another new machine this weekend and the exact same old DNS problem showed up.
The problem is that when the Firstspot Host is configured in the DHCP category to use the (DEFAULT) DNS server IP 0.0.0.0, client machines get numerous "Cannot find Server" error messages when browsing the internet. If the Preferred DNS server IP for the Visitor Network is changed to any external DNS server IP the problem disappears.
This has now occurred on 2 new Firstspot Host machines, on 2 different ISP networks. The problem MUST be a glitch within Firstspot.

Alan, have you made any progress in determining the cause of this Firstspot problem????

[alan]

So again, did you mange to capture a nslookup output?

Also, make sure there is no firewall and other low-level software enabled in your Windows.
_________________
~ Patronsoft Limited ~

[Crusher]

So again, "it always finds the correct site when you hit the "Try Again" button, so if I get an error and then do a nslookup, I suspect it will see this as a "Try Again" and not show any error."
Nslookup is NOT going to be any assistance in finding the cause of this glitch.

As I understand it, the only thing that is really affected by using an external DNS server is the 'Logout' button on the Infobox. Is there any way around this? i.e. is there a way of re-directing the 'logout' command ?

[Crusher]

Also, in regard to a firewall or low-level software being enabled, there is none. As I have mentioned numerous times before, the ONLY thing that causes this problem is using the Firstspot default DNS Server IP 0.0.0.0

As soon as the Preferred DNS server IP for the Visitor Network is changed to any external DNS server IP the problem disappears, and NO other changes are made.

[Crusher]

Sorry, I mentioned the "logout" button in the Infobox, I meant typing "logout" in the browser address bar. My mistake. Is there any way around this so that this would still work even though the Preferred DNS Server IP is set to an external DNS Server?

[alan]

Sorry, no. You need to use FirstSpot DNS server for Instant Keywords to work.

From your symptoms, it looks like the DNS server works but not very responsive. As FirstSpot DNS server is just a relay, it relies on the stability of your backend DNS server. Please set your Internet Network Interface DNS to one entry ONLY, and then restart FirstSpot.

If you still have difficulties, we need the nslookup output (issued from both client and FirstSpot) to make further diagnosis.
_________________
~ Patronsoft Limited ~

[Crusher]

OK, thanks.
If the only thing affected by using an external DNS server is the Instant Keywords, then I guess I'll just stick with that. It isn't worth the trouble to try to figure out what Firstspot is doing wrong to cause this problem.