Linux - ServerThis forum is for the discussion of Linux Software used in a server related context.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
I am a trying to configure DNS in FC 6 using chrooted-bind . It is
a experimental DNS for
learning purpose. I am finding the following difficulties.
1. There is no configuration file named named.conf in /var/named/
chroot/etc/ as in case of
earlier versions of Linux. The file that is present is
named.rfc1912.zones . I have edited
the file as follows for the domain example.com . The contents is
shown below.
zone "example.com" IN {
type master;
file "iqnet.in.zone";
allow-update { none; };
};
zone "0.168.192.in-addr.arpa" IN {
type master;
file "iqnet.in.local";
allow-update { none; };
};
The zone file are as follows
A) example.com.zone
$ORIGIN example.com.
$TTL 86400
@ IN SOA iqnetns.example.com. root.example.com. (
42 ; serial (d.
adams)
3H ; refresh
15M ; retry
1W ; expiry
1D ) ; minimum
@ IN NS iqnetns.example.com.
IN A 192.168.0.254
IN AAAA ::1
iqnetns.example.com. IN A
192.168.0.254
B) example.com.local
$TTL 86400
@ IN SOA iqnetns.example.com. root.example.com. (
1997022700 ; Serial
28800 ; Refresh
14400 ; Retry
3600000 ; Expire
86400 ) ; Minimum
IN NS iqnetns.example.com.
254 IN PTR
iqnetns.example.com.
After that I edited /etc/resolv.conf and restarted the named service.
There is no error.
But when I try to resolve
iqnetns.example.com
using dig or host command , name resolution is not taking place.
I am a trying to configure DNS in FC 6 using bhrooted-bind . It is
a experimental DNS for
learning purpose. I am finding the following difficulties.
1. There is no configuration file named named.conf in /var/named/
chroot/etc/ as in case of
earlier versions of Linux. The file that is present is
named.rfc1912.zones . I have edited
the file as follows for the domain example.com . The contents is
shown below.
zone "example.com" IN {
type master;
file "iqnet.in.zone";
allow-update { none; };
};
zone "0.168.192.in-addr.arpa" IN {
type master;
file "iqnet.in.local";
allow-update { none; };
};
The zone file are as follows
A) example.com.zone
$ORIGIN example.com.
$TTL 86400
@ IN SOA iqnetns.example.com. root.example.com. (
42 ; serial (d.
adams)
3H ; refresh
15M ; retry
1W ; expiry
1D ) ; minimum
@ IN NS iqnetns.example.com.
IN A 192.168.0.254
IN AAAA ::1
iqnetns.example.com. IN A
192.168.0.254
B) example.com.local
$TTL 86400
@ IN SOA iqnetns.example.com. root.example.com. (
1997022700 ; Serial
28800 ; Refresh
14400 ; Retry
3600000 ; Expire
86400 ) ; Minimum
IN NS iqnetns.example.com.
254 IN PTR
iqnetns.example.com.
After that I edited /etc/resolv.conf and restarted the named service.
There is no error.
But when I try to resolve
iqnetns.example.com
using dig or host command , name resolution is not taking place.
Please let me know ehere is the problem ?
With thanks
===========
I am trying to do serveral option but still can not
I also looking for help as well, hope we can get helped soon
I am trying to do serveral option but still can not
I also looking for help as well, hope we can get helped soon
You restart the named service and see the log file. There
you will find if any error is there related to named service
and try to correct it out.
I was facing the same problem. You can look down to know more about the error.
Apparenly your server is not resolving. Do you have the DNS server addresses of your ISP provider? You can use those as your forwarders, rather than having to resolve using the root DNS servers, which takes longer.
hi,
i am configure DNS in fedora core 6 but not able to DIG, suppose i use dig it show the server starts serverfail, and wht is the resason
Probably your DNS was not configured correctly.You
can check the log file for errors.
Also you can check the syntax of bind configuration files using the following commands.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.