-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Thu, 3 Jan 2002, Julian Opificius posted the following:
JO>Hi Gary, hope you can clarify this for me ... JO> JO>At 10:18 PM 1/3/02 -0600, you wrote: JO>>On Thu, Jan 03, 2002 at 03:57:17PM -0600 or thereabouts, Julian Opificius JO>>wrote: JO>> > Using RH 7.2, KDE - new install. JO>> JO>> > 2) I don't think my named daemon is doing anything. I have a valid hosts JO>> > file, but my windows clients - who are pointed at the linux box - can't JO>> > resolve LAN names that are in the /etc/hosts file. The daemon is running. JO>> > Is there a test method I can use? JO>> JO>>Hi Julian, A /etc/hosts file is not a named daemon. JO> JO>That much I knew ... it's a data file containing links between IPs and JO>friendly names. But who uses it? Only the host it resides on. JO>> It will not resolve JO>>name and address, only DNS does that, i.e. BIND. JO> JO>Right, but somebody uses the info in /etc/hosts, don't they? Yeah the host it sits on. JO>I thought (don't ask me where I got this idea) that bind (ie.named) looked JO>in /etc/hosts first before going to an upstream DNS server. Nope. Although Linux boxen can be told to use a hosts file first for name resolution (this is the default for RH boxen). JO>> The Hosts file will go JO>>by IP addresses only, and not names/aliases.. JO> JO>Don't know what you mean by that. Is the "hosts" file only looked at by the JO>machine upon which it resides, then? Exactly. JO>>This is more of a local JO>>protocol on a small network, versus a DNS daemon, which is more global JO>>going out onto the net, and working with several networks, and subnets. JO>>This provides for reverse name and address lookup, with SOA's (start of JO>>authority) records, etc... Now BIND will set up a local resolver and use JO>>hosts, but it just looks there first anyway... it is easier just to use JO>>hosts for a small network by IP instead of name and address resolution.. JO>>The only difference instead of saying "Bob's box", you have to punch out JO>>some octets.. <g> JO> JO>So who is it that looks at /etc/hosts then? Asked and answered. JO>Help me out here ... JO> JO>There's the DNS service, implemented by the application called bind, whose JO>daemon is called "named", right? I know what that does, SOAs, A records, JO>etc. It keeps a local, dynamic cache file with data that is aged according JO>to instructions from the upstream server. It's just that I thought it also JO>looked at the host file for local static info first. Nope. JO>Who uses /etc/resolv.conf? Another daemon? That tells the localhost where it's nameservers are. JO>Basically, how does a machine on the LAN get resolution to an IP from a JO>friendly name for JO>a) another machine on the LAN, and JO>b) a machine somewhere out on the Internet ? [csm@stealth csm]$ cat /etc/host.conf order hosts,bind You see? JO>Maybe if you could also tell me where WINS fits into all this, that would JO>help a lot too! WINS has nothing to do with DNS or the hosts file. - -- csm Dmitry is free! Boycott Adobe! Repeal the DMCA! Stop the SSSCA! -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iEYEARECAAYFAjw1NowACgkQv6Gjsf2pQ0rqUACgguFPRN+nRckta2vsQAmICY4e DgkAoKXrXx1plz9hhzJpOT7aYMpw5rxi =FQm+ -----END PGP SIGNATURE----- _______________________________________________ Redhat-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/redhat-list
