| Author |
Message |
Shoie13
Joined: 29 Apr 2009
Posts: 10
|
| Posted: Sun Jul 05, 2009 8:44 am Post subject: Domain Name Resolving |
|
|
I'm running an online game through my vps, and on other hosts (that I didn't set up and run myself) IPs from players connecting would resolve to their host names, however, here, all I see are IPs. I believe this is something I did not setup or something that is setup incorrectly on my end, however, I'm unsure as of where to turn to resolve the issue. Can anyone tell me how to rectify this issue?
Much thanks. |
|
| Back to top |
|
glg
Joined: 09 Jan 2009
Posts: 503
|
| Posted: Sun Jul 05, 2009 8:56 am Post subject: |
|
|
| do you have DNS servers in /etc/resolv.conf? does DNS resolution work from a command line (eg nslookup/host/dig)? |
|
| Back to top |
|
Shoie13
Joined: 29 Apr 2009
Posts: 10
|
| Posted: Sun Jul 05, 2009 9:08 am Post subject: |
|
|
glg wrote: do you have DNS servers in /etc/resolv.conf? does DNS resolution work from a command line (eg nslookup/host/dig)?
Code:
root@mud:/etc# nslookup
> root@mud:/etc# nslookup www.google.com
Server: 97.107.133.4
Address: 97.107.133.4#53
Non-authoritative answer:
www.google.com canonical name = www.l.google.com.
Name: www.l.google.com
Address: 64.233.169.103
Name: www.l.google.com
Address: 64.233.169.99
Name: www.l.google.com
Address: 64.233.169.147
Name: www.l.google.com
Address: 64.233.169.104
root@mud:/etc# host www.google.cat
cawww.google.cat CNAME www.google.com
www.google.com CNAME www.l.google.com
www.l.google.com A 64.233.169.103
www.l.google.com A 64.233.169.99
www.l.google.com A 64.233.169.147
www.l.google.com A 64.233.169.104
root@mud:/etc# cat /etc/resolv.conf
domain members.linode.com
search members.linode.com
nameserver 97.107.133.4
nameserver 207.192.69.4
nameserver 207.192.69.5
root@mud:/etc#
Firstly, I don't know if that means it's working or not, and second, I was curious if not setting my domain name in resolv.conf or somewhere else would cause this. |
|
| Back to top |
|
hoopycat
Joined: 30 Aug 2008
Posts: 1286
Location: Rochester, New York
|
| Posted: Sun Jul 05, 2009 9:19 am Post subject: |
|
|
| Often times, applications will have a setting for whether or not to do reverse lookups. Doing it in real time is relatively useless, and they can take a long time to perform. It looks like your DNS stuff is set up correctly, so I'd check your application's settings to see if there's something for that. |
|
| Back to top |
|
glg
Joined: 09 Jan 2009
Posts: 503
|
| Posted: Sun Jul 05, 2009 3:48 pm Post subject: |
|
|
hoopycat wrote: Often times, applications will have a setting for whether or not to do reverse lookups. Doing it in real time is relatively useless, and they can take a long time to perform. It looks like your DNS stuff is set up correctly, so I'd check your application's settings to see if there's something for that.
If it's not a setting, check to see if the application requires some kind of dns library that you don't have installed (eg perl's Net::DNS, aka libnet-dns-perl in debian/ubuntu). |
|
| Back to top |
|
Shoie13
Joined: 29 Apr 2009
Posts: 10
|
| Posted: Sun Jul 05, 2009 7:40 pm Post subject: |
|
|
| I tried the package and restarting my game, and I believe I'm already on 32-bit Debian, so I don't know what the problem is as the domain still would not resolve. However, I simply rewrote the socket connection part so it no longer resolves domains and I will simply see IPs. It is more convenient that way anyway, but I do appreciate the help you all gave. :) |
|
| Back to top |
|
Sophira
Joined: 10 Dec 2008
Posts: 14
|
| Posted: Mon Jul 06, 2009 11:45 am Post subject: |
|
|
| If you use Apache for a web-based game, bear in mind that by default name resolution is off. You'll want to turn it on if that's what you want. However, it's probably better to leave it off and use a log analyzer later to resolve them. |
|
| Back to top |
|
| |
