When your run NETACCEPTON, it will listen on the primary network adapter, but not the loopback adapter. As a result, you cannot NETCONNECTON to "localhost" or "127.0.0.1". Instead, you must know your machine's IP address or name.
For the purpose of creating example code or writing tests, it would be convenient of "localhost" worked, as the example code/tests would work everywhere without modification. I suspect that this would also make it easier to learn how to use the networking commands, as your first experience wouldn't be how to fix a "Connection Refused" error.
Furthermore, from an API design perspective, it's natural to expect that you can connect to the local machine using "localhost" in addition to the machine's name.
The fact that NETACCEPTON doesn't listen on the loopback adapter might be an accident. The code in netwind.cpp is convoluted, but it looks like, before it does a listen(), it gets the local machine's name, then resolves that name using DNS. The resolved name, of course, only includes the IP address when the DNS server returned, which is external one. I don't know why the code is like this, but it might explain why "synchronous DNS" needed to be added. I don't think a DNS resolution should be needed.
If listening on localhost isn't possible, then adding a command to get the machine's name would enable writing sample code that runs everywhere without modification.
I have committed a change that makes NETACCEPTON listen on all of the machine's adapters, which includes the loopback adapter (localhost). This will be available in FMSLogo 7.0.0.