Hi.
I have set up a dedicated openttd server but the address of the server is resolved on advertise and client is forced to use the IP address and not the DNS address of the server.
Thus in an enviroment like mine which has internal DNS and external DNS set different cannot reach the server that the openttd master server has resolved, where I have the server as part of LAN address, as well as the global address for other people to connect to.
So, it's better to send the DNS name address to client and let client resolve the IP to connect to.
Request : Make server address resolve on client side
Moderator: OpenTTD Developers
Re: Request : Make server address resolve on client side
No, sending DNS names is very bad. But... I assume you have multiple IPs on your OpenTTD-server-pc? If so, use 'set server_bind <ip>' to bind to a certain IP.Hideki wrote:Hi.
I have set up a dedicated openttd server but the address of the server is resolved on advertise and client is forced to use the IP address and not the DNS address of the server.
Thus in an enviroment like mine which has internal DNS and external DNS set different cannot reach the server that the openttd master server has resolved, where I have the server as part of LAN address, as well as the global address for other people to connect to.
So, it's better to send the DNS name address to client and let client resolve the IP to connect to.
Ok, I'll be more specific.
Right now I run one openttd server at IP address 218.219.203.156 (Listed at http://servers.openttd.org)
It's no problem accessing from outside my network, but my network has DNS servers set for internal and external IP different, which means I forward the openttd ports on the router, so outside IP gets to the destination, but from inside I use the LAN IP (like 192.168.0.1) to access the server myself, but since I'm forced to access the server as a global IP from INSIDE lan, the ports don't get forwarded, thus I cannot access the server (which just says "server offline" in the server list).
So, I was wondering if all the clients can resolve the IP via DNS name.
Right now I run one openttd server at IP address 218.219.203.156 (Listed at http://servers.openttd.org)
It's no problem accessing from outside my network, but my network has DNS servers set for internal and external IP different, which means I forward the openttd ports on the router, so outside IP gets to the destination, but from inside I use the LAN IP (like 192.168.0.1) to access the server myself, but since I'm forced to access the server as a global IP from INSIDE lan, the ports don't get forwarded, thus I cannot access the server (which just says "server offline" in the server list).
So, I was wondering if all the clients can resolve the IP via DNS name.
If it is in your LAN, use the LAN setting and press Find Server, it will find your server.Hideki wrote:Ok, I'll be more specific.
Right now I run one openttd server at IP address 218.219.203.156 (Listed at http://servers.openttd.org)
It's no problem accessing from outside my network, but my network has DNS servers set for internal and external IP different, which means I forward the openttd ports on the router, so outside IP gets to the destination, but from inside I use the LAN IP (like 192.168.0.1) to access the server myself, but since I'm forced to access the server as a global IP from INSIDE lan, the ports don't get forwarded, thus I cannot access the server (which just says "server offline" in the server list).
So, I was wondering if all the clients can resolve the IP via DNS name.
Why DNS is out of the question:
Now 1 server takes 6 bytes (ip + port)
If we use DNS, it takes a lot more. And even more important: it is unsafe.
Who is online
Users browsing this forum: No registered users and 9 guests