Date: Fri, 25 Sep 1998 11:39:46 +0930 (CST) From: "Daniel O'Connor" <doconnor@gsoft.com.au> To: Mark Murdock <fee@tetrahome.tetranet.net> Cc: stable@FreeBSD.ORG, Mike Tancsa <mike@sentex.net> Subject: Re: resolving ips? Message-ID: <XFMail.980925113946.doconnor@gsoft.com.au> In-Reply-To: <Pine.BSD/.3.91.980924133354.7245A-100000@tetrahome.tetranet.net>
next in thread | previous in thread | raw e-mail | index | archive | help
> To clarify the routing table issue, I'll explain what I meant by that. > If I type "telnet 10.1.1.1", I would not expect telnet to consult a DNS > server to do a reverse lookup on that IP. I would expect it to consult > the routing table, decide that 10.1.1.1 was either on a local subnet, > through a remote gateway, or through the default route, and route my TCP > SYN packet accordingly. By mentioning routing, I only meant that to ME, > that was the logical step after receiving an IP address. Had I give it a > host name, I would have EXPECTED it to consult DNS, and then route to the > resulting IP accordingly. I hope this sheds some light on what I meant. Well, it could be telnetd doing the reverse lookup, or tcp wrappers etc.. I personnally fixed this stuff when I had a dialup my making my named.boot file change depending on if my link is up or down.. --------------------------------------------------------------------- |Daniel O'Connor software and network engineer for Genesis Software | |http://www.gsoft.com.au | |The nice thing about standards is that there are so many of them to| |choose from. -- Andrew Tanenbaum | --------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?XFMail.980925113946.doconnor>