On Tue, 20 Feb 2001, Tim Seifert wrote:
> By: Fred Wright <[EMAIL PROTECTED]>
> On: Tuesday, February 20, 2001, 9:13:30 AM
>
> >> Here goes, the solution was VERY simple, IF you know it: It was JUST the
> >> DNS server which on PC seems to work with an INTERN number (for example,
> >> in my case 192.168.0.1) it had to be an OUTSIDE dns number!!!! Any DNS
> >> number from a host, but ofcourse your own provider is best will do!!!!
> >> :D
>
> > That's correct for the Amiga, but it doesn't make sense that the private
> > IP would work for DNS on the PC unless there's a server at that IP. This
> > raises a couple of questions:
> >
> > 2) Is it possible that Sygate includes its own DNS server as a way of
> > handling certain naming problems, but that server was not accessible to
> > the Amiga, perhaps due to a configuration problem?
>
> I think Sygate relays DNS enquiries, so the networked computers are
> configured to find a DNS server at the gateway, and it does the actualy
> DNS enquiry. Something like that anyway. I read the poor documentation
> on an ancient version, and that seemed to be the gist of it.
That makes sense, although if it's merely a relay it still wouldn't allow
you to do rDNS lookups on LAN IP addresses. That would require that it
act as a real DNS server for those queries, and then relay others.
This still doesn't explain why the Amiga couldn't use the SyGate DNS IP.
It might be worth experimenting with MiamiDiG.
Fred Wright
--
To unsubscribe send "unsubscribe miami-talk-ml" to
"[EMAIL PROTECTED]". For help on list commands send "help" to
"[EMAIL PROTECTED]".
