Issue with remote client connections

John MacKenzie john at
Fri Feb 3 01:55:32 UTC 2006

Hi there, 

It was the fact that UDP 53 was not open. 

Thank you both for your help!

- John

-----Original Message-----
From: bind-users-bounce at [mailto:bind-users-bounce at] On
Behalf Of Kevin Darcy
Sent: Thursday, February 02, 2006 8:30 PM
To: bind-users at
Subject: Re: Issue with remote client connections

John MacKenzie wrote:

>Hi there,
>I've tried searching google and newgroups but couldn't find anything 
>similar to my issue, hopefully someone here can help.
> [root at samsara root]# named -v
>BIND 9.2.2-P3
>Bind is not responding to requests from external hosts.
>IPTABLES has port 53 open, I can connect to the interface port 53 from 
>local machine with no issues, however a remote client times out.
>I can telnet to port 53 from remote client and port appears open.
>Bind is listening to both my external IP address and loopback.
>When I go from a home pc, anmd nslookup , server <my hostname>
>And lookup a record from my own master Zone.
>I get request timed out messages.
Double-check IPTABLES. TCP/53 *and* UDP/53 as inbound destination and/or

outbound source.

nslookup sucks. Use a real lookup tool, e.g. "host" or "dig", not 
"nslookup". What may be tripping you up with nslookup is its stupid 
reverse-lookup dependency, i.e. if it can't do a reverse-lookup of its 
intended nameserver's IP, then it fails without doing the lookup you 

At the very least, if you're stuck with using nslookup, use the -debug 
flag so you can have some clue as to what is failing and how.

- Kevin

No virus found in this incoming message.
Checked by AVG Free Edition.
Version: 7.1.375 / Virus Database: 267.15.0/248 - Release Date: 2/1/2006

More information about the bind-users mailing list