Amiga.org

Amiga computer related discussion => Amiga Software Issues and Discussion => Topic started by: pneron on November 06, 2020, 12:28:43 AM

Title: Cannot resolve host name
Post by: pneron on November 06, 2020, 12:28:43 AM
I seem to be having an issue with Aweb3.3
I have my TCP/IP stack working but now getting this message:

Cannot resolve host name

I can ping google.com or any other DNS site and I get a ping back.
I can FTP to Aminet from from CLI

I have an entry in my resolv.conf file that points to my DNS server.


thoughts?
Title: Re: Cannot resolve host name
Post by: utri007 on November 06, 2020, 06:23:03 AM
have you tried change DNS to 8.8.8.8 (or any other) wich is google public?
Title: Re: Cannot resolve host name
Post by: pneron on November 06, 2020, 03:37:58 PM
No change

BTW: My IP stack is Inet-225 and when I ping from that dir via CLI, I get DNS responses back. When I FTP to anminet I can log-on.

Do I need to ASSIGN or ADD paths to DEVS: Internet dir or does Aweb "know" where Inet lives?

Thanks


Title: Re: Cannot resolve host name
Post by: Matt_H on November 06, 2020, 04:56:18 PM
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 (http://web.archive.org/web/19970131043742/http://www.iworks.com/iw/files/bsdsocket44.lha) 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 (http://aminet.net/package/comm/www/aweb3.5.09_68k_20070721).
Title: Re: Cannot resolve host name
Post by: pneron on November 06, 2020, 05:08:39 PM
Thanks Matt...I did have it running a few days ago so not sure what happened

Appreciate the bkg info
Title: Re: Cannot resolve host name
Post by: Matt_H on November 06, 2020, 06:36:15 PM
Hmm. AWeb was working correctly a few days ago?
Then maybe it is a config thing rather than an incompatibility...
Title: Re: Cannot resolve host name
Post by: pneron on November 06, 2020, 07:38:59 PM
correct...just don't know where else. Like I said, I can ping google.com or FTP into AMinet with no issues, so it seems to be at the "application" layer I **think**
I was going to try and install the version of Aweb you sent me
Title: Re: Cannot resolve host name
Post by: pneron on November 07, 2020, 12:46:29 AM
Matt and team, here's a video that I hope will shed some light

https://youtu.be/TeIvbXP-zsw

Title: Re: Cannot resolve host name
Post by: Matt_H on November 07, 2020, 04:01:25 AM
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?
Title: Re: Cannot resolve host name
Post by: pneron on November 07, 2020, 04:40:36 AM
OK, to be clear, I should try adding 8.8.8.8 to my "resolv.conf" file and see if I can get out?
Title: Re: Cannot resolve host name
Post by: kolla on November 07, 2020, 06:30:33 PM
OK, to be clear, I should try adding 8.8.8.8 to my "resolv.conf" file and see if I can get out?

If it follows normal conventions... “nameserver 8.8.8.8”
Title: Re: Cannot resolve host name
Post by: pneron on November 08, 2020, 04:21:50 AM
Same  issues:

Ping aminet.net....message "alive"
Ping google.com ....message "alive"

Resolv.conf file:
nameserver 192.168.1.1 ---> my router
nameserver  8.8.8.8


Aweb3:
cannot resolve host name

FTP aminet.net

host name lookup failure
Title: Re: Cannot resolve host name
Post by: pVC on November 08, 2020, 10:42:09 AM
I would still guess that this could be some incompatibility issue with the TCP/IP stack... why have you decided to use Inet-225? AmiTCP/IP's bsdsocket.library solution is the de-facto standard for networking software support on Amiga, and all newer stacks are also based on that, so using a stack that is based on older standards is for asking trouble sooner or later IMHO, and will restrict the sofware selection you can use.
Title: Re: Cannot resolve host name
Post by: pneron on November 08, 2020, 11:20:25 AM
Thanks...to be clear, I did not choose Inet-225, I had it running for a few years and just recently started experiencing  this issue. I am thus just trying to understand why I would now be having this issue. But it sounds like I should now move away from this TCP/IP stack?
Title: Consider buying Roadshow TCP/IP - almost certain to work
Post by: First Ninja on November 08, 2020, 01:14:10 PM
Please consider buying a copy of the Roadshow TCP/IP service. It is almost certain to work; not only does it support dynamic IP numbers using DHCP, but it is also written by AmigaOS developer Olaf 'Olsen' Barthel. In short, it's a solid product. Moreover, and unlike software like Miami, it is under active development. In fact, a maintenance version was released just a few weeks ago. Roadshow isn't expensive at all and, as always, by purchasing a copy you clearly show your support for AmigaOS software development. You'll find more information about Roadshow on its homepage (http://roadshow.apc-tcp.de/index-en.php) and on amigashop.org (https://www.amigashop.org/product_info.php?products_id=200).
Title: Re: Cannot resolve host name
Post by: pneron on November 08, 2020, 01:21:09 PM
Thank you for the info, time to "upgrade"  :D
Title: Re: Cannot resolve host name
Post by: pVC on November 08, 2020, 01:36:28 PM
Yeah, Roadshow is a good choice, but as you already have OS3.9 installed, you also should have AmiTCP/IP Genesis bundled with it, and you probably could try quickly if it'd work any better.
Title: Re: Cannot resolve host name
Post by: utri007 on November 08, 2020, 09:52:56 PM
With OS3.9 Genesis is way to go. It has nice very configurable GUI, but you need to set up static IP for it.
Title: Re: Cannot resolve host name
Post by: Matt_H on November 10, 2020, 03:50:16 AM
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.
Title: Re: Cannot resolve host name
Post by: pneron on November 10, 2020, 04:14:13 AM
ok, will try this tonight

Thanks Matt
Title: Re: Cannot resolve host name
Post by: pneron on November 10, 2020, 04:55:28 AM
yep, I get an alive but still get "cannot resolve hostname" from Aweb

BTW: I only get an alive pinging from Inet:c  and not sys: c and assume this is ok?
Also my Inet-225 dir is located DEVS: Internet and assume that also ok and don't need any paths/assign statements.


My Amiga = 192.168.1.75
Gate/router = 192.168.1.1

netstat -nr:

Dest                  Gateway
127.0.0.1          127.0.0.1   
192.168.1.75     127.0.0.1
default               192.168.1.1
192.168.1.1       192.168.1.75

My resolv.conf file:

domain 192.168.1.1
nameserver 192.168.1.1
search hsd1.ma.comcast.net


I am going to try a new version on AWEB  and see if that helps. I am going to get Roadshow.





Title: Re: Cannot resolve host name
Post by: Matt_H on November 10, 2020, 05:39:58 AM
What result do you get with typing 'which ping' in a shell?
Title: Re: Cannot resolve host name
Post by: kolla on November 10, 2020, 08:07:15 AM
And you can ping your default gateway?
You don’t write anything about the netmask, is it set to 255.255.255.0?

(I think perhaps Inet/AS-225 predates CIDR, from a time when classfull networks was still the thing)
Title: Re: Cannot resolve host name
Post by: pneron on November 10, 2020, 12:31:22 PM
Yes for the Gateway - as long as I ping from Inet: dir....otherwise I get "unknown protocol ICMP". I would assume that NOT to be a concern since the "ping" command within DEV: Internet dir is not the same as Inet: C?

netstat -nr does not show any masking info, is there another command I can use to check?


Thanks
Title: Re: Cannot resolve host name
Post by: pneron on November 11, 2020, 09:14:03 PM
While I wait for Roadshow, I ended up installing Genesis and everything works now, so I suspect (as Matt & Kolla) said, must have been a "socket" issue with Inet-225...well time to move on. Thanks for all the help
Title: AmigaOS 3.2 + Roadshow: A New Experience
Post by: First Ninja on November 11, 2020, 10:03:35 PM
Slightly off topic, but still relevant - you may want to prepare for a complete system overhaul in the near future. As you may already know, AmigaOS 3.2 is in the works. The previews previously published (https://forum.amiga.org/index.php?topic=74270.0) on the Amiga.org forum holds a clear statement - the jump from Release 3.1.4 to 3.2 will likely be the most significant jump in the history of Legacy AmigaOS, rendering the offshoot versions obsolete. Please consider a ditching your current setup for an OS 3.2 + Roadshow combination down the road; chances are you'll feel like you've acquired a brand new Amiga.
Title: Re: AmigaOS 3.2 + Roadshow: A New Experience
Post by: giZmo350 on November 11, 2020, 10:21:53 PM
- the jump from Release 3.1.4 to 3.2 will likely be the most significant jump in the history of Legacy AmigaOS, rendering the offshoot versions obsolete.

Which is why I have avoided OS3.1X..... 

Why was the title of this thread changed and by whom?
Title: Re: Cannot resolve host name
Post by: Oldsmobile_Mike on November 12, 2020, 11:31:49 PM
- the jump from Release 3.1.4 to 3.2 will likely be the most significant jump in the history of Legacy AmigaOS, rendering the offshoot versions obsolete.

This is so great.  Stealing this quote as well.  Like with any update, will probably fix a dozen bugs while introducing two dozen more.  🤣

LOL, j/k.  Best of luck to you all!  😁
Title: Re: Cannot resolve host name
Post by: olsen on November 15, 2020, 04:51:08 PM

...

My resolv.conf file:

domain 192.168.1.1
nameserver 192.168.1.1
search hsd1.ma.comcast.net


Sorry, I'm just reading this thread right now: this "resolv.conf" file has issues :(

The "domain" option should be a domain name, such as "example.com" (which is just an example) and not an IP address. You use the "domain example.com" if your computer is part of a local network and you don't want to add "example.com" to every host name in the same network whenever you type it. Instead of, for example, "router.example.com" you then just enter "router" and the name resolution will automatically add "example.com" to it. If you have "192.168.1.1" in there, then the name lookup translates it into "router.192.168.1.1" which is not a valid domain name. You don't necessarily need to add a "domain" option to the "resolv.conf" file.

The "search" option is a more powerful replacement for the "domain" option. Where the "domain" option can take care of just one single local domain, the "search" option allows you to provide multiple domains to search for. As with the "domain" option, you don't necessarily need this. If you enter "ping example", then the name lookup will translate this into "ping example.hsd1.ma.comcast.net", which is not useful.

As far as I can tell, you only need to have a single "nameserver" option in your "resolv.conf" file, and nothing else.

If I remember correctly, INet-225 as a product is about as old as AmiTCP V4. The features of both TCP/IP stacks should be similar, drawing upon technology of the same age (1990-1992).

Some things have changed greatly since these TCP/IP stacks were released, and how DNS server responses look like is one of them.

I suspect that changing the INet-225 "resolv.conf" file may not have much of an impact on your name resolution issues. If I remember correctly, the AmiTCP V4 and INet-225 TCP/IP stack defaults restrict IP datagram sizes to the small end (576 bytes?), which was how things were in the early 1990'ies. This used to be sufficient for DNS lookups back then, but today's DNS zones tend to feature many more records and those records can be much longer than they used to be (e.g. signature information for DKIM, multiple IPv4 and IPv6 addresses corresponding to the same name).

This means that your name resolution could fail because the name resolution feature in your Amiga TCP/IP stack does not expect the DNS lookup response to be so large. The limitations of the DNS lookup library buffer sizes as these existed in the early 1990'ies may play a part here, too.
Title: Re: Cannot resolve host name
Post by: pneron on November 15, 2020, 05:18:55 PM
Thanks for the bkg info, I am online now. I gave up trying to get Inet to work and went with Genesis stack and it works fine. I also order Roadshow which I will test at some point