Actually, there *could* be a bit of a problem with the DNS. Judging from
experience, the DNS queries are transmitted via UDP, which poses a bit of
a problem with masquerading. My solution has always been to setup a
nameserver on the gateway - either a caching-only nameserver, or - usually
- one that also serves to resolve the local machines' addresses - in
your case, the 10.10.10.in-addr.arpa zone. Many OS's are happier when they
have a hostname along with the local IP address :)
I do not really know if it is even possible to make DNS work with an
external server - is there some way to masquerade UDP that I've
missed?
Of course, all of the above is invalid if all the machines in the internal
network also have a 24.2.222.x IP address, in which case they would be
able to access the nameserver directly; but for some reason, I have a
feeling this is not exactly the case.
G'luck,
Peter
On Tue, 23 May 2000, John Reynolds~ wrote:
>
> [ On Tuesday, May 23, B. Carlson wrote: ]
> > I'm trying to set up FreeBSD 4.0 so I can use more than one computer
> > for the internet, I have a cable modem. I followed these steps:
> > http://freebsd.lanfear.com/howtos/firewall.html
> >
> > [snip]
> >
> > I'm trying to setup another BSD box behind the firewall, I specify
> > it with an IP of 10.10.10.2 and tell it the gateway is at 10.10.10.1
> > with a netmask of 255.255.0.0 and still point it to the DNS server
> > at 24.2.222.33, which is the server of the cable company. Is
> > there any steps in here that I have missed? Am I sending it to the
> > wrong spot?
>
[snip]
> As far as the DNS, I run named on my gateway so, my /etc/resolv.conf just
> looks like this:
>
> search home-net chnd1.az.home.com
> nameserver 192.168.1.3
>
> But, I can't imagine why you couldn't just put
>
> nameserver 24.2.222.33
>
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message
