3 ms·
> DNS should associate a name with an address - including what we currently call the port. This is something I really agree with. For an example that does nami
by kccqzy 5y ago
> DNS should associate a name with an address - including what we currently call the port.
This is something I really agree with. For an example that does naming right, Google's internal BNS addresses[0] in fact resolve to a host IP address plus port. Much more convenient because conceptually now a single piece of information is needed to identify a specific running instance of an application on a machine.
[0]: https://sre.google/sre-book/production-environment/ https://sre.google/sre-book/production-environment/
- icedchai 5y agoDNS supports SRV records which resolve to a host and port. They’re rarely used, however.
- MayeulC 5y agoUnfortunately web browser, web apps and websockets can only use a few ports, so if you run a service that you later want to interoperate with a web app of some sort, you don't really have a choice. In a way, ports are already becoming obsolete for some applications.
- icedchai 5y agoWeb browsers are actually quite flexible about what ports they can use. However some ISPs and “enterprise” networks will filter traffic on non-standard ports. That’s the real problem.