• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Trouble with DNS2GO Error: Server name lookup failed?

Oakenfold

Diamond Member
Okay guys here's the message I'm getting
Error: Server name lookup failed

I'm running on a linksys 4 port router, currently I have the dns client software installed on 2 machines
one on XP PRO - which connects
The other on 98SE- so I can use PWS for my web server software(I'm very green so this is the best choice right now)
The 98SE machine is the one getting that error...
The network properties mimic each other except for the IP of course.
Any ideas? If I need to be more specific lmk!
 
Where and when do you get this error? Is this for reverse lookups? If so there isnt much you can do. A webserver shouldnt really need a dns entry at all...
 
So um.... do you have two different accounts?

Only one machine need run the client app for DNS2GO. This way it will point yourdomain.dns2go.com to your external IP.

{There is also a way to have multiple domains registered and linked to your main account so yourdomain2.dns2go.com and yourdomain3.dns2go.com, etc points to your one IP so you can host multiple websites, but your PWS doesn't support host headers.}

How are your machines connected to the Linksys?? DHCP or static? What you really need to do to set up serving is to set static IP's for all machines on your internal lan, such as 192.168.1.100 for the XP machine and 192.168.1.101 for the 98 or however you want to name them with the 192.168.1.X internal addresses. You would set the network properties on each box to look like this:

IP-192.168.1.X
Subnet-255.255.255.0
Gateway-192.168.1.1
DNS-add the DNS servers of your ISP (to find this type ipconfig /all when you're connected to the net before you change the IP settings)

Then- inside the linksys config, you need to set it to do static routing, with port forwarding. If you are serving webpages, forward port 80 the the internal IP of your win98 w/pws on it.

Question- what is the XP machine going to be doing? Will it be hosting anything or serving? If not, then don't run the DNS2GO client on that box, just put it on the 98 machine and leave the box turned on and the dns client on.

I think your second box is having problems because that account is already connected to dns2go.com's dns database.

HTH,
Matt
 
I currently have the router on DHCP but it's running half, for two boxes I have set manual IP's so that there is a static address. I'm not running two clients on two machines, only one client at a time. Now the only thing that I have thought of is that I have not run the software(IE not the DNS 2 go client heartbeat-the other one) on the 98 box, I just now realized that. I think I need to run all the software on the 98 box instead of just hearbeat(doh)..hopefully this will resolve the issue, I'll let you guys know. I just thought this was really weird because it worked for like 5 minutes and then wouldn't ever re-connect to the server.
Thanks to n0cmonkey and mattbta for your help!
 
Back
Top