We are happy to announce that Vesta is back under active development as of 25 February 2024. We are working on v1 candidate and expect to engage more with the community over the coming months. We are committed to open source, and we encourage contributors to help us build the future of Vesta.
nameserver not woking
nameserver not woking
Hello!
Some weeks ago I made a server for my own use. I defined at domain registrar name server, like this:
ns1.domain.com xxx.xxx.xxx.xxx
ns2.domain.com xxx xxx xxx xxx
Everything worked super ok for 2 weeks. I could add any domain without problems. But since last week, without doing something, my DNS is not solved anymore. I mean, if I define DNS from registrar panel or hosts file ( in My Computer ) I can see my domains. With name servers defined I can not see my domains and I can not ping them.
I think that my internet provider has closed some ports, but I am not sure because he said to me that they did not such thing. Could you, please, tell me which ports must be opened so my name servers ( Vestacp ) to work ok again?
The only port I know and I verified it is the 53 port and it is open.
I am new in all this, so I am sorry if I ask something that others think is a simple issue. I really appreciate your help!
It would be great if you could give me a list with the ports that must be opened so that Vestacp work ok.
Thank you very much!
Some weeks ago I made a server for my own use. I defined at domain registrar name server, like this:
ns1.domain.com xxx.xxx.xxx.xxx
ns2.domain.com xxx xxx xxx xxx
Everything worked super ok for 2 weeks. I could add any domain without problems. But since last week, without doing something, my DNS is not solved anymore. I mean, if I define DNS from registrar panel or hosts file ( in My Computer ) I can see my domains. With name servers defined I can not see my domains and I can not ping them.
I think that my internet provider has closed some ports, but I am not sure because he said to me that they did not such thing. Could you, please, tell me which ports must be opened so my name servers ( Vestacp ) to work ok again?
The only port I know and I verified it is the 53 port and it is open.
I am new in all this, so I am sorry if I ask something that others think is a simple issue. I really appreciate your help!
It would be great if you could give me a list with the ports that must be opened so that Vestacp work ok.
Thank you very much!
-
- Posts: 13
- Joined: Tue Apr 15, 2014 1:39 pm
Re: nameserver not woking
Is your server on your home connection?
Did you verify that port 53 is publicly accessible? You can use this tool to help: http://www.yougetsignal.com/tools/open-ports/
There are lots of reasons you could be having issues, it would be helpful if you posted your domains or nameservers here. http://mxtoolbox.com/ and http://intodns.com/ are useful tools to check common DNS problems.
Did you verify that port 53 is publicly accessible? You can use this tool to help: http://www.yougetsignal.com/tools/open-ports/
There are lots of reasons you could be having issues, it would be helpful if you posted your domains or nameservers here. http://mxtoolbox.com/ and http://intodns.com/ are useful tools to check common DNS problems.
Re: nameserver not woking
Thank you for answering me! I verified my ports and these ones are closed: 135, 115,139,443,445,1433,3389,5632,5900 and this report: http://www.intodns.com/datacatalog.us . I do not know which ones are for DNS propagation. Please tell me what can I do, I mean do I have the posibility to change this ports with others that are open? Thank you!
-
- Posts: 13
- Joined: Tue Apr 15, 2014 1:39 pm
Re: nameserver not woking
Hey there. Port 53 is the only one used for DNS. I can't access that port so it's an issue somewhere between or at your ISP or your server. Can you post the output of the following command?puturos wrote:Thank you for answering me! I verified my ports and these ones are closed: 135, 115,139,443,445,1433,3389,5632,5900 and this report: http://www.intodns.com/datacatalog.us . I do not know which ones are for DNS propagation. Please tell me what can I do, I mean do I have the posibility to change this ports with others that are open? Thank you!
Code: Select all
netstat -an | grep :53
You could configure bind to listen on another port, but then you would need a proxy at another location that accepted connections on port 53 and forwarded them to another port on your server. Of course that defeats the point of having your server at it's current location.
Re: nameserver not woking
Code: Select all
[@home ~]# netstat -an | grep :53
tcp 0 0 93.115.46.29:53 0.0.0.0:* LIST EN
tcp 0 0 192.168.10.254:53 0.0.0.0:* LIST EN
tcp 0 0 127.0.0.1:53 0.0.0.0:* LIST EN
tcp 0 0 93.115.46.29:80 210.193.180.19:53407 ESTA BLISHED
tcp 0 0 93.115.46.29:80 210.193.180.19:53404 ESTA BLISHED
tcp 0 0 93.115.46.29:80 210.193.180.19:53408 ESTA BLISHED
tcp 0 0 93.115.46.29:80 210.193.180.19:53405 ESTA BLISHED
tcp 0 0 93.115.46.29:80 210.193.180.19:53373 ESTA BLISHED
tcp 0 0 93.115.46.29:80 210.193.180.19:53406 ESTA BLISHED
udp 0 0 93.115.46.29:53 0.0.0.0:*
udp 0 0 192.168.10.254:53 0.0.0.0:*
udp 0 0 127.0.0.1:53 0.0.0.0:*
-
- Posts: 13
- Joined: Tue Apr 15, 2014 1:39 pm
Re: nameserver not woking
Yeah looks like all is fine on the server. When you asked your ISP if they closed any ports did you specifically ask whether they blocked incoming connections? They might have though you were talking about outgoing connections which are very unlikely to be blocked.
If you can't work with your ISP to solve the problem I suggest you use a third party DNS provider. One such provider which I've used before is Zonomi. You can host one domain with 10 records for free. This won't automatically update with changes made in Vesta, but you could write a script that uses Zonomi's API to update the records when they are changed in Vesta.
If you can't work with your ISP to solve the problem I suggest you use a third party DNS provider. One such provider which I've used before is Zonomi. You can host one domain with 10 records for free. This won't automatically update with changes made in Vesta, but you could write a script that uses Zonomi's API to update the records when they are changed in Vesta.
Re: nameserver not woking
Thank you very much for your help! I will try Zonomi. My ISP does not recognize to me that it were made some changes so I can not work with them to solve this.