I think there is massive confusion going on here.  

>From what I can remember of your thread, I don't know why someone
recommended that you run named (bind).  I don't think you need it. 

/etc/resolv.conf is used for when you try to resolve a name.  that is
necessary on any computer connected to the internet.  It has nothing to
do with named.

named is for if you want to run a name server, to serve requests for a
particular domain (or a caching name server) - you don't need it!  It's
a pita to set up if you're not familiar with it, anyway.

All you should need to do is put a good name server in /etc/resolv.conf
- usually your ISP's.  You can test your name server by doing (dig does
the same thing, but it's output is a bit more complicated)

$> host google.com 209.46.63.1

If it returns addresses, it's working (works for me).  Throw that IP of
your name server in /etc/resolv.conf, and you're good to go.

If i'm misunderstanding your problem, let me know.  It sounds to me that
you're making it much more difficult than it is.

> Once I get named running, I can add GoFasts second DNS machine to the 
> resolv.conf file, and see how that goes.

What?  You can add a second DNS server to resolv.conf anytime. 

What exactly is not working?

Dan

On Fri, Oct 29, 2004 at 10:45:31AM -0500, Chris Schumann wrote:
> Again, thanks for all the help so far.
> 
> The thing that I keep coming to is that it appears named is not running on 
> this machine.
> 
> "service named xxx", where xxx is anything gives me no output. 
> /etc/init.d/named xxx gives no output.
> 
> GoFast is my provider, and /etc/resolv.conf contains just the one 
> nameserver for them: 209.46.63.1. Since I'm not running named (or am I?) I 
> can't imagine the content of that file matters.
> 
> ps gives no named, pidof named returns nothing.
> 
> Here's the beginning of /etc/init.d/named, where it apparently just quits:
> #!/bin/bash
> #
> # named           This shell script takes care of starting and stopping
> #                 named (BIND DNS server).
> #
> # chkconfig: - 55 45
> # description: named (BIND) is a Domain Name Server (DNS) \
> # that is used to resolve host names to IP addresses.
> # probe: true
> 
> # Source function library.
> . /etc/rc.d/init.d/functions
> 
> # Source networking configuration.
> . /etc/sysconfig/network
> 
> RETVAL=0
> prog="named"
> 
> # Check that networking is up.
> [ "${NETWORKING}" = "no" ] && exit 0
> 
> [ -r /etc/sysconfig/named ] && . /etc/sysconfig/named
> 
> [ -x /usr/sbin/named ] || exit 0 
> 
> [ -r ${ROOTDIR}/etc/named.conf ] || exit 0 
> 
> 
> start() {
> 
> <<< end of excerpt
> 
> It should be standard Red Hat issue.
> /etc/sysconfig/named exists and has only comments.
> /usr/sbin/named exists and is executable.
> 
> Aha. /etc/named.conf did not exist. I made a blank file, and service named 
> now prints "rndc: connect failed: connection refused".
> 
> I'd appreciate a pointer to a quick and dirty HOWTO on DNS. I've looked at 
> one pretty bad page, so pointers to a good one would be nice.
> 
> Once I get named running, I can add GoFasts second DNS machine to the 
> resolv.conf file, and see how that goes.
> 
> Chris Schumann
> 
> 
> _______________________________________________
> TCLUG Mailing List - Minneapolis/St. Paul, Minnesota
> Help beta test TCLUG's potential new home: http://plone.mn-linux.org
> Got pictures for TCLUG? Beta test http://plone.mn-linux.org/gallery
> tclug-list at mn-linux.org
> https://mailman.real-time.com/mailman/listinfo/tclug-list

_______________________________________________
TCLUG Mailing List - Minneapolis/St. Paul, Minnesota
Help beta test TCLUG's potential new home: http://plone.mn-linux.org
Got pictures for TCLUG? Beta test http://plone.mn-linux.org/gallery
tclug-list at mn-linux.org
https://mailman.real-time.com/mailman/listinfo/tclug-list