Thank U.
Seems to have solved the problem of reverse zone.
srv:/var/lib/named/master # nslookup 192.168.1.9
Server: 127.0.0.1
Address: 127.0.0.1#53
9.1.168.192.in-addr.arpa name = srv.web.lan.
srv:/var/lib/named/master # nslookup 10.8.0.1
Server: 127.0.0.1
Address: 127.0.0.1#53
1.0.8.10.in-addr.arpa name = srv.web.lan.
srv:/var/lib/named/master #
Still I do not quite understand the question of the “@”.
Can you explain me better this question?
That is if I put the “@” in zone file I must necessarily use the 1.168.192.in-addr name?
When I’m filling the named.conf and defining one zone :
Should I use always the name like xxx.xxx.xxx…in-addr.arpa.zone ?
In witch time i can use different names?
Can you give me a full example for I understand better ?
srv:/var/lib/named/master # cat 1.168.192.in-addr.arpa.zone
$TTL 2D
@ IN SOA srv.web.lan. hostmaster.srv.web.lan. (
2015021016 ; serial
1D ; refresh
2H ; retry
1W ; expiry
2D ) ; minimum
IN NS srv.web.lan.
9 IN PTR srv.web.lan.
100 IN PTR TL-WR841N.web.lan.
srv:/var/lib/named/master #
zone "1.168.192.in-addr.arpa" in {
type master;
file "/var/lib/named/master/1.168.192.in-addr.arpa.zone";
};
zone "0.8.10.in-addr.arpa" in {
type master;
file "/var/lib/named/master/0.8.10.in-addr.arpa.zone" ;
};
Another question I have is regarding the forward zone.
Apparently my zone forward is not working well, because when i try to Ping the name of the server i get:
srv:/var/lib/named/master # ping srv
ping: unknown host srv
srv:/var/lib/named/master # ping srv.web.lan
ping: unknown host srv.web.lan
srv:/var/lib/named/master # ping tl-wr841.web.lan
ping: unknown host tl-wr841.web.lan
srv:/var/lib/named/master #
My forward zone is now like this :
srv:/var/lib/named/master # cat 192.168.1.zone
$TTL 2D
@ IN SOA srv.web.lan. root.web.lan. (
2015021517 ; serial
1D ; refresh
2H ; retry
1W ; expiry
2D ) ; minimum
IN NS srv
IN MX 10 srv
IN AAA ::1
; A RECORDS
srv IN A 192.168.1.9
srv IN A 10.8.0.1
TL-WR841N IN A 191.168.1.100
;CNAME ALIASES
www IN CNAME srv
ftp IN CNAME srv
srv:/var/lib/named/master #
and my named.conf regarding that forward is like this :
##Local Area network Zone
zone "192.168.1.0.ip4.arpa" in {
type master;
file "/var/lib/named/master/192.168.1.zone";
};
zone "1.168.192.in-addr.arpa" in {
type master;
file "/var/lib/named/master/1.168.192.im-addr.arpa.zone";
};
zone "0.8.10.in-addr.arpa" in {
type master;
file "/var/lib/named/master/0.8.10.in-addr.arpa.zone" ;
};
And here you have my log from var log messages when i start the service
Feb 12 16:43:57 srv named[14029]: adjusted limit on open files from 8192 to 1048576
Feb 12 16:43:57 srv named[14029]: found 2 CPUs, using 2 worker threads
Feb 12 16:43:57 srv named[14029]: using up to 4096 sockets
Feb 12 16:43:57 srv named[14029]: Using 101 tasks for zone loading
Feb 12 16:43:57 srv named[14029]: loading configuration from '/etc/named.conf'
Feb 12 16:43:57 srv named[14029]: using default UDP/IPv4 port range: [1024, 65535]
Feb 12 16:43:57 srv named[14029]: using default UDP/IPv6 port range: [1024, 65535]
Feb 12 16:43:57 srv named[14029]: listening on IPv6 interfaces, port 53
Feb 12 16:43:57 srv named[14029]: listening on IPv4 interface lo, 127.0.0.1#53
Feb 12 16:43:57 srv named[14029]: listening on IPv4 interface eth0, 192.168.1.9#53
Feb 12 16:43:57 srv named[14029]: listening on IPv4 interface tun0, 10.8.0.1#53
Feb 12 16:43:57 srv named[14029]: generating session key for dynamic DNS
Feb 12 16:43:57 srv named[14029]: set up managed keys zone for view _default, file 'managed-keys.bind'
Feb 12 16:43:57 srv named[14029]: automatic empty zone: 0.IN-ADDR.ARPA
Feb 12 16:43:57 srv named[14029]: automatic empty zone: 127.IN-ADDR.ARPA
Feb 12 16:43:57 srv named[14029]: automatic empty zone: 254.169.IN-ADDR.ARPA
Feb 12 16:43:57 srv named[14029]: automatic empty zone: 2.0.192.IN-ADDR.ARPA
Feb 12 16:43:57 srv named[14029]: automatic empty zone: 100.51.198.IN-ADDR.ARPA
Feb 12 16:43:57 srv named[14029]: automatic empty zone: 113.0.203.IN-ADDR.ARPA
Feb 12 16:43:57 srv named[14029]: automatic empty zone: 255.255.255.255.IN-ADDR.ARPA
Feb 12 16:43:57 srv named[14029]: automatic empty zone: 0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.IP6.ARPA
Feb 12 16:43:57 srv named[14029]: automatic empty zone: D.F.IP6.ARPA
Feb 12 16:43:57 srv named[14029]: automatic empty zone: 8.E.F.IP6.ARPA
Feb 12 16:43:57 srv named[14029]: automatic empty zone: 9.E.F.IP6.ARPA
Feb 12 16:43:57 srv named[14029]: automatic empty zone: A.E.F.IP6.ARPA
Feb 12 16:43:57 srv named[14029]: automatic empty zone: B.E.F.IP6.ARPA
Feb 12 16:43:57 srv named[14029]: automatic empty zone: 8.B.D.0.1.0.0.2.IP6.ARPA
Feb 12 16:43:57 srv named[14029]: command channel listening on 127.0.0.1#953
Feb 12 16:43:57 srv named[14029]: command channel listening on ::1#953
Feb 12 16:43:57 srv named[14029]: the working directory is not writable
Feb 12 16:43:57 srv named[14029]: zone 192.168.1.0.ip4.arpa/IN: loading from master file /var/lib/named/master/192.168.1.zone failed: unknown class/type
Feb 12 16:43:57 srv named[14029]: zone 192.168.1.0.ip4.arpa/IN: not loaded due to errors.
Feb 12 16:43:57 srv named[14029]: managed-keys-zone ./IN: loading from master file managed-keys.bind failed: file not found
Thank s