Resolve windows host names

Contents Exit focus mode. Please rate your experience Yes No. Any additional feedback? Note hostname is the placeholder of the name of the computer that is being queried.

Note xxx. Please rate your experience Yes No. Any additional feedback? Module: DnsClient. Performs a DNS name query resolution for the specified name. Resolves this query using only the local cache. Resolves this query using only the DNS protocol. Specifies the name to be resolved. Problem: Client is unable to resolve a host name. Troubleshooting steps: If a client cannot resolve a host name, then it is best to verify the Host name resolution sequence listed above that the client should be using.

If the name does not exist in any of the resources that the client uses, then you must decide to which resource to add it. If the name exists in one of the resources, such as a DNS server or a Windows Internet Name Service WINS server and the client is not resolving the name correctly, focus your attention on troubleshooting that specific resource.

Many applications have multiple methods that they can utilize to resolve names, this is especially true of mail and database applications. Depending on the client configuration the client may bypass host name resolution. Problem: Client resolves a name very slowly, or fails to resolve a name and takes a long time to report a failure. The client will then attempt to query a second DNS server if one is configured and take the same time to fail.

There are three ways to approach this issue. If the host name is correctly entered in a host file, it will be resolved before the client attempts to query DNS. This solution works well if DNS servers are temporarily unreachable and there is a small number of host names that need to be resolved. Manually configuring Hosts files for numerous clients may be prohibitive. Even if a DNS server reports that it cannot resolve a name, this will happen much faster than if the client cannot reach a DNS server at all.

If DNS servers are configured on the client, but these servers are permanently unavailable, then remove the IP addresses of the DNS servers from the client configuration. The above command will pick up the necessary dependencies samba-winbind and samba-winbind-modules. That is all you need to do for Fedora. Once those install, you should be able to ping your Windows machine, via hostname, all you want. With this fix in place, you should also be able to connect to Windows shares via hostname and any other service you might need.

If you're working on a network landscape that consists of a mixture of platforms, these little nuances can go a very long way.

You don't want to miss our tips, tutorials, and commentary on the Linux OS and open source applications. Delivered Tuesdays.

He's covered a variety of topics for over twenty years and is an avid promoter of open source. For more news about Jack Wallen, visit his website jackwallen