Date: Fri, 10 Jul 1998 22:19:47 -0500 (CDT) From: George <freebsd@mutsgo.kf7nn.com> To: Rob <robert@irrelevant.com> Cc: questions@FreeBSD.ORG Subject: RE: natd Message-ID: <199807110319.WAA07070@mutsgo.kf7nn.com>
next in thread | raw e-mail | index | archive | help
ok that pretty much sums it up, crap... i was trying to get away with having to pay $3 a month for an extra IP address. I think we could use something like this. something that knows what machine is at what internal ip address and to direct traffic to each machine accordingly. maybe just a config file that lists the machine names and internal ip's and a program that answers requests from the net for these machines. what i am gatering is if there is no DNS lookup for the name then it will not be sent to the next higher domain for dns. like this: if someone does a mail to foo.freebsd.org the internic dont have a name for foo.freebsd.org so it just tells them that,, it doesnt send them to freebsd.org to find out who foo is right? At 12:20 AM 7/11/98 +0100, you wrote: >>On 10-Jul-98 laszlo vagner wrote: >>> suppose i had a machine connected to the net with it own ip address >>> lets call it foo1.bar.com, and i had another machine connected to >>> it via ethernet lets call it foo2.bar.com, foo2.bar.com does not >>> have a ip address on the net but wants to receive mail from >>> the internet without having to pop it off of foo1.bar.com. >>> >>> can i use natd to fake the name foo2.bar.com so it looks like >>> foo2 is really on the internet at that name and foo2 wont get >>> "domain dont resolve" error messages when sending mail. >>> >>> how about if someone does a nslookup on foo2.bar.com? >>> what will they get back? >>> >At 10:56 10/07/98 +0200, Malte Lance wrote: >>If you are not authoritative for bar.com, there is no way. >>natd just rewrites IP-addr.es in such a way, that internal >>rewritten IPs are not initially accessible from outside. >>If foo1.bar.com is a registered domain, and you are authoritative >>for this domain, you have the option of extending it to foo2.foo1.bar.com >> >>Malte. >> > >You can redirect incoming smtp to an internal machine, but can;t >differentiate between machines, unless you can get your ISP to supply more >than one IP address to you. > >I have my mail server internal to my private network, where the fbsd box is >the gateway using natd. I simply use redirect_port to send any connections >to ports 25 and 110 through to the correct machine. Both >"mail.irrelevant.com" and "www.irrelevant.com" (among others) have the same >IP address, although they way they are used means they end up on different >machines. > > >snippet of natd config file says: > >interface ed1 >same_ports yes >use_sockets yes > ># pop requests to green >redirect_port tcp 192.168.0.4:110 110 > ># smtp requests to green >redirect_port tcp 192.168.0.4:25 25 > ># web requests to blue >redirect_port tcp 192.168.0.5:80 80 > > > >Rob. > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-questions" in the body of the message > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199807110319.WAA07070>