Take the 2-minute tour ×
Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

how to open port 53 for bind on debian server?

[xxx.xxx.xxx.xxx] 53 (domain) : Connection refused

share|improve this question

migrated from stackoverflow.com Feb 8 '10 at 20:37

This question came from our site for professional and enthusiast programmers.

5 Answers 5

up vote 0 down vote accepted

"Connection refused" generally means that your connection attempt got through to the remote server--in other words, it wasn't blocked by a firewall--but the remote server doesn't have anything listening for connections on that port. If you have command-line access on the remote host, you can use netstat to make sure it actually has something listening on TCP port 53.

share|improve this answer
    
don't forget that it's actually the (ip, port) tuple that matters, not just the port number, unless the IP is 0.0.0.0 (aka INADDR_ANY). In this case, the port is listening, but on the wrong IP address. –  Alnitak Feb 9 '10 at 9:59

"Connection refused" means that BIND isn't actually running on that port, for that particular IP address.

It's a common default configuration for BIND on desktop installs to only listen on the "loopback" IP address.

In fact your netstat -an output confirms that - I can see it listening on 127.0.0.1:53 but not on 0.0.0.0:53

Have a look at /etc/named.conf and check for the listen-on directive. Mine says:

listen-on port 53 { any; };
share|improve this answer
    
thx a lot i cant give You reputation because of post is migrated from stackoverflow.com –  Kowalikus Feb 8 '10 at 22:09

Depends on the documentation for your firewall, and whether that firewall is software on the debian server or a hardware device in front of it.

share|improve this answer

Perhaps this will help http://serverfault.com/questions/51354/debian-open-port-81

53 is going to be a privileged port so you're probably not going to be able to open it without being root or using some other workaround.

share|improve this answer

netstat -an | grep "LISTEN " tcp 0 0 0.0.0.0:993 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:995 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:3306 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:587 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:2222 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:110 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:143 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:80 0.0.0.0:* LISTEN
tcp 0 0 127.0.0.1:53 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:21 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN
tcp 0 0 127.0.0.1:953 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:25 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:443 0.0.0.0:* LISTEN

port 53 isnt blocked by iptables

share|improve this answer

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.