DNS – How to Ping a Server on a Different Network by Hostname Only

domain-name-systemmultiple-instances

have two networks that I am connected to via my computer, two different routers and all. This computer is connected to a windows domain "Domain A", I can resolve the IP from any Computer Name from CMD/Ping on the same Domain A network. But on a different NIC on the same computer, I can't resolve Domain B computers just by the host name alone, I need the FQDN (like machinename1.domain.local) when pinging Domain B computers. How can I suppress the fact that I need the FQDN?

Hope this makes sense, this is the only way that I know of how to ask this question.

Best Answer

Add the name of Domain B to your DNS Suffix Search List. Either manually through IPv4 settings -> Advanced -> DNS, or automatically through Group Policy.

Related Solutions

Unable to resolve FQDN, hostname works

From what I gather Hannes, you are using either MDT (Microsoft Deployment Toolkit) or WDS (Windows Deployment Server). In that case, when you load into the PE environment you are not going to be able to interact with the resources you are trying to by design from Microsoft. It's funny you'd ask this, because I just worked with a Microsoft consultant today on this very thing. The PE environment is designed to keep a sort of hedge, if you will, around the systems that are having an OS deployed to them. To interact with them you will need the right drivers for not only the PE environment, but also your system.

Correct me if I'm wrong, but I'm sure you're talking about MDT with PE environment loading from PXE. Let me know and I can troubleshoot further for you.

A link for reference: http://community.spiceworks.com/topic/440812-imaging-with-mdt-and-wds-networking-issues

Setting the Hostname: FQDN or Short Name?

I would choose a consistent approach across the entire environment. Both solutions work fine and will remain compatible with most applications. There is a difference in manageability, though.

I go with the short name as the HOSTNAME setting, and set the FQDN as the first column in /etc/hosts for the server's IP, followed by the short name.

I have not encountered many software packages that enforce or display a preference between the two. I find the short name to be cleaner for some applications, specifically logging. Maybe I've been unlucky in seeing internal domains like server.northside.chicago.rizzomanufacturing.com. Who wants to see that in the logs or a shell prompt?

Sometimes, I'm involved in company acquisitions or restructuring where internal domains and/or subdomains change. I like using the short hostname in these cases because logging, kickstarts, printing, systems monitoring, etc. do not need full reconfiguration to account for the new domain names.

A typical RHEL/CentOS server setup for a server named "rizzo" with internal domain "ifp.com", would look like:

/etc/sysconfig/network:
HOSTNAME=rizzo
...

/etc/hosts:
127.0.0.1   localhost localhost.localdomain localhost4 localhost4.localdomain4
::1         localhost localhost.localdomain localhost6 localhost6.localdomain6

172.16.100.13   rizzo.ifp.com rizzo

[root@rizzo ~]# hostname 
rizzo

/var/log/messages snippet:
Dec 15 10:10:13 rizzo proftpd[19675]: 172.16.100.13 (::ffff:206.15.236.182[::ffff:206.15.236.182]) - Preparing to               
 chroot to directory '/app/upload/GREEK'
Dec 15 10:10:51 rizzo proftpd[20660]: 172.16.100.13 (::ffff:12.28.170.2[::ffff:12.28.170.2]) - FTP session opened.
Dec 15 10:10:51 rizzo proftpd[20660]: 172.16.100.13 (::ffff:12.28.170.2[::ffff:12.28.170.2]) - Preparing to chroot                
to directory '/app/upload/ftp/SRRID'

Best Answer

Related Solutions

Unable to resolve FQDN, hostname works

Setting the Hostname: FQDN or Short Name?

Related Topic