Name Server Question

seekuel seekuel at
Mon Jan 1 02:30:37 UTC 2007


Is there any way to determine this issue? UDP port 53 is open but TCP is closed.

On 12/30/06, Barry Margolin <barmar at> wrote:
> In article <en3jqh$1vp9$1 at>, seekuel <seekuel at>
> wrote:
> > Hello group,
> > I am new to BIND and I've configured a centos 4.4 box with bind,
> > bind-chroot, caching-nameserver installed. This box functions an
> > authoritative name server for our domain.
> >
> > I am confuse. This server is an authoritative server for our domain and
> when
> > our work station uses its public ip as the dns that workstation cannot
> > resolve other domains. This is also true in the server it self. If I edit
> > /etc/resolv.conf to or its public ip the server cannot resolve
> to
> > other domains say When I use our ISP's dns in /etc/resolv.conf
> > then it can resolve to other domains.
> >
> > This are some of my questions. In an authoritative name server, why is it
> > that even a caching-nameserver is installed and change /etc/resolv.conf to
> > the server's ip this server cannot resolve to other domain but it can
> > resolve our domain. Is there something wrong with the configurations? Im
> > willing to attach the configuration if needed.
> My guess is that your firewall is only allowing DNS out to your ISP's
> server.  When you use your own server, it tries to send DNS to the root
> servers, and this is being blocked by the firewall.
> --
> Barry Margolin, barmar at
> Arlington, MA
> *** PLEASE post questions in newsgroups, not directly to me ***
> *** PLEASE don't copy me on replies, I'll read them in the group ***

Respectfully yours,

Sandeil C. Tenebro, E.C.E.
Linux Registered User #384410

More information about the bind-users mailing list