I haven't really read your post thoroughly. Here's a couple of
suggestions... when you change your named config, restart it with:
service named stop
then check that it has stopped
service named status
and then start it again...
service named start
When you get messages like "rndc: connect failed: connection refused"
that means that named isn't going.
"/var/named/chroot/etc" is a weird weird place for named.conf... did you
manually put it there or is this something new that Fedora has
introduced? In the olden days it used to just be /var/named/ ...
Your problem is probably due to the named.conf file being busted. If
you attached your entire named.conf file below it looks decidedly empty
(no forward lookups for a start!?). I can't say that for sure, but one
this that WILL tell you is /var/log/messages so try a "service named
start" and see what ends up appended in /var/log/messages. You can do
a "tail -vf /var/log/messages" is a new windows while you start named in
another window.
Man, I'm used to the RedHat version of named. This info could be well
different in the Fedora environment.
Good luck, normally it's just something stupid in the configs...
Michael.
On Wed, 2004-09-15 at 16:04, Olwen Williams wrote:
> I have just re setup my Linux developement websorver using Fedora.
>
> I used to use DNS with an imaginary domain and wildcards for testing.
> Let's call it xyz so sites are site1.xyz site2.xyz with the actual
> name being handled by Apache name-based virtual hosting.
>
> I can't get the DNS working again.
> The server is on 10.0.0.3 and is called lionel
> I can access the default website from other computers in the network
> woth 10.0.0.3 and with lionel but nit with lionel.xyz
> For the time being I am happy just to get DNS working and will worry
> about wild cards later.
> rdnc start (or stop or ....) gives
> rndc: connect failed: connection refused
>
> named.conf is in /var/named/chroot/etc
> and reads:
> -----
> zone "xyz" {
> allow-query (any;);
> type master;
> notify no;
> file "xyz.zone";
> };
> -----
>
> rdnc.key is in the same directory and is empty.
>
> There is also rdnc.key in /etc with
> -----
> key "rndckey" {
> algorithm hmac-md5;
> secret "L9EJnz0ahTCcZbMycUaKy4Ipxp0D6Doxqy0yEsVZKXDmK63r9FXEsFErvDf4";
> };
> -----
> and rndc.conf in /etc with:
> -----
> options {
> default-server localhost;
> default-key "rndckey";
> };
>
> server localhost {
> key "rndckey";
> };
>
> include "/etc/rndc.key";
> -----
>
> xyz.zone is in /var/named/chroot/var/named and reads:
> -----
> ns.xyz. IN SOA localhost root (
> 41 ; serial
> 28800 ; refresh
> 14400 ; retry
> 3600000 ; expire
> 86400 ; ttl
> )
> 10.0.0.3 IN NS ns.xyz.
> lionel.xyz IN A 10.0.0.3
> -----
