Error message on pointing name servers - what does it mean?

"Server doesn't listen/answer on port 53 for TCP protocol"

[itnecor]

I've tried to point the domain name but I've get the below message. What does it mean? How to resolve this? Please help!

Test: Server doesn't listen/answer on port 53 for TCP protocol.

[Webwork]

I'm not expert but if memory serves me correctly you can configure a server to respond to certain protocols on certain ports.

So, in other words, somewhere in your server configuration there is a mismatch between the port that IS configured to "listen" for TCP requests and an application that is attempting to access that port via TCP.

Anyone more expert can step right up. :)

[John Carpenter]

It could be caused many things. For instance,

1) Firewall blocking the port
2) No name server software running (Apache is the web server, BIND [isc.org] is an example of a name server).
3) etc.

If you use managed hosting, they should be able to fix this. If you use unmanaged hosting, maybe you should consider managed one.

[MamaDawg]

If it's any help, port 53 is the "well known port" for DNS - maybe you're not pointing to a valid name server?

[edited by: MamaDawg at 8:23 pm (utc) on Aug. 18, 2006]

[jtara]

maybe you're not pointing to a valid name server

That's the most likely scenario.

You may have some confusion as to just what is done by "pointing" the domain. I assume that you are doing this at your domain registrar?

The pointer(s) at the domain registrar point to your DNS servers, NOT your website. The DNS servers have to be configured with DNS records for your web site, mail server(s) (if any) etc.

You might be provided with DNS servers by your registrar, by your web hosting company, or you might get DNS service from a third party.

The DNS servers should be configured BEFORE you set the pointer(s) at the registrar.