----- Original Message -----
From: "Alexander Dalloz" <ad+lists@xxxxxxxxx>
To: "For users of Fedora Core releases" <fedora-list@xxxxxxxxxx>
Sent: Tuesday, December 07, 2004 3:17 AM
Subject: Re: Problem whith DNS
>Either none of the nameservers specified in /etc/resolv.conf is
>listening or communication is blocked by a firewall setting. Maybe a
>better check method is to run
The server specified in resolf.conf in the same machine in which I'm
installing the DNS
> dig -t ANY station22.alilou.fr @127.0.0.1
this commande give the same answer with 'host'.
; <<>>DiG 9.2.3 <<>> -t ANY station22.alilou.fr @127.0.0.1
;; global options: printcmd
;; connection timed out; no servers could be reached
>> Dec 7 00:13:53 a22sys3 named[6977]: couldn't add command channel
::1#953:
>> not found
>This error is due to IPv6.
OK
>> Dec 7 00:13:53 a22sys3 named[6977]: zone alilou.fr/IN: loading master
file
>> alilou.fr.zone: file not found
>Either the zone file is missing or - what I expect more - it has wrong
>permissions.
>chown named:named /var/named/chroot/var/named/alilou.fr.zone
>chmod 644 /var/named/chroot/var/named/alilou.fr.zone
I have done this change but the result is the same.
>> Dec 7 01:13:54 a22sys3 named: starting of named succeeded
>So it started.
Yes! !
Tank you Alexander. But the message is already the same:
dig -t ANY station22.alilou.fr @127.0.0.1
; <<>>DiG 9.2.3 <<>> -t ANY station22.alilou.fr @127.0.0.1
;; global options: printcmd
;; connection timed out; no servers could be reached
So, why it can't reach the DNS server my god!!
Am Di, den 07.12.2004 schrieb AlilouLinux um 2:38:
> I decided to install a DNS server in my machine (name of the machine =
> station22) which run under FC2. I have used for this 'bind'. I have created
> a primary zone (name of domaine= alilou.fr).
Ok.
> In order to test if my server work well, I have used the commande 'host',
> but I get this error:
> [root@a22sys3 root]# host station22
> ;; connection timed out; no servers could be reached
Either none of the nameservers specified in /etc/resolv.conf is
listening or communication is blocked by a firewall setting. Maybe a
better check method is to run
dig -t ANY station22.alilou.fr @127.0.0.1
> And get these messages in the log file:
>
> Dec 7 00:13:53 a22sys3 named[6977]: couldn't add command channel ::1#953:
> not found
This error is due to IPv6.
> Dec 7 00:13:53 a22sys3 named[6977]: zone alilou.fr/IN: loading master file
> alilou.fr.zone: file not found
Either the zone file is missing or - what I expect more - it has wrong
permissions.
chown named:named /var/named/chroot/var/named/alilou.fr.zone
chmod 644 /var/named/chroot/var/named/alilou.fr.zone
> Dec 7 00:13:53 a22sys3 named[6977]: running
> Dec 7 01:13:54 a22sys3 named: starting of named succeeded
So it started.
> This mean that it does'nt found the zone file alilou.fr.zone. This file
> exist in /var/named/chroot/var/named/ and in /var/named/
It has to be only in 1 location. Do you run bind chrooted? Then the
first path does matter, the last is ignored/unknown to bind. Else vice
versa.
rpm -q bind-chroot
cat /etc/sysconfig/named
> I give you the structure of some files if you need this:
> /etc/named.conf:
> // added by Alilou (me) <-----
> zone "alilou.fr" IN {
> type master;
> file "alilou.fr.zone";
> };
>
> zone "forward.alilou.fr" {
> type master;
> file "forward.alilou.fr.zone";
> };
What is the last "zone forward.alilou.fr"? You already specified the
forward zone file for alilou.fr on top of it. "alilo.fr.zone is the
forward zone (file).
> alilou.fr.zone:
> ******************
>
> TTL 86400
> @ IN SOA @ root.localhost (
> 14 ; serial
> 28800 ; refresh
> 14400 ; retry
> 3600000 ; expire
> 86400 ; ttl
> )
>
>
>
> IN NS localhost.
> ns IN NS 10.194.3.39.
> a22 IN NS 10.194.3.39.
The trailing dots on the 10.194.3.39 address is wrong.
> localhost IN NS 10.194.3.39
> station22 IN A 10.194.3.39
> station23 IN A 10.194.3.40
> station12 IN A 10.194.3.35
> station11 IN A 10.194.3.34
>
> resolv.conf:
> ************
> domain alilou.fr
> search alilou.fr
> nameserver 10.194.3.39
> nameserver 127.0.0.1
> ****************
10.194.3.39 and 127.0.0.1 are the same nameserver. You gain nothing by
setting both as nameservers.
> Aliloulinux
Alexander
--
Alexander Dalloz | Enger, Germany | new address - new key: 0xB366A773
legal statement: http://www.uni-x.org/legal.html
Fedora GNU/Linux Core 2 (Tettnang) on Athlon kernel 2.6.9-1.6_FC2smp
Serendipity 03:02:05 up 1 day, 2:24, load average: 0.08, 0.39, 0.55
