On this page
- BIND Installation On CentOS
- What is bind?
- 1. You Can Check BIND Packet
- 2. Setting Computer NS1 With IP 192.168.0.1 As Nameserver And Domain Name yourdomain.com
- 3. Setting File /etc/named.conf
- 4. Setting File /var/named/yourdomain.com.zone
- 5. Setting File /var/named/0.168.192.rev
- 6. nslookup yourdomain.com
- 7. dig yourdomain.com
- 8. Configuration For NS 1 Is Finished
- 9. Check The /var/log/messages Log To Find Out If There Are Errors
BIND Installation On CentOS
What is bind?
BIND is alternative software for translating domain names into IP addresses. Because domain names are alphabetic, they are easier to remember. So if we will browse the Internet we don’t need to remember IP addresses. For example, the domain name www.yourdomain.com might translate to 192.168.0.1.
1. You Can Check BIND Packet
[[email protected] named]# rpm -qa bind*
bind-libs-9.2.4-2
bind-utils-9.2.4-2
bind-9.2.4-2
2. Setting Computer NS1 With IP 192.168.0.1 As Nameserver And Domain Name yourdomain.com
[[email protected] ~]# cat /etc/resolv.conf
nameserver 192.168.0.1
3. Setting File /etc/named.conf
[[email protected] ~]# nano /etc/named.conf
//
// named.conf for Red Hat caching-nameserver
//
options {
directory "/var/named";
dump-file "/var/named/data/cache_dump.db";
statistics-file "/var/named/data/named_stats.txt";
/*
* 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 "localhost" IN {
type master;
file "localhost.zone";
allow-update { none; };
};
zone "yourdomain.com" IN {
type master;
file "/var/named/yourdomain.com.zone";
allow-update { none; };
};
zone "0.168.192.in-addr.arpa" IN {
type master;
file "/var/named/0.168.192.rev";
allow-update { none; };
};
include "/etc/rndc.key";
4. Setting File /var/named/yourdomain.com.zone
First you must create the file yourdomain.com.zone; you can use this syntax:
[[email protected] ~]# nano /var/named/yourdomain.com.zone
$TTL 86400 @ IN SOA yourdomain.com. root.yourdomain.com. ( 100 ; serial 1H ; refresh 1M ; retry 1W ; expiry 1D ) ; minimum @ IN NS ns1.yourdomain.com. @ IN A 192.168.0.1 ns1 IN A 192.168.0.1 @ IN MX 10 mail.yourdomain.com. mail IN A 192.168.0.1 WWW IN A 192.168.0.1
5. Setting File /var/named/0.168.192.rev
First you must create the file 0.168.192.rev; you can use this syntax:
[[email protected] ~]# nano /var/named/0.168.192.rev
$TTL 86400 @ IN SOA yourdomain.com. root.yourdomain.com. ( 100 ; serial 1H ; refresh 1M ; retry 1W ; expiry 1D) ; minimum @ IN NS ns1.yourdomain.com. 1 IN PTR binggo.yourdomain.com.
6. nslookup yourdomain.com
[[email protected] ~]# nslookup yourdomain.com
Server: 192.168.0.1
Address: 192.168.0.1#53
Name: yourdomain.com
Address: 192.168.0.1
7. dig yourdomain.com
[[email protected] ~]# dig yourdomain.com
; DiG 9.2.4 yourdomain.com
;;
global options: printcmd
;; Got answer:
;; ->>HEADER<<-
opcode: QUERY, status: NOERROR, id: 10576
;; flags: qr aa rd ra;
QUERY: 1, ANSWER: 1, AUTHORITY: 1, ADDITIONAL: 1
;; QUESTION SECTION:
;yourdomain.com.
IN A
;; ANSWER SECTION:
yourdomain.com.
86400 IN A 192.168.0.1
;; AUTHORITY SECTION:
yourdomain.com.
86400 IN NS ns1.yourdomain.com.
;; ADDITIONAL SECTION:
ns1.yourdomain.com. 86400
IN A 192.168.0.1
;; Query time: 8 msec
;; SERVER:
192.168.0.1#53(192.168.0.1)
;; WHEN: Sat Aug 2 10:56:16
2008
;; MSG SIZE rcvd: 85
8. Configuration For NS 1 Is Finished
If you see errors, you can try to change the permissions of the folder /var/named.
[[email protected] ~]# chmod 777 -Rvf /var/named/
mode of
`/var/named/’ changed to 0777 (rwxrwxrwx)
mode of
`/var/named/named.zero’ changed to 0777 (rwxrwxrwx)
mode of
`/var/named/localhost.zone’ changed to 0777 (rwxrwxrwx)
mode of
`/var/named/198.99.208.rev’ changed to 0777 (rwxrwxrwx)
mode of
`/var/named/data’ changed to 0777 (rwxrwxrwx)
mode of
`/var/named/named.local’ changed to 0777 (rwxrwxrwx)
mode of
`/var/named/named.ca’ changed to 0777 (rwxrwxrwx)
mode of
`/var/named/named.ip6.local’ changed to 0777 (rwxrwxrwx)
mode of
`/var/named/localdomain.zone’ changed to 0777 (rwxrwxrwx)
mode
of `/var/named/yourdomain.com.zone’ changed to 0777
(rwxrwxrwx)
mode of `/var/named/named.broadcast’ changed to 0777
(rwxrwxrwx)
mode of `/var/named/slaves’ changed to 0777
(rwxrwxrwx)
9. Check The /var/log/messages Log To Find Out If There Are Errors
[[email protected] ~]# tail /var/log/messages
Aug 2 10:53:57 server named[20094]:
listening on IPv4 interface venet0:0, 192.168.0.1#53
Aug 2
10:53:57 server named[20094]: command channel listening on
127.0.0.1#953
Aug 2 10:53:57 server named[20094]: zone
0.168.192.in-addr.arpa/IN: loaded serial 100
Aug 2 10:53:57
server named[20094]: zone yourdomain.com/IN: loaded serial 100
Aug 2 10:53:57 server named[20094]: zone localhost/IN: loaded serial
42
Aug 2 10:53:57 server named[20094]: running
Aug 2 10:53:57 server named[20094]: zone yourdomain.com/IN: sending
notifies (serial 100)
Aug 2 10:53:57 server named[20094]:
zone 0.168.192.in-addr.arpa/IN: sending notifies (serial 100)
Aug
2 10:53:57 server named[20094]: received notify for zone
‘yourdomain.com’
Aug 2 10:53:57 server named[20094]:
received notify for zone ‘0.168.192.in-addr.arpa’
