named behind a firewall

Adam Lang aalang at rutgersinsurance.com
Wed Jun 6 19:44:47 UTC 2001


I think the only thing BIND can do in that regards is to allow you to use
the option "query-source port" set to 53.

Other than that, it sounds like it is an issue with your firewall you have
to work out and not BIND related.

Adam Lang
Systems Engineer
Rutgers Casualty Insurance Company
http://www.rutgersinsurance.com
----- Original Message -----
From: "Budec" <budec at qwest.net>
Newsgroups: comp.protocols.dns.bind
To: <comp-protocols-dns-bind at moderators.isc.org>
Sent: Wednesday, June 06, 2001 2:43 PM
Subject: named behind a firewall


>
> I setup named behind my firewall and forwarded UDP/TCP port -> 53 to it.
The
> DNS works for internal hosts, but external hosts get time out errors.  Any
idea
> on what I am doing wrong.  I thought the only thing named (and DNS in
general)
> was port 53...
>
> I can telnet (from external host) to firewall ip port 53 and this does
forward
> me to the internal DNS server, but things like nslookup fail.
>
> Jack
>



More information about the bind-users mailing list