bind and named and "rndc: connect failed: connection refused"

coffee9876 · 12-16-2003, 01:49 AM

Hello.
I'm trying to set up my linux box to be an internet nameserver. I"ve got web traffic, defined at networksolutions, to ns1.coffee9876.com. at 63.226.001.1.

I think I need Bind/named to take traffic for 63.226.1.1 and make it act as name server.
Sound right?
--------------------------------
In Services, it says that named status is "rndc: connect failed: connection refused"

In /var/log/messages

Dec 14 09:46:20 multivac named[10550]: starting BIND 9.2.1 -u named
Dec 14 09:46:20 multivac named[10550]: using 1 CPU
Dec 14 09:46:20 multivac named: named startup succeeded
Dec 14 09:46:20 multivac named[10550]: loading configuration from '/etc/named.conf'
Dec 14 09:46:20 multivac named[10550]: no IPv6 interfaces found
Dec 14 09:46:20 multivac named[10550]: listening on IPv4 interface lo, 127.0.0.1#53
Dec 14 09:46:20 multivac named[10550]: listening on IPv4 interface eth0, 63.226.1.1#53
Dec 14 09:46:20 multivac named[10550]: could not configure root hints from 'named.ca': file not found
Dec 14 09:46:20 multivac named[10550]: loading configuration: file not found
Dec 14 09:46:20 multivac named[10550]: exiting (due to fatal error)
Dec 14 09:50:00 multivac named: named reload failed

I'm a newbie. I'm baffled. What do I need to check or change to get this to run? What could be broken? How do I get named to run? Any suggestions?
Thanks

chort · 12-16-2003, 02:11 AM

You're very confused. Name Service and web traffic are two very different things.

Domain Name Service (DNS) is a system for translating Internet names into IP addresses. Web traffic generally means Hyper Text Transfer Protocol and refers to the World Wide Web of interconnected web sites. A DNS daemon runs name service (such as BIND, djbdns, etc) and a HTTP daemon runs web service (such as Apache).

Chances are that Network Solutions will host your DNS for you. You don't necessarily need to setup your own (although it could be educational). What you need to know is whether you setup your own IP as your authoritative DNS server or not (look in your account on Network Solutions to see what is listed as your authoritative DNS servers). If you only want to display a web page, then you only need httpd listening for connections.

As for your error above, you do not have a file named "named.ca" in the proper directory. You need to download the list of "root servers" from Internic, which you can do like this:
wget ftp://ftp.internic.net/domain/named.root
You need to put it in a directory, such as /var/named/, and you need to edit your /etc/named.conf file to use /var/named/named.root as your "hints" file for the "." zone. That's the bare minimum just to get a DNS server working to resolve outside names. If you want to setup your own DNS, you'll have to do a lot more work to configure it.

coffee9876 · 12-16-2003, 10:21 AM

Chort,
Thanks for the help! While it did not fix the problem, it did at least cause different ones! I'm on the right track!

Dec 16 08:16:23 multivac named: named shutdown failed
Dec 16 08:16:25 multivac named[3725]: starting BIND 9.2.1 -u named
Dec 16 08:16:25 multivac named[3725]: using 1 CPU
Dec 16 08:16:25 multivac named[3725]: loading configuration from '/etc/named.conf'
Dec 16 08:16:25 multivac named[3725]: /etc/named.custom:8: option 'allow-update' is not allowed in 'hint' zone '.'
Dec 16 08:16:25 multivac named[3725]: /etc/rndc.key:1: key 'rndc-key': already exists
Dec 16 08:16:25 multivac named[3725]: loading configuration: failure
Dec 16 08:16:25 multivac named[3725]: exiting (due to fatal error)
Dec 16 08:16:25 multivac named: named startup succeeded

chort · 12-16-2003, 10:50 AM

Your "." zone should just be like this:

Code:

    zone "." {
            type hint;
            file "standard/root.hint";
    };

(where "standard" is the path to your hints file).