rndc connection refused

Hello. first off i've read the stickies (time and time again) and here's my info:

I'm using bind 9 on redhat 9
IP 67.18.5.157
This is a leased dedicated server
Here's my situation: I want to use 67.18.5.157 as ns1 for www.realestatelogic.net.

realestatelogic.net is a virtual hosted domain on eonflux.com.

the IP address of both realestatelogic.net and eonflux.com is 66.98.177.166.

these are the relevent files:

http://67.15.47.3/named.conf http://67.15.47.3/named.ca
http://67.15.47.3/named.custom http://67.15.47.3/named.run http://67.15.47.3/realestatelogic.net.zone
http://67.15.47.3/localhost.zone http://67.15.47.3/0.0.127.in-addr.arpa.zone
http://67.15.47.3/resolv.conf
I still can't get anything to work right. rndc fails to start, which means there's a config problem.
I'm also wondering if resolv.conf is proper, so i included it. I don't have a domain name for 67.18.5.157, can i just use the IP? btw, realestatelogic.net's email server is also hosted on eonflux with qmail.

as of right now ns1 for realestatelogic.net, created201.com, and a few others (all hosted on eonflux.com) is ns1.created201.com which is eonflux.com as well.

here's the physical layout right now:
named.conf, named.custom, named.run and named.ca are all under /etc. the zone files are under /var/named.

my problem is, named will not start because rndc will not start. Is there something i have overlooked and/or misconfigured? also, i don't have this 127.0.0.1.rev file anywhere. what exactly is it for?

any help at all would be greatly appreciated. Thanks in advance!

I see you didn't find it necessary to follow the linux BIND setup tutorial in that sticky though. Perhaps if you followed my instructions you could've gotten it working. But I'm not going to make ya, I'll help you were you are at.

Point #1

named.run has some errors, these are the important ones:

Jan 04 11:11:36.832 could not configure root hints from 'named.ca': file not found
Jan 04 11:11:36.832 load_configuration: file not found
Jan 04 11:11:36.832 loading configuration: file not found

So far it's pretty obvious. BIND won't start cause it can't find "named.ca".

Point #2

named.conf included named.custom. named.custom said it will look for relative paths in the following directory:

directory "/var/named/";

Point #3

You said "named.ca" IS located in the /var/named directory.

Problem: There is one of 4 things that could cause this problem.

#1: You are mistaken. named.ca is NOT in /var/named.
#2: BIND is trying to load a different named.conf. But this is unlikely cause named.run said:

loading configuration from '/etc/named.conf'

#3: BIND is in a chroot jail and so the path to the proper named.conf is /path/to/chroot/etc/named.conf for example. But this is unlikely unless rndc can start named in chroot. Usually you execute named directly with special commandline options.

#4: Those are old errors and you are misinterpreting rndc's error message.

Solution:

If the problem is NOT #1, then doing the following commands will start named correctly:

killall -KILL named
named -u named

Fallback:

If the above didn't work, and you're still convinced named.ca is located in /var/named then execute the following command and paste for me the results:

named -u named -g

in my own defense i tried using redhat-config-bind to make this work, and now i'm trying to sift through the mess it made.

----------------------------------------------------------------------------------
named.conf, named.custom, named.run and named.ca are all under /etc.
----------------------------------------------------------------------------------

