?
Solved

Windows 2008 r2 host name is resolved without the domain suffix

Posted on 2011-03-22
8
Medium Priority
?
687 Views
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?
thanks
0
Comment
Question by:pozlu0
[X]
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
8 Comments
 
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?
0
 

Author Comment

by:pozlu0
ID: 35192777
Sorry.
  ping myservername get myservername and not myservername.mydomain.com
0
 

Author Comment

by:pozlu0
ID: 35192795
Sorry.
  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
0
Ransomware Attacks Keeping You Up at Night?

Will your organization be ransomware's next victim?  The good news is that these attacks are predicable and therefore preventable. Learn more about how you can  stop a ransomware attacks before encryption takes place with our Ransomware Prevention Kit!

 
LVL 37

Expert Comment

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

Author Comment

by:pozlu0
ID: 35193241
Yes
0
 

Author Comment

by:pozlu0
ID: 35193244
Yes
0
 

Accepted Solution

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

modifica.JPG
0
 

Author Closing Comment

by:pozlu0
ID: 37199852
I've found solution by mylself
0

Featured Post

Technology Partners: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

Question has a verified solution.

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

Most DNS problems are VERY easily troubleshot and identifiable if you can follow the steps a DNS query takes. I would like to share the step-by-step a DNS query takes from the origin to the destination. _____________________________________________…
There have been a lot of times when we have seen the need to enter a large number of DNS entries in a forward lookup zone. The standard procedure would be to launch the DNS Manager console, create the Zone and start adding new hosts using the New…
Monitoring a network: how to monitor network services and why? Michael Kulchisky, MCSE, MCSA, MCP, VTSP, VSP, CCSP outlines the philosophy behind service monitoring and why a handshake validation is critical in network monitoring. Software utilized …
Visualize your data even better in Access queries. Given a date and a value, this lesson shows how to compare that value with the previous value, calculate the difference, and display a circle if the value is the same, an up triangle if it increased…
Suggested Courses
Course of the Month9 days, 17 hours left to enroll

762 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