As i see it now the problem is you're not getting a search domain from your dns-server (presumably your router).
Your resolv.conf should look like this:
# Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
# DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
nameserver 192.168.1.254 # <-- could also be 127.0.1.1, does not matter
search fritz.box # <-- THIS IS IMPORTANT
Normally with a ping the OS appends the search-string after the hostname to search on its internal network. (You'll see that
ping drobo-fs.domain.ext does work.) You should have gotten the
domain.ext automatically from the dns-server.
Now you'll need to determine what the
domain.ext is in your case. You could try
nslookup x.x.x.x where
x.x.x.x is your dns-server (router?, in my example
192.168.1.254). For me it gave a
name = fritz.box. at the end. (where
fritz.box is the
Now you can add this yourself by adding it in the connection-settings like this:
After that both
ping drobo-fs.domain.ext and
ping drobo-fs should work.
Old answer (for reference):
Why not just have the line
hosts: files dns in your
mdns4_minimal [NOTFOUND=return] and
mdns4 if you don't have a working mdns-setup in your network.
You could also try
[NOTFOUND=continue] instead of
[NOTFOUND=return] if you do have a mdns-setup in your network.