Registering DNS hostnames on an EdgeRouter

Wow\... I think I found it after just 2 hours.. While I was making some progress on development, I needed to test whether it worked on mobile.\ With the backend Laravel and frontend Nuxt running in Docker, during the SSR stage the frontend Docker container had linked the api.localhost domain to Docker, so they connected without any problems, but The real problem was that it wouldn't connect on mobile, rather than during the SSR stage. Since the last Docker update, it has changed so it automatically detects and connects to the domain without having to enter the 127.0.0.1 domain in Hosts (Traefik). I couldn't edit Hosts on mobile. (They say you can on Android, but I'm an iPhone user.) So... I tried turning on a hotspot on my Windows computer and connecting to Wi-Fi, but nothing solved the problem... (The most likely solution seemed to be the Windows hotspot, but it didn't work. Maybe it was because the network drive itself was being set up separately (?), but I couldn't connect to Docker.) And so... before I knew it, about 3 hours had passed... I solved it by forcing DNS to be set on the router.... I use an EdgeRouter, and I solved it through the DNS host names configuration here. ![](/storage/media/38/conversions/dddddd8-1024x790-webp.webp) I entered the domain I needed to connect to and the IP address of the computer running Docker in the IP Address field. So, when I made a request to that Domain while connected on mobile (Wi-Fi - EdgeRouter), it was sent to the IP address where Docker was running, 192.168.1.101. There, Traefik caught the request for that Domain and routed it to the Docker server as expected. ![](/storage/media/39/conversions/dddddddd9-1024x431-webp.webp) With this Docker update, I heard that something called virtual VAT or whatever made Ethernet faster, and I could really feel that it had gotten incredibly faster.... Also, I used to run Logs commands with Docker, but while solving this issue I found out that Docker Desktop had received a huge UI and functionality update. I used to run docker logs each time to check the status, but now I can monitor it in real time using the Logs feature in Desktop.. On top of that, the button in the upper-right corner lets me jump straight into bash. (It's incredibly convenient !!!) Well... anyway, the problem is solved... Now all that's left is to deal with the issue that seems to have changed a bit in the volume section with the Docker update... There's so much work and progress is slow, but I'll try to get it done as quickly as possible...

More posts