[OOPS] Re: Best way for one-way DNS traffic

From: H. Wade Minter (minter@lunenburg.org)
Date: 02/22/01 

Date: Thu, 22 Feb 2001 14:06:16 -0500 (EST)
From: "H. Wade Minter" <minter@lunenburg.org>
To: <freebsd-security@FreeBSD.ORG>

I had postponed this message in pine, but got a case of happy fingers and
accidentally sent it. Feel free to disregard.

--Wade

On Thu, 22 Feb 2001, H. Wade Minter wrote:

> My gateway box is running a name server for my home network. Internal
> clients point to the gateway box for DNS service, and the gateway goes out
> and resolves DNS queries.
>
> I've also got an ipfw firewall on the gateway. What I'd like to do is
> make it so internal DNS works like it should, but nobody on the outside
> should be able to connect to port 53.sadm@unired.net.pe
>
>
>
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-security" in the body of the message
>

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-security" in the body of the message

Relevant Pages

  • Re: Baffling DNS Problem
    ... Narrowed it down to a local DNS problem. ... info Resolving name ok for: ... Gateway Diagnostic ... Could be either gateway or DNS issue action Automated repair: Reset network connection action Disabling the network adapter ...
    (microsoft.public.windowsxp.network_web)
  • Re: newbie lost in trying to setup NAT
    ... Also make sure you have not configured a default gateway on the private ... that sounds correct for the DNS forwarding. ... > be able to resolve both local and Internet names from this server. ...
    (microsoft.public.windows.server.networking)
  • Re: Problem(s) resolving names with natd/ipfw.
    ... Then set all the clients' primary DNS to ... that of the internal IP of your gateway. ... > The problem is that the Windows XP client CANNOT ... > access the Internet with alphabetic names (should be ...
    (freebsd-questions)
  • Re: Domain controller not found
    ... The WAN port on the gateway has an IP of 192.168.0.4. ... All internet traffic ... So the 192.168.0.1 is not longer used on any server or workstation? ... It just seems that the DNS ...
    (microsoft.public.windows.server.setup)
  • Re: .com domain not accessible from .local workstations. Server O
    ... I was able to get rid of it by resetting it up as the only gateway ... DNS server listed for both the Lan nic and the Internet nic should list ... Connection-specific DNS Suffix. ...
    (microsoft.public.windows.server.sbs)