Cannot resolve host name

[Matt_H]

INet is based on the old Commodore AS225 and socket.library API. Most networking software uses the AmiTCP bsdsocket.library API - a different interface. That might be your problem. I can't recall if AWeb supports AS225. Interworks produced a wrapper to map bsdsocket.library calls to socket.library, but I don't know how well it works.

Consider a new TCP/IP stack like Roadshow, AmiTCP, EasyNet, or MiamiDx. You might also be interested in a newer version of AWeb.

[Matt_H]

Hmm. AWeb was working correctly a few days ago?
Then maybe it is a config thing rather than an incompatibility...

[Matt_H]

That is really strange. I'm not familiar with the nuances of INet, but everything "looks" correct from what I can tell.
I'm just throwing out guesses at this point, but I wonder if it might be something with your main router? Usually gateway and DNS/nameserver are both 192.168.1.1, but I came across an issue recently where a new modem/router provided by an ISP wouldn't allow itself to be used as a nameserver. I had to manually add the external nameserver IPs as reported by the unit to my TCP/IP config. Do you get any different results with the 8.8.8.8 that utri007 suggested?

[Matt_H]

Just thought of something else to try: see if you can ping out to an external IP address instead of a hostname.

i.e., instead of 'ping google.com' try 'ping 172.217.3.110'.

If that fails, then it's a general network config problem and not just a nameserver issue.

[Matt_H]

What result do you get with typing 'which ping' in a shell?