Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I want to access nodes in a network using "host.domain" notation that will be resolved by dns

Client Node: host, B1 Domain: domain

What I'm able to do:

  • Access nodes using
  • I setup a dns server with FQDN(fully qualified domain name) as in win 2008 r2
  • Added DNS A record for host with its ip
  • Now I am able to ping using

What I really want ? ping using host.domain instead of

Note: Please suggest any alternatives like linux setups as well if its not possible in windows.

share|improve this question

migrated from Sep 19 '12 at 4:44

This question came from our site for professional and enthusiast programmers.

What you describe is typically called a "single label domain" in Microsoft AD speak. You'll find that you have app compat issues as many apps make assumptions when presented with "domain" that does not have a period in it...namely, that it isn't a valid DNS domain.

So I wouldn't recommend doing this directly even though it's possible.

That said, there are a couple of other options fo ryou, depending upon your exact goal:

  • You can make hostname resolution work (ie "ping host") by just configuring DNS correctly. It would append the suffix of automagically. Maybe this is good enough?
  • You can use Netbios name resolution (typically people refer to this via an old service that implements it, called WINS) to get hostname resolution (ie make "ping host" work). By setting up WINS (typically done on the same boxes that host DNS, though not required) & having your clients register WINS records, this would start working for you. The advantage of this over DNS is that this can work across many DNS namespaces with flexibilities not often afforded to DNS (yes, yes, there are other options in modern DNS, like resolution across namespaces, global zones, etc....but it's out there).
  • You can register records in a different namespace named just "domain" and host this on your DNS servers, then register records in to it for your boxes. I'll admit I haven't configured this myself but in theory this should work. I'd be curious if ti doesn't (I can imagine a few edge cases that might be problematic, like Kerb mutual auth, if you rely on such things for your scenarios).
share|improve this answer
As domain names without a dot, other than the implied trailing dot, are perfectly valid there is no legitimate reason for any application to complain. Any that do so are defective. – John Gardeniers Sep 19 '12 at 5:40
Defective or not, that does not make said systems operable. Folks are welcome to spend months of their lives building out these sorts of environments and then chasing down every bug they find across dozens or hundreds of vendors to prove a point. My guidance is rooted in how these systems actually are implemented and the general desire that most folks have to not spend large amounts of time on issues like this one. – Eric Fleischman Sep 19 '12 at 6:27
the proper suffix is domain.local unless you are really an owner of on the Internet – kubanczyk Aug 5 '13 at 3:07

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.