By seang1
I can only seem to pass DNS traffic through on that port.
This textbox defaults to using Markdown to format your answer.
You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!
Hello,
I don’t think that it is a good idea to use the registered ports for anything custom, I would recommend avoiding using anything up to and including 1023, or over 49152. For your custom services, just pick up a port from 1024 to 49151.
But generally speaking, you need to make sure that nothing else is listening on that port before you could bind another service as you can not have more than 1 service listening on one port at the same time.
Is there a particular reason why you need to use 53 for anything else besides DNS?
Regards, Bobby
I’m security testing and the target is only allowed outbound 53. It’s not a binding problem as netstat doesn’t show anything listening and the same happens with a fresh EC2 also. I’ll dig some more tomorrow, but at least I know it’s not a digital ocean issue. Thanks
Become a contributor for community
Get paid to write technical tutorials and select a tech-focused charity to receive a matching donation.
DigitalOcean Documentation
Full documentation for every DigitalOcean product.
Resources for startups and SMBs
The Wave has everything you need to know about building a business, from raising funding to marketing your product.
The developer cloud
Scale up as you grow — whether you're running one virtual machine or ten thousand.
Get started for free
Sign up and get $200 in credit for your first 60 days with DigitalOcean.*
*This promotional offer applies to new accounts only.