Named and IP-Filtering

Named and IP-Filtering

Post by Eric Wi » Sat, 09 Oct 1999 04:00:00



Hello,

i run a Named on my Gateway for getting resolved my internal homedomain. All
Clients just take the Named for their DNS and the Named itself connect the two
DNS at the Provider.

The great Questions: When using Port 53 for the Bind this Port must be opened
bidi from the Outside. I just degrade this Port to the Provider-DNS to get a
little security.

I dont know what happens when Named runs as its default, this will use some
unknown upper >1024 Port. To which Port will the answers come back to my
machine from the outside?

--
This posting offers only my personal meanings
ByeBye
Eric

 
 
 

Named and IP-Filtering

Post by Tom Easte » Sat, 09 Oct 1999 04:00:00



> Hello,

> i run a Named on my Gateway for getting resolved my internal homedomain. All
> Clients just take the Named for their DNS and the Named itself connect the two
> DNS at the Provider.

> The great Questions: When using Port 53 for the Bind this Port must be opened
> bidi from the Outside. I just degrade this Port to the Provider-DNS to get a
> little security.

> I dont know what happens when Named runs as its default, this will use some
> unknown upper >1024 Port. To which Port will the answers come back to my
> machine from the outside?

The source port will be 53 - the destination port will be > 1024

-Tom
--
Tom Eastep               \    Opinions expressed here

Shoreline, Washington USA  \    those of my employer


 
 
 

Named and IP-Filtering

Post by Pierre Assel » Sat, 09 Oct 1999 04:00:00



>The great Questions: When using Port 53 for the Bind this Port must be opened
>bidi from the Outside. I just degrade this Port to the Provider-DNS to get a
>little security.

I accept UDP and TCP packets from my ISP's name servers, port 53, to my
interface, ports 1024-5999 and 6010-max.  Works for me.  My named sends
queries from unprivileged ports to port 53, the replies come back from
port 53 to the originating port and the above rule lets them in.

Oops, important detail:  I run named as a slave.  In the /etc/named.conf,

        options {
                directory "/var/named";
                forward only;
                forwarders {
                        xxx.xxx.xxx.xxx;        // ISP's nameserver
                        xxx.xxx.xxx.xxx;        // backup nameserver
                };
        };
        // rest of the named.conf unchanged because I'm lazy.

This means my named forwards all queries to my ISP, without ever bothering
other nameservers on the Internet.  That's why I don't need to accept
DNS replies from the net at large.  The replies are still cached locally.

--
--Pierre Asselin, Westminster, Colorado

 
 
 

1. IP Filter/IP NAT vs IPFW/NATD

I got a serious problem here... I used to be under IPFW/NATD, but I decided
to give a try to IP Filter/IP NAT... It turns out that IP Filter fixes the
forwarding problem I had with IPFW, but I can't get the IRC DCC connections
to work under IP Filter/IP NAT (I can't send DCCs), whereas I could do it
with NATD (by using the "-use_sockets yes" and "-sameports yes" switches)...
Are there equivalents for IPNAT ?

My computer is on a reserved address (192.168.0.42) and using a FreeBSD
gateway (192.168.0.100)
--
*****************************************************
* Les ames peuvent revenir de n'importe ou pour venir hanter le net  *
*****************************************************
DarkSoul EPITA SUP E2

2. dhcpcd can't get an IP

3. Matrox Mystique ands X.

4. Whois servers UK

5. Filters, Filters, where are you Filters...

6. U20: sound (of the box, not music) - and more

7. Recipe for bridging, IP-filtering firewall?

8. Connect to linux machine together

9. ipfilter appears not to be ip-filtering!

10. how to change domain name, host name, ip address

11. Q: Does named requires a static IP and a registered domain name?

12. named and static IP to resolve domain name

13. How to find IP name knowing IP adress?