Ubuntu Networking :: Pinging Hostname Rather Than Hostname.local?
May 24, 2010
I'm trying to ping another Ubuntu computer on my local network. If I try doing,ping <hostname>then I get the messageping: unknown host <hostname>however, if I doping <hostname>.localthen I get a response back. I was wondering how I can change it so that I can ping without having to append .localI've installed winbind and modified my /etc/nsswitch.conf file but this has made no difference.
I have a network of 2 WinXP machines and one linux box. I have fiddled around with the settings as you do when learning. The network is working. The network neighbourhood on the WinXP machines recognise the linux box and vice versa, (the linux Places|Network recognises the 2 WinXP). I can Ping the linux box using its hostname from a WinXp. But I cannot do the reverse. I get an 'unknown host' response. I can ping the linux to itself using its hostname.
I have an ubuntu 10.04 server with hostname "abc.domain.com". However, due to migration, we had to change to hostname to something else, "xyz".
I have done changing /etc/hosts and /etc/hostname and run /etc/init.d/hostname start.
Checking the hostname and all shows it is now using hostsname of xyz. However, email sending out is still using old hostname. We have some scripts that will send out alerts like failed rsync or hdd space full to my email account. But I see the sender is still "firstname.lastname@example.org".
How do change that to xyz? I am using postfix. I have edited main.cf and restarted postfix but no go.
I'm having an issue on two Fedora Core 13 machines where I can ping others by hostname, but the hostname resolution fails whenever I use ssh/scp/vnc/etc. I can still do these things by IP address, just not by hostname. RHEL5.3 machines on the same network with the same configuration do not seem to have this problem.
Here's the not-so-quick-and-dirty description of the situation:
I know that there is a virtual router at 192.168.31.1 and another at 192.168.30.1. I also know that there is another network (let's call it 22.214.171.124) and on that network lies a number of resources. By nature of this configuration, any machine on 126.96.36.199 can be accessed by any 192.168.x.x, but not the other way around. Beyond that is out of my hands and currently out of my scope of knowledge.
I have a dnsmasq server on 188.8.131.52 that operates as a secondary nameserver, another machine out of my sphere of influence is the primary nameserver (184.108.40.206).
The secondary nameserver on 220.127.116.11 holds the hostnames of our development machines. The problem is that in some cases, while I can ping by hostname all day long, services such as ssh, scp, vncviewer, etc all fail to resolve the hostname. In other cases I can do all of these things.
Every machine has an equivalent resolv.conf:
As an example, I will show the output of a handful of my development machines:
I also included columbia as a one-way test -- even though it cannot access 30.x or 31.x, they can access it:
columbia -- physical machine, Red Hat Enterprise 5.3, IP 192.168.100.200
Okay, so here are the various outputs. Remember, nibbler, discovery, and atlantis can ALL: - Ping by IP address - Ping by hostname - ssh, scp, vnc, etc by IP addess
Additionally, the SERVFAIL reply from 18.104.22.168 is expected since my dnsmasq server is on the secondary server.
Note that the only machine that can both ping and ssh/scp/etc by hostname is nibbler, which also happens to be the only one of the three running RHEL5.3 instead of FC13. Other virtual and physical machines running on the 192.168.31.0 and 192.168.30.0 networks (all running RHEL5.3) work just like nibbler does. So the problem seems to only affect machines running FC13.
Final note: selinux is disabled, iptables is disabled, ip6tables is disabled.
Other than that, discovery is a brand-spanking-new install straight off of the FC13 DVD. atlantis has been around longer, but its just a file server so I haven't done anything too crazy to it.
ever since upgrading from karmic to lucid, i cannot ping fqdn hosts in .local tlds. nslookup & dig work, but most other utilities fail (ping, traceroute, etc...). i know .local is an invalid tld, but apple seems to have made it a defacto standard on private networks, so i'd imagine somebody else has seen this issue before... is there a simple fix that doesn't require managing hosts file entries on a bunch of systems?
I found that I needed to connect them to the same workgroup, which I now have and for the most part it works. However, for one of the computers I do not want to use a .local domain, rather I need to use a .org. But no matter what I do, other computers on the network think it is a .local hostname. Currently the /etc/hostname on the computer file is as follows:
Here is a screenshot of an ipscan done from another computer on the local area network so you can see what I'm talking about.
I can reach other hosts by means of their global addresses by either the IP address or hostname (that has the global address). What I want to (also) do is have a hostname that references the IPv6 link local IP address (an AAAA record in DNS, or just the fe80::<whatever> address in /etc/hosts) and use that host name in commands to access that host. The problem is, an interface ID is needed when making such a reference.
It sure looks like the programs just pass the host name string on to the resolver library, which does not understand the significance of the '%' even though it could find and see that the name preceding the '%' is consistent with that being an IPv6 link local address (e.g. the logic could have been "split at first % and see if preceeding name is found as a link local address and accept that if so, or ignore the split otherwise" ... but it isn't). Is there a different syntax for this ... or was it overlooked in the design of programming around IPv6?I want to be able to address a host by its link local address, while still using a mnemonic instead of having to type the IPv6 address.
I have installed Ubuntu on four machines at work and have been blown away. On my machine I have Apache setup for web development and other machines can "see" it using my IP address. I would like to have it so they can access by the name of my computer though. I have no local DNS server so I guess I need to hard code the relationship in each machine? Ideally I'd actually like to be able to use subdomains (which I use locally to avoid annoying .htaccess path problems). i.e. from another machine on the network to go to [URL].
I'm using kubuntu 9.10 desktop edition as a server and I set the IP statically, what happens is that when I ping it from another machine on the same network, I get intermittent packet loss (up to 80% and sometimes even higher). When I ping any other machine on the local network everything's fine with 0% packet loss. Packets go directly through switch, no router or anything in between.
I suspected wiring issues, but that doesn't seem to be the problem after I changed the wiring. I was connected to wireless and suspected that but no go either. Same thing when I turn wired. I just changed the ethernet card suspecting drivers but that's no good either. Iptables is a cleanslate installation, it's totally empty.
I just finished installing ubuntu server 9.10 - fairly new. I couldn't run SSH when I use IP address of the server. I've also setup DynDNS that returns responses when I ping. SSH works fine when I use the hostname of my server (leopard) but SSH doesn't work when I use IP.I was expecting IP for "eth0" something starting with 192.168.x.x as are my other computers running WIN on the same network.Any ideas why
1) Why am I not able to run SSH from IP assigned to server by DHCP. It works when I use machine hostname (leopard) 2) Why SSH isn't working from DynDNS web hostname when it responses back the ping command.
ok so when i sudo apt-get update i get a bunch of crap that says no address associated with hostname
ive googled this and changed my /etc/hosts to all sorts of things and no luck apache wont even work now either. this server is for a few websites the company i work for hosts. currently i swaped it over to another windows based comp but we want it on ubuntu.
ive heard this is dns related? and that a FQDN is needed? if so im not sure how to re write my /hosts file but as of not it looks like this:
Code: 127.0.0.1localhost 22.214.171.124speed # The following lines are desirable for IPv6 capable hosts ::1 localhost ip6-localhost ip6-loopback
I have set up an Ubuntu 10.10 server with SAMBA shares and Apache web server. Everything was working fine. Then there was a power failure and after I restarted the server the XP pc's can see the server using the hostname. They can only see it using the ip adress. I haven't change anything on server or client side. Just the restart of the server.
I have a Windows 7 machine that I have an installation of Ubuntu 10.10 via VMware and am having an issue with pinging by hostname thorugh the VM. From the Windows 7 machine I can ping by name without any issue but not with the VM. I have the VM as bridged so it is pulling all the network stuff via DHCP including the correct DNS servers. I can ping all the DNS servers and host without any issue. I have verified my /etc/resolv.conf entries are all correct.
If I run nslookup via the VM it says:
I have also verified that AVAHI is running to cache the DNS stuff and still no success.
I have a Fedora 13 desktop I have at work that I want to use to back up data off my laptop, also running Fedora 13. I can ping the hostname of the laptop from the desktop, but not the other way round. I don't think I did anything to have the laptop register its hostname with the DNS server. Since my company uses DHCP, I can't just edit the hosts file on the laptop. I want to be able to use the hostname when I mount the NFS shares for the backup. I also want to run the desktop headless so Remote Desktop needs to be able to find it. Is there a way to force the registration? If I ping the laptop's fully qualified hostname from itself, I get back the correct IP address. If I do the same thing on the desktop, it tells me it can't find its own hostname. I do have the domain name configured in the dns search path under System->Administration-Network
Right now my setup is as follows: I have an Asus Eeepc 900 running Netbook Remix named eeepc, and a media centre running 64-bit Ubuntu named media.When I try to ping or ssh into one machine from the other, for exampleCode:$ ping mediaI get an "unknown host name" error. However, pinging the device's IP address works. How do I get the computers to recognize each other's host names? Did I miss something in the setup?
At work, I recently installed FreeNAS 0.7.4919 on a computer and set it up to be a samba server. Using a Windows XP Pro SP3 computer on the same subnet as the FreeNAS server, I can ping the FreeNAS server's hostname and it works just fine. However, using an Ubuntu 10.04 computer on the same subnet as the FreeNAS server, I am unable to ping the FreeNAS server's hostname. When I try, it says "ping: unknown host [the FreeNAS server's hostname]". I can ping its IP address just fine, though. Why is it that Windows XP Pro can ping the FreeNAS server's hostname but Ubuntu 10.04 can't?Here's the output of the ifconfig command on the Ubuntu 10.04 computer:
Code: eth0 Link encap:Ethernet HWaddr 00:14:c2:cd:a6:39 inet addr:10.37.74.141 Bcast:10.37.75.255 Mask:255.255.252.0
I have Ubuntu server installed on my old machine, which has no avahi running. I want to be able to connect to it by hostname. Is it possible. I have a tp-link TL-WR941ND router, but it doesn't seem to have any related options. How can I do it? Is there another way?I know I can add them on by one to the host file, but that is not what I want. Also that wouldn't work well with DHCP, and new hosts.
I have a weird problem since yesterday that I can't solve. I can't ping / ssh my machine anymore using its hostname... says "unknown host", "network unreachable". I have no idea why - it used to work perfectly. I can still ping / ssh using the IP so it must be a problem of hostname not being resolved.
I have a dynamic IP (I'm at work...) but that doesn't seem to be the problem - network manager automatically adds a line in /etc/hosts with <mycurrentip> <hostname> (I checked, it's indeed the IP given by ifconfig and that I can use to ping/ssh).
2nd question: Another computer has a similar problem but slightly different: the hostname is resolved but points to a wrong IP (seen in ping or nslookup), different from what ifconfig returns. As a result, ping times out and ssh says "no route to host".
Here is what I am trying to do. I set up a Samba server on Ubuntu 10.10, which seems to be working (sort of).
I set it up using Webmin, which has always worked for me before.
I set up two shares, both of which are read/write and are allowing any hosts. And are set up using the default samba configuration that is provided by Webmin.
For privacy reasons I won't disclose the domains, but I will call them test.abc.com and xyz.com
I set up /media/mount as a share called [mount_a] and I also set up /media/mount_b as [mount_b]
The server's host name in my internal network is mount-box
I originally mapped it to a sub-domain of my domain abc.com via DNS, so that test.abc.com resolves to the IP address of my router; which has all the necesarry port forwarding set up.
In windows explorer in the remote location I tested it by using \test.abc.compoonani_a, this works fine and after a password prompt I can access my files. However, I do not want to use this domain name for this server, so I registered a new domain name and again via DNS mapped domain xyz.com to the IP address of my router.
Since setting up the new hostname, I cannot connect to it via Windows to access the samba share. It just won't work. When I try to connect the password prompt appears and I put in my credentials, when I submit it the window re-appears and it has appended the servername xyz.com before the username, so it reads \xyz.com<myusername>, but won't let me connect.
If I try again with the previous hostname test.abc.com, it works fine.
What am I doing wrong that it would let me connect with one hostname, and not another.
When I use Ubuntu, my DSL modem correctly gets the hostname I call my computer "mertensia", but I'm having issues with Fedora. Yet, when I look at the name assigned by the modem (using URL... in a web browser),I need the PC Name to be mertensia, because otherwise it will complicate how I ssh immensely.
I have 4 installations of Fedora 14 running on a Win 2008 R2 server in Hyper-V.
When I try to ping my desktop or the host server via the hostname from within any of the Fedora installations, the ping fails. I can ping by IP without issue. Also if I try to ping the VMs from my desktop it fails. I have an XP VM setup that I can ping without issue via hostname and IP.
All of the VMs can access the Internet without issue. I have disabled all firewalls on all systems with no luck. My desktop can ping the Hyper-V server without issue so it would appear that the problem lies with the Fedora installations.
Does anyone have anything I can try to get the name resolution working?
I am coming across a strange error with my gateway. When I do a "ping", this is what I get below:k-63a5b848c6cb4:~ # ping simba PING simba.gateway.2wire.net (192.168.1.69) 56(84) bytes of data.
64 bytes from k-63a5b848c6cb4 (192.168.1.69): icmp_seq=1 ttl=64 time=0.041 ms 64 bytes from k-63a5b848c6cb4 (192.168.1.69): icmp_seq=2 ttl=64 time=0.029 ms 64 bytes from k-63a5b848c6cb4 (192.168.1.69): icmp_seq=3 ttl=64 time=0.023 ms
I got an application deployed on Websphere Application Server on SUSE Linux V 10. We are accessing the application using the IP address in the URL. Please let me know how to configure the DNS, so that we can use the Host name in the URL and the Host name is automatically mapped to the IP address.