02-12-2024, 06:56 AM
Good day. I have encountered a significant limitation in iventoy. The
problem is that iventoy does not support setting up a DNS name. The
issue arises during the Ubuntu installation process when the
installation scripts reference the internal IP, but I intend to use it
behind NAT. For example, I am running it in a Docker container with
the interface IP of 172.70.20.2. I have a public IP on the router, and
I am redirecting it to 172.70.20.2 using NAT. Ubuntu boots up, the
installation begins, but then the installer tries to reach
172.70.20.2, which is not accessible. It should instead reach out
using a DNS name or directly using the public IP. I would be grateful for any suggestions on how to bypass this
limitation.
problem is that iventoy does not support setting up a DNS name. The
issue arises during the Ubuntu installation process when the
installation scripts reference the internal IP, but I intend to use it
behind NAT. For example, I am running it in a Docker container with
the interface IP of 172.70.20.2. I have a public IP on the router, and
I am redirecting it to 172.70.20.2 using NAT. Ubuntu boots up, the
installation begins, but then the installer tries to reach
172.70.20.2, which is not accessible. It should instead reach out
using a DNS name or directly using the public IP. I would be grateful for any suggestions on how to bypass this
limitation.