On Wednesday 21 February 2007, Sandy Drobic wrote: > John Andersen wrote: > > I've set up a minimal bind installation using yast on 10.2 which seems to > > do the job quite well for DNS servicing my local network. > > > > Now I want to add a host name, two actually, 1) to resolve to a specific > > public IP in another city, and one to point to an internal machine on > > my network. > > > > In the past, putting these in the hosts file of the server running bind > > would work, but this seems broken in my setup. > > The resolution is set up through /etc/nsswitch.conf. If you use "files" in > addition to dns, then you should be able to use your hosts file for dns > resolution. > > # Legal entries are: > # > # compat Use compatibility setup > # nisplus Use NIS+ (NIS version 3) > # nis Use NIS (NIS version 2), also called YP > # dns Use DNS (Domain Name Service) > # files Use the local files > # [NOTFOUND=return] Stop searching if not found so far > # > # For more information, please read the nsswitch.conf.5 manual page. > # > > hosts: files dns > networks: files dns
Yup, that's what I have, (I think that is standard). # passwd: compat group: compat hosts: files dns networks: files dns services: files protocols: files etc etc All the windows machines on the network get their dns set up by dhcp from this server, but they still can not resolve entries in hosts. They have no problem resolving names on the internet (which again, is done by the bind in the suse server). For instance: In the server's /etc/hosts I have this: 192.168.2.200 testmach And the server can ping testmach by name. But none of the windows machines can, it says unknown (the machine is reachable by IP). This is why I'm wondering if there is some other setting I'm missing in bind somewhere. -- _____________________________________ John Andersen
pgp7B2fyk8MgY.pgp
Description: PGP signature
