Ping my server via name and not IP.

michaelk · 11-28-2018, 06:32 AM

Depends on the distribution, what services are running and how it is configured. You might be getting hostname resolution on the server using Avahi but I am only guessing.

wpeckham · 11-28-2018, 06:32 AM

Quote:

Originally Posted by hack3rcon

But from the server I can ping other computers by their names!!!
For example, I did "ping client1" from server itself:

Code:

$ ping client1
PING client1.mydomain.com (X.X.X.X) 56(84) bytes of data.
64 bytes from X.X.X.X (X.X.X.X): icmp_seq=1 ttl=128 time=0.456 ms
64 bytes from X.X.X.X (X.X.X.X): icmp_seq=2 ttl=128 time=0.196 ms

Check the other machine. Check name resolution for client1 from myserver

Code:

grep -i client1 /etc/hosts;cat /etc/resolv.conf

looking for either client1 in the hosts file OR a nameserver defined on this network. Something allows the resolution of client1 on myserver, so if we replicate that for myserver it should help. If it is the hosts file, we just need to replicate the proper line for myserver (NOT 127.0.0.1, that is loopback) or an entry on the nameserver for myserver. In both cases use the correct network interface address for myserver, not the loopback address.

If your nameserver is running DHCP and using the host name, it may already have an entry for your "myserver" under an earlier name. If that is the case I would check to see if that old name resolves. The solution may be as simple as turning myserver off and waiting out the lease time.

hack3rcon · 11-28-2018, 06:42 AM

Quote:

Originally Posted by wpeckham

Check the other machine. Check name resolution for client1 from myserver

Code:

grep -i client1 /etc/hosts;cat /etc/resolv.conf

looking for either client1 in the hosts file OR a nameserver defined on this network. Something allows the resolution of client1 on myserver, so if we replicate that for myserver it should help. If it is the hosts file, we just need to replicate the proper line for myserver (NOT 127.0.0.1, that is loopback) or an entry on the nameserver for myserver. In both cases use the correct network interface address for myserver, not the loopback address.

If your nameserver is running DHCP and using the host name, it may already have an entry for your "myserver" under an earlier name. If that is the case I would check to see if that old name resolves. The solution may be as simple as turning myserver off and waiting out the lease time.

I did:

Code:

# Generated by NetworkManager
search mydomain.com
nameserver 172.20.1.2
nameserver 172.20.2.7

wpeckham · 11-29-2018, 05:46 AM

Quote:

Originally Posted by hack3rcon

I did:

Code:

# Generated by NetworkManager
search mydomain.com
nameserver 172.20.1.2
nameserver 172.20.2.7

That indicates that the node at 172.20.1.2 is resolving names for you. Is that host on your network, or is that under control of your ISP?
If it is under your control, that is where we would add your myserver host DNS entry.

Although, if it is under your control and you do not have the knowledge needed to manage it, you might be better just adding the myserver line to all available hosts files. That is far less technical a solution.