Upon installing Centos 4.4 a second time it worked "out of the box" as expected. Sorry that I caused a stir over a non-problem. I still have no idea what I did that may have caused dns to fail, I think I made all the same choices and entries the second time around? However doing this in the wee hours I had no interruptions or distractions ...
Should anyone be interested the dns servers are: cat /etc/resolv.conf nameserver 12.189.32.61 nameserver 208.67.222.222 nameserver 208.67.220.220
but there may be a problem here: service named status rndc: connect failed: connection refused
I'm not certain about that but next is to run yum update and do some other configuration to satisfy my own preferences.
Thanks much to all.
Bob Goodwin Zuni, Virginia
In article 46010BD3.1070307@wildblue.net, Bob Goodwin bobgoodwin@wildblue.net wrote:
Upon installing Centos 4.4 a second time it worked "out of the box" as expected. Sorry that I caused a stir over a non-problem. I still have no idea what I did that may have caused dns to fail, I think I made all the same choices and entries the second time around? However doing this in the wee hours I had no interruptions or distractions ...
Should anyone be interested the dns servers are: cat /etc/resolv.conf nameserver 12.189.32.61 nameserver 208.67.222.222 nameserver 208.67.220.220
These are all external to your box.
but there may be a problem here: service named status rndc: connect failed: connection refused
So this isn't a problem - you don't need named running on the box unless you want to support having "nameserver 127.0.0.1" in your resolv.conf
Hope this helps.
Cheers Tony
Tony Mountifield wrote:
In article 46010BD3.1070307@wildblue.net, Bob Goodwin bobgoodwin@wildblue.net wrote:
Upon installing Centos 4.4 a second time it worked "out of the box" as expected. Sorry that I caused a stir over a non-problem. I still have no idea what I did that may have caused dns to fail, I think I made all the same choices and entries the second time around? However doing this in the wee hours I had no interruptions or distractions ...
Should anyone be interested the dns servers are: cat /etc/resolv.conf nameserver 12.189.32.61 nameserver 208.67.222.222 nameserver 208.67.220.220
These are all external to your box.
but there may be a problem here: service named status rndc: connect failed: connection refused
So this isn't a problem - you don't need named running on the box unless you want to support having "nameserver 127.0.0.1" in your resolv.conf
Hope this helps.
Cheers Tony
Yes I want the caching-nameserver running and thought it would result from the install but that didn't happen?
Despite that it seems to be working well! I was able to install xfce via yum but apparently gkrellm will have to be done without yum? I also like the dejavu fonts ...
So I have some configuration to attend to but so far I am quite happy with the result.
Thanks.
Bob
In article 460131B0.5030706@wildblue.net, Bob Goodwin bobgoodwin@wildblue.net wrote:
Tony Mountifield wrote:
So this isn't a problem - you don't need named running on the box unless you want to support having "nameserver 127.0.0.1" in your resolv.conf
Yes I want the caching-nameserver running and thought it would result from the install but that didn't happen?
You need to start named running:
root# service named start
And then tell the system to start named automatically on future boots:
root# chkconfig named on
Then provided the caching-nameserver package is installed, you just take out the external nameserver lines from /etc/resolv.conf (else you won't get the benefit of caching nameserver) and replace them with the single line "nameserver 127.0.0.1".
Cheers Tony
Bob Goodwin wrote:
Upon installing Centos 4.4 a second time it worked "out of the box" as expected. Sorry that I caused a stir over a non-problem. I still have no idea what I did that may have caused dns to fail, I think I made all the same choices and entries the second time around? However doing this in the wee hours I had no interruptions or distractions ...
Should anyone be interested the dns servers are: cat /etc/resolv.conf nameserver 12.189.32.61 nameserver 208.67.222.222 nameserver 208.67.220.220
These are all external to your box.
but there may be a problem here: service named status rndc: connect failed: connection refused
So this isn't a problem - you don't need named running on the box unless you want to support having "nameserver 127.0.0.1" in your resolv.conf
Yes I want the caching-nameserver running and thought it would result from the install but that didn't happen?
Despite that it seems to be working well! I was able to install xfce via yum but apparently gkrellm will have to be done without yum? I also like the dejavu fonts ...
So I have some configuration to attend to but so far I am quite happy with the result.
Serving DNS and where you resolve it as a client are completely independent. It is entirely possible to run a nameserver but not use it yourself on the same machine. The /etc/resolv.conf nameserver entries determine where you resolve.
By the way, a 'yum update' might fix the rndc problem. I thought there was some issue with the key generation that only affects communication between named and its control program. Normal operation should work anyway.
In article 460139E4.4050505@gmail.com, Les Mikesell lesmikesell@gmail.com wrote:
Bob Goodwin wrote:
but there may be a problem here: service named status rndc: connect failed: connection refused
By the way, a 'yum update' might fix the rndc problem. I thought there was some issue with the key generation that only affects communication between named and its control program. Normal operation should work anyway.
"connection refused" most likely means named is not running, and that it hasn't actually got as far as trying to use the key.
Cheers Tony
Tony Mountifield wrote:
In article 460139E4.4050505@gmail.com, Les Mikesell lesmikesell@gmail.com wrote:
Bob Goodwin wrote:
but there may be a problem here: service named status rndc: connect failed: connection refused
By the way, a 'yum update' might fix the rndc problem. I thought there was some issue with the key generation that only affects communication between named and its control program. Normal operation should work anyway.
"connection refused" most likely means named is not running, and that it hasn't actually got as far as trying to use the key.
Cheers Tony
Yes that was the problem, I can start named and service named status shows it running, that's ok but when I make the 127.0.0.1 entry in /etc/resolv.conf I get -
dig centos.org dig: couldn't get address for '127.0.0.1': not found
This is stuff that works for me in FC6 so apparently there are other things to deal with in Centos?
Bob
In article 4601477F.6040008@wildblue.net, Bob Goodwin bobgoodwin@wildblue.net wrote:
Yes that was the problem, I can start named and service named status shows it running, that's ok but when I make the 127.0.0.1 entry in /etc/resolv.conf I get -
dig centos.org dig: couldn't get address for '127.0.0.1': not found
This is stuff that works for me in FC6 so apparently there are other things to deal with in Centos?
That suggests that you haven't actually got the caching-nameserver RPM installed, so you are lacking the zone for it to do a reverse lookup on 127.0.0.1.
Could you post the output from the following commands?
cat /etc/resolv.conf rpm -q caching-nameserver cat /etc/named.conf ls -l /var/named
Or feel free to email me off-list.
Cheers Tony
-
Bob Goodwin -
Les Mikesell -
tony＠softins.clara.co.uk