DNS in Fedora core 2

caocon · 11-10-2004, 11:48 AM

I'm using Fedora core 2
One beautiful day, I want to configure DNS server .I did everything the same in books , but it didn't work !` ! !

(
I installed RedHat 8.0 and did the same , wow it worked ! ! ! I saved all files (etc/named.config , etc/host , var/named/192.168.3 , var/named/caocon.com) and installed Fedora core 2 .After that, I copied all that files into Fedora core 2! ! ! aha ahahah.a.a.a... It didn't work ! ! !
So could you help me to solve this problem ?

This is my DNS config

etc/named.conf

// generated by named-bootconf.pl

options {
directory "/var/named";
/*
* If there is a firewall between you and nameservers you want
* to talk to, you might need to uncomment the query-source
* directive below. Previous versions of BIND always asked
* questions using port 53, but BIND 8.1 uses an unprivileged
* port by default.
*/
// query-source address * port 53;
};

//
// a caching only nameserver config
//
controls {
inet 127.0.0.1 allow { localhost; } keys { rndckey; };
};
zone "." IN {
type hint;
file "named.ca";
};

zone "localhost" IN {
type master;
file "localhost.zone";
allow-update { none; };
};

zone "0.0.127.in-addr.arpa" IN {
type master;
file "named.local";
allow-update { none; };
};

zone "caocon.com" IN {
type master;
file "caocon.com";
allow-update { none; };
};

zone "3.168.192.in-addr.arpa" IN {
type master;
file "192.168.3";
allow-update { none; };
};$TTL 86400
@ IN SOA ns.caocon.com. hostmaster.caocon.com. (
1997022700 ; Serial
28800 ; Refresh
14400 ; Retry
3600000 ; Expire
86400 ) ; Minimum

TXT "caocon.com, your DNS consultants"
NS ns ; Inet Address of name server
NS ns.friend.com.
MX 10 mail ; Primary Mail Exchanger
MX 20 mail.friend.bogus. ; Secondary Mail Exchanger

localhost A 127.0.0.1

gw A 192.168.3.1
TXT "The router"

ns A 192.168.3.1
MX 10 mail
MX 20 mail.friend.bogus.
www CNAME ns

donald A 192.168.3.2
MX 10 mail
MX 20 mail.friend.bogus.
TXT "DEK"

mail A 192.168.3.3
MX 10 mail
MX 20 mail.friend.bogus.

ftp A 192.168.3.4
MX 10 mail
MX 20 mail.friend.bogus.

include "/etc/rndc.key";

==================================
var/named/caocon.com

$TTL 86400
@ IN SOA ns.caocon.com. hostmaster.caocon.com. (
1997022700 ; Serial
28800 ; Refresh
14400 ; Retry
3600000 ; Expire
86400 ) ; Minimum

TXT "caocon.com, your DNS consultants"
NS ns ; Inet Address of name server
NS ns.friend.com.
MX 10 mail ; Primary Mail Exchanger
MX 20 mail.friend.bogus. ; Secondary Mail Exchanger

localhost A 127.0.0.1

gw A 192.168.3.1
TXT "The router"

ns A 192.168.3.1
MX 10 mail
MX 20 mail.friend.bogus.
www CNAME ns

donald A 192.168.3.2
MX 10 mail
MX 20 mail.friend.bogus.
TXT "DEK"

mail A 192.168.3.3
MX 10 mail
MX 20 mail.friend.bogus.

ftp A 192.168.3.4
MX 10 mail
MX 20 mail.friend.bogus.
================================================

var/named/192.168.3

$TTL 86400
@ IN SOA ns.caocon.com. hostmaster.caocon.com. (
1997022700 ; Serial
28800 ; Refresh
14400 ; Retry
3600000 ; Expire
86400 ) ; Minimum
IN NS ns.caocon.com.

1 IN PTR gw.caocon.com.
2 IN PTR ns.caocon.com.
3 IN PTR donald.caocon.com.
4 IN PTR mail.caocon.com.
5 IN PTR ftp.caocon.com.

==================================================

etc/host

# Do not remove the following line, or various programs
# that require network functionality will fail.
127.0.0.1 localhost.localdomain localhost
192.168.3.1 caocon.com.

================================================

etc/rndc.conf

key "rndckey" {
algorithm hmac-md5;
secret "c3Ryb25nIGVub3VnaCBmb3IgYSBtYW4gYnV0IG1hZGUgZm9yIGEgd29tYW4K";
};

options {
default-server 192.168.3.1;
default-key "rndckey";
};

server 192.168.3.1 {
key "rndckey";
};

=======================================================
rndc.key

key "rndckey" {
algorithm hmac-md5;
secret "9hPhuIbBEFY2GyVO5QQZbznkjxXucHV1PSuY7er0MqDooXgSq8eclOdSu7F2";
};

=============================================================

Thanks for youe help !

Matir · 11-10-2004, 02:00 PM

Is the named server running? Do you get any errors?

What HAPPENS to make you believe it is not "working"?

RHELL · 11-10-2004, 03:12 PM

Does the following string really exist in named.conf as you posted?

>>;$TTL 86400
>>@ IN SOA ns.caocon.com. hostmaster.caocon.com. (
>>1997022700 ; Serial
>>28800 ; Refresh
>>14400 ; Retry
>>3600000 ; Expire
>>86400 ) ; Minimum

>>TXT "caocon.com, your DNS consultants"
>>NS ns ; Inet Address of name server
>>NS ns.friend.com.
>>MX 10 mail ; Primary Mail Exchanger
>>MX 20 mail.friend.bogus. ; Secondary Mail Exchanger

>>localhost A 127.0.0.1

>>gw A 192.168.3.1
>>TXT "The router"

>>ns A 192.168.3.1
>>MX 10 mail
>>MX 20 mail.friend.bogus.
>>www CNAME ns

>>donald A 192.168.3.2
>>MX 10 mail
>>MX 20 mail.friend.bogus.
>>TXT "DEK"

>>mail A 192.168.3.3
>>MX 10 mail
>>MX 20 mail.friend.bogus.

>>ftp A 192.168.3.4
>>MX 10 mail
>>MX 20 mail.friend.bogus.

Darin · 11-10-2004, 03:41 PM

Like Matir mentioned, what makes you say it doesn't work? can you get normal internet names like www.linuxquestions.org? can you get your own domain like caocon.com? Are you trying in a web browser, or a shell prompt, or what do you do to see if it works?

Try these commands in a terminal window: 'dig caocon.com' and 'dig -x 192.168.3.1', they should respond with your DNS server in the answer section. If not then check that /etc/resolv.conf has:

Code:

search caocon.com
#one of these nameserver lines, either should work
nameserver 127.0.0.1
nameserver 192.168.3.1

Matir · 11-10-2004, 03:48 PM

As a question of my own, is the search line there required? I use a LAN DNS server for names such as "ozone", "tritium', etc. for my computers. In order to get them to resolve, I had to remove the search line from my resolv.conf. If I do need this line, I guess I need to edit my DNS server

, but things seem to run fine right now.

Darin · 11-10-2004, 08:17 PM

I belive the search line is for using multiple DNS servers and pointing lookups for a specific domain to a specific server.. This means if you are using one DNS server for your specific domain(s) and it also forewards DNS lookups for other domains (the zone "." { type hint; file "named.ca"; }; line in named.conf) then you shouldn't have to have a search line. Everything I have read about DNS config tells you to put it in there so I just do even though it is probably not required.

caocon · 11-11-2004, 10:16 AM

I just create a domain for my LAN.
I knew it work in Redhat 8.0 because when I used commands : dig -x 127.0.0.1 ; dig -x 192.168.3.1 ; dnslookup ... ; server www.caocon.com ; server mail.caocon.com , all of them worked very well.
But in Fedora , I didn't get the same result.

for emxaple :
===================================
[root@caocon root]# dig -x 127.0.0.1

; <<>> DiG 9.2.3 <<>> -x 127.0.0.1
;; global options: printcmd
;; connection timed out; no servers could be reached
=====================================
[root@caocon root]# nslookup
> server www.caocon.com
nslookup: Couldn't find server 'www.caocon.com': Temporary failure in name resolution
=====================================
[root@caocon root]# rndc reload
rndc: connect failed: network unreachable
=====================================

You see , It make me angry :~((

Thank you .

Darin · 11-11-2004, 05:57 PM

post the results of:
[root@caocon root]# named-checkconfig
[root@caocon root]# named-checkzone localhost /var/named/localhost.zone
[root@caocon root]# named-checkzone 0.0.127.in-addr.arpa /var/named/named.local
[root@caocon root]# named-checkzone caocon.com /var/named/caocon.com
[root@caocon root]# named-checkzone 3.168.192.in-addr.arpa /var/named/192.168.3

Basically any one that doesn't say OK in the result means that zonefile is bad, it usually gives you the line # of anything problematic. If all those say OK then it's most likely in your named.conf

edit- I also had a problem with RedHat that you might be experiencing where the init script isn't set up to properly shutdown the nameserver. So if you are trying to reload named and it doesn't seem to change anything, killall -9 named is just as easy to type as service named stop

Matir · 11-11-2004, 08:06 PM

Quote:

Originally posted by Darin

edit- I also had a problem with RedHat that you might be experiencing where the init script isn't set up to properly shutdown the nameserver. So if you are trying to reload named and it doesn't seem to change anything, killall -9 named is just as easy to type as service named stop

Try a nice -HUP first perhaps. I don't know how named responds to that, but some software likes a bit more graceful shutdown than -9

scowles · 11-11-2004, 08:55 PM

Quote:

Originally posted by Matir
Try a nice -HUP first perhaps. I don't know how named responds to that, but some software likes a bit more graceful shutdown than -9

From: man named

Code:

SIGNALS
       In  routine  operation, signals should not be used to control the name-
       server; rndc should be used instead.
 
       SIGHUP Force a reload of the server.
 
       SIGINT, SIGTERM
              Shut down the server.
 
       The result of sending any other signals to the server is undefined.

Matir · 11-11-2004, 09:20 PM

Ah, indeed. Though -HUP, PER DOCUMENTATION, is the proper way (ignoring control scripts) to reload the server.

Darin · 11-12-2004, 01:27 AM

Good ideas although someone needs to tell the guys at Slackware that...

from Slackware 9.1 /etc/rc.d/rc.bind:

Code:

...
# Stop bind:
bind_stop() {
  killall named
}
...

edit- that's what I get for posting too late at night, killall without the -9 sends a SIGTERM anyhow.