### Author:  [@mpalmer](https://meta.discourse.org/u/mpalmer)
#### Post date: [5 Mayo, 2018 01:06 UTC](https://meta.discourse.org/t/install-problem-getaddrinfo-name-or-service-not-known/86783/2 "2018-05-05T01:06:27Z")
Check if it’s a recently-introduced Docker bug by downgrading to 18.03. Can’t say it’s likely to fix it, but it’s easy enough to try it first just in case.
Modify the app.yml to run the ping test before anything else; that’ll rule in (or out) problems with the app container itself versus network issues.
After that, you’re in `tcpdump` territory. Capture DNS packets going over `docker0` with something like `tcpdump -i docker0 -n port 53`, and make sure the packets are at least getting onto the network. Then make sure they’re getting _out_ by capturing on `enp1s0` as well – and make sure they’re gooing out with the machine’s public IP, rather than some internal IP. If the firewall’s too restrictive, the packets won’t show up at all on one of those `tcpdump`s, and if they’re on `enp1s0` but with a private IP, then the NAT config’s busted.
If the packets are going out but not coming back, there’s upstream network problems (or an `OUTPUT` rule that’s eating them at the last minute), but given you’ve got some DNS resolution on the machine, the problem’s unlikely to be there. If the DNS response packets are coming back in part of the way, then it’s incoming firewall rules that are the problem, and if they appear to be making it all the way back to `docker0`, dump the `veth` interface for the container to double-check, and if they’re there too, something’s setting up iptables rules inside the container, and you’re back to giving Docker some serious side-eye.
---
### Author:  [@pfaffman](https://meta.discourse.org/u/pfaffman)
#### Post date: [5 Mayo, 2018 01:50 UTC](https://meta.discourse.org/t/install-problem-getaddrinfo-name-or-service-not-known/86783/3 "2018-05-05T01:50:00Z")
Thanks, Matt. I am somewhat relieved that you didn’t say something like “Uh, duh, you just need to fix the permissions,” so I don’t look foolish. But, really, I’m disheartened that there’s not an obvious and quick solution.
I’m 90% sure that I did an install that worked when these machines were on my home network.
~~I guess I’ll dust off my `discourse-pin-docker` script and work down the list.~~ Well, that wasn’t it.
But, the `tcpdump` appears to have shed the necessary light! And now I see the typo in `/etc/network/interfaces` (perfectly replicated on all three servers) that was the root of the problem.
Hooray for simple (that I still don’t quite understand) networking errors!
And from there I found that I _do_ know how to get `pups` to bind to a single IP.
And soon, a few people can use a server that if it catches on fire will be down until I wake up and look at my phone.
Thanks, Matt. **My day is saved.**
---
### Author:  [@codinghorror](https://meta.discourse.org/u/codinghorror)
#### Post date: [5 Mayo, 2018 01:55 UTC](https://meta.discourse.org/t/install-problem-getaddrinfo-name-or-service-not-known/86783/4 "2018-05-05T01:55:49Z")
All this for.. a typo? How is this going to help any future readers?
---
### Author:  [@pfaffman](https://meta.discourse.org/u/pfaffman)
#### Post date: [5 Mayo, 2018 02:00 UTC](https://meta.discourse.org/t/install-problem-getaddrinfo-name-or-service-not-known/86783/5 "2018-05-05T02:00:50Z")
Yeah. A typo. I’m afraid my tale of woe is unlikely help future readers, **except** to know that you can use `tcpdump` to watch port 53. That was the saving grace.
The actual typo was somehow I copy-pasted `dns-nameservers` in twice, so I had
```plaintext
uto enp1s0
iface enp1s0 inet static
address 38.242.7.195/28
gateway 38.242.7.193
dns-nameservers dns-nameservers 1.0.0.1 1.1.1.1
```
rather than
```plaintext
dns-nameservers 1.0.0.1 1.1.1.1
```
And DNS worked all the time except, inside of docker. (Docker used only the first entry rather than using the next one if the first failed?)
---
### Author:  [@thsnyzkn](https://meta.discourse.org/u/thsnyzkn)
#### Post date: [3 Julio, 2019 15:47 UTC](https://meta.discourse.org/t/install-problem-getaddrinfo-name-or-service-not-known/86783/6 "2019-07-03T15:47:57Z")
¿Cómo podría encontrar el archivo mencionado anteriormente de _dns-nameservers_?
---
### Author:  [@pfaffman](https://meta.discourse.org/u/pfaffman)
#### Post date: [3 Julio, 2019 19:33 UTC](https://meta.discourse.org/t/install-problem-getaddrinfo-name-or-service-not-known/86783/7 "2019-07-03T19:33:26Z")
Lo siento, @thsnyzkn. ¡Eso habría sido útil de incluir!
Consulta `/etc/network/interfaces`. Si tienes una distribución de Ubuntu más reciente, es posible que en su lugar debas revisar `/etc/netplan/01-netcfg.yaml` (o algo similar en el mismo directorio); Netplan se configura de manera totalmente diferente, pero si está roto podría causar los mismos problemas.
---
### Author:  [@thsnyzkn](https://meta.discourse.org/u/thsnyzkn)
#### Post date: [3 Julio, 2019 19:43 UTC](https://meta.discourse.org/t/install-problem-getaddrinfo-name-or-service-not-known/86783/8 "2019-07-03T19:43:29Z")
No, no necesitas disculparte. De hecho, mencionaste el nombre del archivo antes de ese mensaje en tu publicación anterior. Yo lo siento por no haberlo notado. De todos modos, gracias por tu respuesta.
Sin embargo, sigo atascado con este problema y no sé cómo puedo obtener información útil del comando tcpdump de docker0; parece que se queda colgado cuando se intenta ejecutar el comando _gem update bundler_.
---
### Author:  [@JammyDodger](https://meta.discourse.org/u/JammyDodger)
#### Post date: [8 Junio, 2024 12:37 UTC](https://meta.discourse.org/t/install-problem-getaddrinfo-name-or-service-not-known/86783/9 "2024-06-08T12:37:13Z")
Este tema se cerró automáticamente después de 2226 días. Ya no se permiten nuevas respuestas.