I moved named.ca to /var/named and at least everything started ok
---------------------------------------------------------------------------------
[root@lt1a-25 admin]# killall -KILL named
[root@lt1a-25 admin]# /usr/sbin/rndc -V reload
create memory context
create socket manager
create task manager
create task
create logging context
setting log tag
creating log channel
enabling log channel
create parser
get key for server
get config key list
decode base64 secret
reload
post event
using server localhost (127.0.0.1#953)
create socket
connect
create message
render message
schedule recv
send message
parse message
[root@lt1a-25 admin]# /usr/sbin/named -u named
---------------------------------------------------------------------------------

named -u named had no output.

I still don't think this is doing what I intend to do, regardless of it it starts or not. Do i need to change anything on eonflux.com to look at this new IP address as ns1.realestatelogic.net? how does virtual hosting play into this?

ok that's one error out of the way. You got no output from "named -u named" cause you're not supposed to. That starts the server.

"Do i need to change anything on eonflux.com to look at this new IP address as ns1.realestatelogic.net?"

don't know what eonflux.com is.

"how does virtual hosting play into this?"

Well, just point all domains to the same IP and the virtual hosts takes care of making multiple websites work at the same IP.

ok, so my config as full of errors. i got an o'reily book on dns/bind and reconfigured it. would you mid taking a look at the files and see if they look ok to you? rndc and named both started just fine.
when i do a dig@localhost realestatelogic.net i get this:
[root@lt1a-25 named]# dig @127.0.0.1 realestatelogic.net

; <<>> DiG 9.2.1 <<>> @127.0.0.1 realestatelogic.net
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 23348
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;realestatelogic.net. IN A

;; Query time: 1 msec
;; SERVER: 127.0.0.1#53(127.0.0.1)
;; WHEN: Sat Jan 6 11:40:54 2001
;; MSG SIZE rcvd: 37

so something is still not right. here are my files:
http://67.15.47.3/realestatelogic.net.zone http://67.15.47.3/localhost.zone http://67.15.47.3/localhost.rev http://67.15.47.3/named.conf http://67.15.47.3/0.0.127.in-addr.arpa.zone

I really appreciate the help!

ftp.realestatelogic.net. IN CNAME realestatelogic.net.
www.realestatelogic.net. IN CNAME realestatelogic.net.


Just assign the domains to IPs. Don't use CNAME's unless you have to.

ok, I changed those lines to :
ftp.realestatelogic.net. IN A 66.98.177.166
www.realestatelogic.net. IN A 66.98.177.166


but still no go, named won't start and rndc fails.

actually what's odd about this server, i can't get ANY service to run, except for ssh. ftp won't start, neither will apache. this may be some other basic networking issue.

ok i found a misspelled word in /etc/hosts. i fixed that and now some services will start, but i still can't open the address in a browser. named and rndc still don't start though.

Well if named won't start then let's see some error logs.

Jan 06 15:03:28.695 using 1 CPU
Jan 06 15:03:28.701 loading configuration from '/etc/named.conf'
Jan 06 15:03:28.714 no IPv6 interfaces found
Jan 06 15:03:28.715 listening on IPv4 interface lo, 127.0.0.1#53
Jan 06 15:03:28.716 listening on IPv4 interface eth0, 67.18.5.157#53
Jan 06 15:03:28.721 command channel listening on 127.0.0.1#953
Jan 06 15:03:28.721 ignoring config file logging statement due to -g option
Jan 06 15:03:28.723 zone 0.0.127.in-addr.arpa/IN: loaded serial 3
Jan 06 15:03:28.725 zone localhost/IN: loaded serial 1
Jan 06 15:03:28.725 zone realestatelogic.net/IN: loading master file realestatelogic.net: file not found



ok, duh, i had the wrong filename in named.conf, fixed it, and i think i'm in business!

here's the dig:

[root@lt1a-25 etc]# dig @127.0.0.1 realestatelogic.net

; <<>> DiG 9.2.1 <<>> @127.0.0.1 realestatelogic.net
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 32163
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 1

;; QUESTION SECTION:
;realestatelogic.net. IN A

;; ANSWER SECTION:
realestatelogic.net. 86400 IN A 66.98.177.166

;; AUTHORITY SECTION:
realestatelogic.net. 86400 IN NS ns1.created201.com.
realestatelogic.net. 86400 IN NS ns2.created201.com.

;; ADDITIONAL SECTION:
ns2.created201.com. 172771 IN A 66.98.177.166

;; Query time: 2 msec
;; SERVER: 127.0.0.1#53(127.0.0.1)
;; WHEN: Sat Jan 6 15:06



that's it right?
RTFM huh. =)

heh, looking at the BIND manual can be kinda overwhelming. So I don't say RTFM. I say RTFS (read the f'ing sticky). One of these days though, I'll be setting up a BIND/DNS reference on my site.