I'll second those firsts.

Agreed, now 10.5 years later. It's never too late to learn something.

1 members found this post helpful.

Yep but it is simpler to use the "getent ahosts <hostname>" suggested above as it requires no additional configuration.

My original question was caused by the fact that HP-UX modified their version of "dig" to resolve from local files based on nsswitch.conf settings but as noted long ago that is not part of the "dig" as provided by the folks that made it as part of BIND.

Amazing after all these years this thread is still getting hits.

Hi Folks,

Same issue on CentOS 6.7

# getent host server28.example.com
> 12.13.14.15 server28.example.com server28

# host server28.example.com
> Host server28.example.com not found: 3(NXDOMAIN)

# host 12.13.14.15
> Host 12.13.14.15.in-addr.arpa. not found: 3(NXDOMAIN)

# /etc/hosts
12.13.14.15 server28.example.com server28

# /etc/nsswitch.conf
> hosts: files dns


cat /etc/resolv.conf
# Generated by NetworkManager
search example.com
nameserver 1.2.3.44
nameserver 1.2.3.55


Now its the application OSAD/jabberd/xmpp that is highly sensitive to FQDN resolving and it is not connecting due to failed DNS resolution.

so i do not have a control over how to tell application to use 'genet'.

the work around link: https://access.redhat.com/solutions/46767 recommended by 'syedwaheedz' doest help as I do not have the support with redhat so can't really see what the work around is?



Any help is highly appreciated!

The work around involves setting up dnsmasq on the local host and telling it to resolve from /etc/hosts.

I can't post what RedHat wrote but if you do a Google search for dnsmasq and /etc/hosts you'll find hits talking about this for other distros like Ubuntu that you should be able to adapt to your CentOS setup.

This link talks about how to install dnsmasq:
http://magicofubuntu.blogspot.com/20...e-dnsmasq.html

1 members found this post helpful.

Thread is marked as Solved but still open. Does closing a thread require mod intervention? If so, triggering this comment to catch moderators' attention, might want to close

Thank you guys for all the unselfish work. I have read it through and even today is a relevant interesting topic.

Ernesto

Essentially the versions of nslookup, dig and host in the "bind" package are using dns only. That's what they are distributed with and that's what they do.
Other implementations of those commands may work differently (i.e. in NIS(+)

This thread is fourteen years old. In fact when someone posted an answer after it was seven years old (oddly enough about seven years ago) I posted the thing about HP-UX' nslookup having been configured to read hosts but most other implementations not doing that.

If you're going to respond to a thread, especially an ancient one, you ought to look through the entire thread to see if the solution is already there. The other poster today was just thanking everyone for having posted before.

Even almost 15 years later the reply by Fravadona was very helpful to me - thanks a lot!
I've run into the problem several times already, and most replies I found online just stated that nslookup won't do it - what a constructive response.
Using instead, e.g., ping with a timeout is not really nice.

Meanwhile I've put the solution in a one-line script called getipaddr:
such that I can easily use it, e.g., in ~/.ssh/config:
such that the connect command can resolve also host name aliases in /etc/hosts

17 years laters, I just suscribed to thank you all !
See you in 3 years to celebrate de 20 years of this thread

Hi,

I have a W10 machine running Ubuntu 20.045/WSL and I am trying to test out nslookup, host, and dig commands. First, it suggested that I run "sudo apt install net-cools," which I did. But when I try to run "dig @127.0.0.1 google.com" or "dig --help" I get the error, "dig: parse of /etc/resolv.conf failed." Any ideas on what to do? Thanks.