summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorRubidium <rubidium@openttd.org>2021-04-11 11:39:43 +0200
committerPatric Stout <github@truebrain.nl>2021-04-12 21:10:21 +0200
commit4fb1e34b1ed84d228ce5d88abe9a78437a3760d3 (patch)
treeda846d5a95e02368bf9e0c2cbe834126b8e84e47
parentd2fe8c2842c7930d5fca4f10bad276b706393946 (diff)
downloadopenttd-4fb1e34b1ed84d228ce5d88abe9a78437a3760d3.tar.xz
Change: add some hints about the getaddrinfo warning to the troubleshooting part of the documentation
-rw-r--r--docs/multiplayer.md7
1 files changed, 7 insertions, 0 deletions
diff --git a/docs/multiplayer.md b/docs/multiplayer.md
index 89a490602..daccbf06d 100644
--- a/docs/multiplayer.md
+++ b/docs/multiplayer.md
@@ -211,3 +211,10 @@ Last updated: 2011-02-16
communication from an admin tool reach the programme. See section 1
'Starting a server' further up for the ports and protocols used by OpenTTD.
The ports can be configured in the config file.
+
+ - My advertising server warns a lot about getaddrinfo taking N seconds
+ This could be a transient issue with your (local) DNS server, but if the
+ problem persists there is likely a configuration issue in DNS resolving
+ on your computer. This seems to be a common configuration issue for
+ Docker instances, where the DNS resolving waits for a time out of usually
+ 5 seconds.