Welcome • User Guide
ToS • Privacy • Canary
Donate • Bugs • License

©2025 Poal.co

1.5K

The problem is the nigger that is docker. When you open an external port on a docker container for use inside the container, it will be paired with a port inside the container. In this case 53:53. I thought that this external port was simply for the docker container, so it would be open to my Linux environment.

BUT NOPE, THAT MAKES SENSE AND IS SAFE. What docker does, when you open an external port on a docker container, is it opens up that port for your entire device (Linux PC for me). DNS servers can be used in what's known as DNS amplification to DDOS a target. While I don't think mine was used in this manner, it was definitely scanned a couple of times with what I looked up and found out were known scam domains.

Which also means you can't have Docker container A with external port #a, and Docker container B with external port #a because both are opened on your external nic and only one thing can listen per port per device... I think, I dunno, I ran into this with a custom port a bit ago and I had to change this functionality specifically because to can't listen on the same port.

DOCKER IS A NIGGER.

The problem is the nigger that is docker. When you open an external port on a docker container for use inside the container, it will be paired with a port inside the container. In this case 53:53. I thought that this external port was simply for the docker container, so it would be open to my Linux environment. BUT NOPE, THAT MAKES SENSE AND IS SAFE. What docker does, when you open an external port on a docker container, is it opens up that port for your entire device (Linux PC for me). DNS servers can be used in what's known as DNS amplification to DDOS a target. While I don't think mine was used in this manner, it was definitely scanned a couple of times with what I looked up and found out were known scam domains. Which also means you can't have Docker container A with external port #a, and Docker container B with external port #a because both are opened on your external nic and only one thing can listen per port per device... I think, I dunno, I ran into this with a custom port a bit ago and I had to change this functionality specifically because to can't listen on the same port. DOCKER IS A NIGGER.

(post is archived)

[–] • 0 pt

You should have a firewall running on the host that controls what can access your server at which ports.

Why do you need to run a server so badly? Why won't you take time to research what you are attempting to do?

There are a-Z tutorials/walkthroughs all over the web for everything you are trying to do. Literal copy/paste type shit.

[–] • 0 pt (edited )

Because I assumed docker wasn't a nigger-tier service. But this makes sense, it's used by soycucks globally.

e; Oh, also;

Assuming the high IQ and correct move that a containerized environment communicates on 127.0.0.1 is somehow bad.

I suppose you're right, I assumed people designing systems were still high-IQ and not faggots.