[2 days left] What’s wrong with your cloud strategy? Learn why multicloud solutions matter with Nimble Storage.Register Now


Windows 2008 r2 host name is resolved without the domain suffix

Posted on 2011-03-22
Medium Priority
Last Modified: 2012-05-11
Hello everyone,
cn i have a problem configuring an IP node cluster Windows 2008 R2
if you ping the host name is resolved without the domain suffix. If the fqdn ping
work correctly the same thing using nslookup. This problem makes
When I create a cluster on this node, the cluster is seen as hostname.hostname.
There is no way to force the resolution of the hostname + domain suffix (for
Apart from the flag in the settings of the Kingston network)? or as an alternative way of
windows 2008 r2 force to use the hosts file?
Question by:pozlu0
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 6
  • 2
LVL 37

Expert Comment

by:Neil Russell
ID: 35192726
I dont understand your question.
You say that Pinging Hostname works.
You also say that " If the fqdn ping work correctly" So pinging the FQDN works as well?

You should need to do nothing with network adapter flags at all.

What does NOT work?

Author Comment

ID: 35192777
  ping myservername get myservername and not myservername.mydomain.com

Author Comment

ID: 35192795
  ping myservername get myservername and not myservername.mydomain.com only from thwe local host the other computer in the  network ping and resolve correctly myservername as myservername.mydomain.com
What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

LVL 37

Expert Comment

by:Neil Russell
ID: 35192835
Is the machine you are on the actual nameserver?

Author Comment

ID: 35193241

Author Comment

ID: 35193244

Accepted Solution

pozlu0 earned 0 total points
ID: 35197043
the problem was the lack of presence of the extension domain.


Author Closing Comment

ID: 37199852
I've found solution by mylself

Featured Post

On Demand Webinar - Networking for the Cloud Era

This webinar discusses:
-Common barriers companies experience when moving to the cloud
-How SD-WAN changes the way we look at networks
-Best practices customers should employ moving forward with cloud migration
-What happens behind the scenes of SteelConnect’s one-click button

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

This article is intended as an extension of a blog on Aging and Scavenging by the MS Enterprise Networking Team. In brief, Scavenging is used as follows: Each record in a zone which has been dynamically registered with an MS DNS Server will have…
If you have a multi-homed DNS setup in windows, you can have issues with connectivity to the server that hosts the DNS services (or even member servers of your domain if this same DNS server is a DC). This is because windows registers all of its IPs…
In this video, Percona Director of Solution Engineering Jon Tobin discusses the function and features of Percona Server for MongoDB. How Percona can help Percona can help you determine if Percona Server for MongoDB is the right solution for …
How to fix incompatible JVM issue while installing Eclipse While installing Eclipse in windows, got one error like above and unable to proceed with the installation. This video describes how to successfully install Eclipse. How to solve incompa…
Suggested Courses

656 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question