Unwanted resolver usage of /etc/host.conf

[Shawn Bakhtiar]

I missed what distro your using...

Here is a possible answer as to why if your running fedora core

http://lists.fedoraproject.org/pipermail/users/2006-February/274721.html

>From the man pages:

http://man7.org/linux/man-pages/man5/nsswitch.conf.5.html
NOTES       Within each process that uses nsswitch.conf, the entire  file  is  read
       only  once;  if  the  file  is later changed, the process will continue
       using the old configuration.



Did you restart and test again after you made changes to the file?
Have you set SELinux to passive by issuing the command setenforce 0

and then of course there is this:

https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/999725

also the latest release nots for NTPv4 say

NTPv4 includes three new server discovery schemes, which in most 
applications can avoid per-host configuration altogether. Two of these 
are based on IP multicast technology, while the remaining one is based 
on crafted DNS lookups. See the Automatic NTP Configuration Schemes page for further information.


If that is the case, You may simply need to restart the NTP after having DNS come up. You can set the via the systemctl functions, by making NTP require DNS before it starts up (you simply have to edit the config files in /etc/systemd








> Subject: Re: Unwanted resolver usage of /etc/host.conf
> From: bryanlharris at me.com
> Date: Sat, 23 Feb 2013 16:07:58 -0500
> To: andris at hpl.hp.com
> CC: bind-users at isc.org
> 
> 
> On Feb 22, 2013, at 10:28 PM, Andris Kalnozols <andris at hpl.hp.com> wrote:
> > I stumbled upon the /etc/host.conf file and had to add the following
> > line to get name resolution working again:
> > 
> >  order  hosts,bind
> I thought Linux should have that line by default.  Do you think someone has removed that line in the past?  Perhaps you always had a problem but it was hidden from you until the latest NTP arrived. Or maybe the new NTP is just doing something wrong.
> 
> Here is the default host.conf on the latest Slackware.  It has the line just like you needed.
> 
> http://mirrors.slackware.com/slackware/slackware64-current/source/n/network-scripts/scripts/host.conf
> 
> 
> > The other workaround was to remove "files" as a service specification
> > from `/etc/nsswitch.conf', i.e., "hosts: dns".
> 
> Now this sounds like something is broken.  Because I thought the default action is 'continue' upon any type of error.  So if you previously had the default which is "hosts: files dns" then it should have worked.
> 
> Here is the default nsswitch.conf for latest Slackware.
> 
> http://mirrors.slackware.com/slackware/slackware64-current/source/a/etc/
> 
> Good luck.
> 
> Bryan
> 
> _______________________________________________
> Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list
> 
> bind-users mailing list
> bind-users at lists.isc.org
> https://lists.isc.org/mailman/listinfo/bind-users
 		 	   		  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.isc.org/pipermail/bind-users/attachments/20130224/415c1f8f/attachment.html>