Date: Thu, 8 Apr 2010 21:33:50 -0400 From: Brodey Dover <doverosx@gmail.com> To: mikel king <mikel.king@olivent.com> Cc: Gary Dunn <osp@aloha.com>, freebsd-questions <freebsd-questions@freebsd.org> Subject: Re: Does NAT require DNS (named)? Message-ID: <m2t283c23cd1004081833q44862425wc0e16852f140f3bb@mail.gmail.com> In-Reply-To: <D1E8BE48-8E31-4873-B10E-2B25B6FCCB0B@olivent.com> References: <201004090034.o390Y0on016839@leka.aloha.com> <D1E8BE48-8E31-4873-B10E-2B25B6FCCB0B@olivent.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Unfortunately, still 17MB. I am going to play around with the sticks of RAM that I have installed to see if there is a chipset/motherboard issue. On Thu, Apr 8, 2010 at 8:56 PM, mikel king <mikel.king@olivent.com> wrote: > > On Apr 8, 2010, at 8:32 PM, Gary Dunn wrote: > >> On Thu, 8 Apr 2010 17:05:12 -0400 mikel king <mikel.king@olivent.com> >> wrote: >> >>> On Apr 8, 2010, at 4:57 PM, Gary Dunn wrote: >>> >>>> Continuing the saga of building a wireless access point, what is the >>>> best way to provide DNS service to the dowstream network? Seems like >>>> all I need is a simple pass-through. For that named seems like >>>> overkill. Anyone have an /etc/named/named.conf that does that? >>> >>> >>> Depends on how your internal LAN is configured. Generally if there are >>> no internal servers then you can forgo deploying a DNS server. Simply >>> setup your firewall IPFW or pf or whatever you are using to allow >>> clients to go out to the net and look names up. You will likely need a >>> dhcp server though so that your wireless clients can auto-discover the >>> appropriate network settings, but you can elect to do that manually as >>> well if it's your >>> desire. >> >> I failed to mention that the same FreeBSD box will provide file and >> printer services via Samba, all clients will be Windows Vista, and there >> will bo no other servers on the downstream network. I cannot rely on cli= ents >> editing their LMHOSTS files ... I need plug and play. Do I need a DNS se= rver >> on the downstream network for Windows clients to connect to Samba? >> -- >> Gary Dunn, Honolulu >> osp@aloha.com >> http://openslate.net/ >> http://e9erust.blogspot.com/ >> Sent from a Newton 2100 via Mail V > > Gary, > > =A0 =A0 =A0 =A0Thanks for the clarification. In this case if it were my n= etwork then > I would roll out both DNS and DHCP on this server. Honestly it will make > your life a hell of a lot easier in the long run, especially if you inten= d > on using WINS resolution for the Windows client via samba. However only > allow the DNS and DHCP services to run on the internal LAN, bind them to = an > internal IP address. > > =A0 =A0 =A0 =A0You should be fine. > > Cheers, > Mikel King > > _______________________________________________ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.o= rg" >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?m2t283c23cd1004081833q44862425wc0e16852f140f3bb>