[LispM] What does a valid internet address look like?
Steven Nunez
steven.nunez at illation.com.hk
Sat Aug 19 01:58:01 PDT 2017
A small step forward: I know that it is not because of communication issues.
Taking Alfred's advice, I set-up a local DNS server and confirmed
connectivity, recursive look-ups, etc, but the problem persists. I had a
look at the stack trace:
And had a look at the code in neti and host.lisp. Not pretty. I am not sure
where to begin.
Regards,
* Steve
-----Original Message-----
From: Alfred M. Szmidt [mailto:ams at gnu.org]
Sent: 18 August, 2017 17:05
To: steven.nunez at illation.com
Cc: lispm at tunes.org
Subject: Re: [LispM] What does a valid internet address look like?
No, still stuck. Most recently I added the remote DNS servers as hosts in
the namespace with them listed as providing the service, like this:
HOST GOOGLE-RESOLVER
SERVICE DOMAIN TCP DOMAIN
ADDRESS INTERNET 8.8.8.8
SYSTEM-TYPE UNIX42
NICKNAME GOOGLE-DNS
SITE SINGAPORE
but still no name resolution. Very frustrating; normally the docs are
quite
good, but something is clearly wrong. I've attached the entire namespace
file here too. Maybe I'm missing something obvious.
Did you read the netio documentation? I don't have Genera setup up
currently to look. I do have a vauge recollection that DNS names are just
plain strings, i.e. "abc.com". Now, one issue might be just that Google's
DNS is not responding, or that Genera is sending garbage.
Can you check that, or use a local BIND instance?
Do nyou have a host that talks telnet somewhere? I'm sure that telnet
accepts some sort of a hostname which you could test. Many of the basic
stuff like ICMP only take an address.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: </archives/lispm/attachments/20170819/def77079/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 26873 bytes
Desc: not available
URL: </archives/lispm/attachments/20170819/def77079/attachment-0001.png>
More information about the LispM
mailing list