1 Тема от petia

  • petia
  • Новичок
  • Неактивен
  • Зарегистрирован: 25.01.2011
  • Сообщений: 22
  • Репутация : [ 0 | 0 ]

Привет всем.Возникла одна проблема с кофигурацией сервера Dns. Вроде всё эадал правильно в Yast2-dns но вот имена обратных зон не разрешает даёт такую ошибку
piter:~ # dig 192.168.0.210 -x 192.168.0.210

; <<>> DiG 9.7.2-P3 <<>> 192.168.0.210 -x 192.168.0.210
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 32802
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;192.168.0.210. IN A

;; AUTHORITY SECTION:
. 10800 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2011012300 1800 900 604800 86400

;; Query time: 67 msec
;; SERVER: 127.0.0.1#53(127.0.0.1)
;; WHEN: Sun Jan 23 21:39:42 2011
;; MSG SIZE rcvd: 106

;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 11711
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;210.0.168.192.in-addr.arpa. IN PTR

;; Query time: 0 msec
;; SERVER: 127.0.0.1#53(127.0.0.1)
;; WHEN: Sun Jan 23 21:39:42 2011
;; MSG SIZE rcvd: 44

piter:~ # dig piter.casa.com

; <<>> DiG 9.7.2-P3 <<>> piter.casa.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 53812
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;piter.casa.com. IN A

;; ANSWER SECTION:
piter.casa.com. 172800 IN A 192.168.0.210

;; AUTHORITY SECTION:
casa.com. 172800 IN NS piter.casa.com.

;; Query time: 0 msec
;; SERVER: 127.0.0.1#53(127.0.0.1)
;; WHEN: Sun Jan 23 21:43:06 2011
;; MSG SIZE rcvd: 62

помогите пожалуйста разобраться

2 Ответ от andaks

  • andaks
  • Пользователь
  • Неактивен
  • Зарегистрирован: 25.02.2010
  • Сообщений: 128
  • Репутация : [ 6 | 0 ]

а если просто 

dig -x 192.168.0.210

3 Ответ от andaks (25.01.2011 12:50:38 отредактировано andaks)

  • andaks
  • Пользователь
  • Неактивен
  • Зарегистрирован: 25.02.2010
  • Сообщений: 128
  • Репутация : [ 6 | 0 ]

или если с другого сервака резолвить, то:

dig @192.168.0.210 -x 192.168.0.210

Будьте любезны, логи в студию!

4 Ответ от petia

  • petia
  • Новичок
  • Неактивен
  • Зарегистрирован: 25.01.2011
  • Сообщений: 22
  • Репутация : [ 0 | 0 ]

да нет другова сервера я не пойму почему он не разрешает имена обратных зон а сылается на внутриний сервер 127.0.0.1 такое ощущения что где то  что то не прописалось при конфигурации. Я настраивал с Yast2-Dns в графической конфигурации

5 Ответ от andaks

  • andaks
  • Пользователь
  • Неактивен
  • Зарегистрирован: 25.02.2010
  • Сообщений: 128
  • Репутация : [ 6 | 0 ]

Давайте логи.

6 Ответ от petia

  • petia
  • Новичок
  • Неактивен
  • Зарегистрирован: 25.01.2011
  • Сообщений: 22
  • Репутация : [ 0 | 0 ]

сейчас не могу на работе сервак стоит дома

7 Ответ от drBatty

  • drBatty
  • drBatty
  • Пользователь
  • Неактивен
  • Откуда: Петербург
  • Зарегистрирован: 20.02.2010
  • Сообщений: 17,053
  • Репутация : [ 451 | 73 ]
petia пишет:

сейчас не могу на работе сервак стоит дома

настройте ssh. рассказать как?

Карусель разнесло по цепочке за час
Всех известий — конец
Да, весна началась!
(всё к лицу подлецу, как родному отцу, не рассказывай, батя, и так всё пройдёт)

8 Ответ от petia

  • petia
  • Новичок
  • Неактивен
  • Зарегистрирован: 25.01.2011
  • Сообщений: 22
  • Репутация : [ 0 | 0 ]

да если можно

9 Ответ от drBatty

  • drBatty
  • drBatty
  • Пользователь
  • Неактивен
  • Откуда: Петербург
  • Зарегистрирован: 20.02.2010
  • Сообщений: 17,053
  • Репутация : [ 451 | 73 ]

http://linuxforum.ru/viewtopic.php?pid=91418#p91418

Карусель разнесло по цепочке за час
Всех известий — конец
Да, весна началась!
(всё к лицу подлецу, как родному отцу, не рассказывай, батя, и так всё пройдёт)

10 Ответ от petia

  • petia
  • Новичок
  • Неактивен
  • Зарегистрирован: 25.01.2011
  • Сообщений: 22
  • Репутация : [ 0 | 0 ]

извините за глупый вопрос но какие именно логи вам нужны

11 Ответ от petia

  • petia
  • Новичок
  • Неактивен
  • Зарегистрирован: 25.01.2011
  • Сообщений: 22
  • Репутация : [ 0 | 0 ]

и вот последний тест

nslookup
> piter.casa.com
Server:        127.0.0.1
Address:    127.0.0.1#53

Name:    piter.casa.com
Address: 192.168.0.200
> 192.168.0.200
;; Got SERVFAIL reply from 127.0.0.1, trying next server
;; Got SERVFAIL reply from 192.168.0.200, trying next server
;; Got SERVFAIL reply from 127.0.0.1, trying next server
;; Got SERVFAIL reply from 192.168.0.200, trying next server
Server:        212.73.32.3
Address:    212.73.32.3#53

** server can't find 200.0.168.192.in-addr.arpa.: NXDOMAIN

12 Ответ от andaks

  • andaks
  • Пользователь
  • Неактивен
  • Зарегистрирован: 25.02.2010
  • Сообщений: 128
  • Репутация : [ 6 | 0 ]

Логи днс сервера.
Которые могут находиться примерно по следующему пути:
/var/log/named/named.log
/var/log/messages/ с пометкой демона (named)
/var/named/chroot/...../log

Опишите пожалуйста детальнее проблему. Вы настраиваете DNS на локальной машине и посылаете запрос на возврат обратной зоны локального компьютера?

13 Ответ от andaks

  • andaks
  • Пользователь
  • Неактивен
  • Зарегистрирован: 25.02.2010
  • Сообщений: 128
  • Репутация : [ 6 | 0 ]

Отрезолвите обратную зону и высылайте логи:

dig -x 192.168.0.210

14 Ответ от petia

  • petia
  • Новичок
  • Неактивен
  • Зарегистрирован: 25.01.2011
  • Сообщений: 22
  • Репутация : [ 0 | 0 ]

piter:~ # dig -x 192.168.0.200

; <<>> DiG 9.7.1-P2 <<>> -x 192.168.0.200
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 12515
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;200.0.168.192.in-addr.arpa.    IN    PTR

;; Query time: 0 msec
;; SERVER: 127.0.0.1#53(127.0.0.1)
;; WHEN: Tue Jan 25 17:24:38 2011
;; MSG SIZE  rcvd: 44

я заменил ip на 192.168.0.200

15 Ответ от petia (25.01.2011 19:31:19 отредактировано petia)

  • petia
  • Новичок
  • Неактивен
  • Зарегистрирован: 25.01.2011
  • Сообщений: 22
  • Репутация : [ 0 | 0 ]

dig -x piter.casa.com

; <<>> DiG 9.7.1-P2 <<>> -x piter.casa.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 46906
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;com.casa.piter.in-addr.arpa.    IN    PTR

;; AUTHORITY SECTION:
in-addr.arpa.        10361    IN    SOA    A.ROOT-SERVERS.NET. dns-ops.ARIN.NET. 2011012504 1800 900 691200 10800

;; Query time: 33 msec
;; SERVER: 127.0.0.1#53(127.0.0.1)
;; WHEN: Tue Jan 25 17:28:55 2011
;; MSG SIZE  rcvd: 112

dig  piter.casa.com

; <<>> DiG 9.7.1-P2 <<>> piter.casa.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 25468
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;piter.casa.com.            IN    A

;; ANSWER SECTION:
piter.casa.com.        172800    IN    A    192.168.0.200

;; AUTHORITY SECTION:
casa.com.        172800    IN    NS    piter.casa.com.

;; Query time: 0 msec
;; SERVER: 127.0.0.1#53(127.0.0.1)
;; WHEN: Tue Jan 25 17:30:36 2011
;; MSG SIZE  rcvd: 62

16 Ответ от drBatty

  • drBatty
  • drBatty
  • Пользователь
  • Неактивен
  • Откуда: Петербург
  • Зарегистрирован: 20.02.2010
  • Сообщений: 17,053
  • Репутация : [ 451 | 73 ]

petia,

 Консоль:
# cd /var/log
# sed -rn '/named\[[0-9]+\]/p' messages

ещё покажите конфиг:

 Консоль:
# cat /etc/named.conf

Карусель разнесло по цепочке за час
Всех известий — конец
Да, весна началась!
(всё к лицу подлецу, как родному отцу, не рассказывай, батя, и так всё пройдёт)

17 Ответ от petia

  • petia
  • Новичок
  • Неактивен
  • Зарегистрирован: 25.01.2011
  • Сообщений: 22
  • Репутация : [ 0 | 0 ]

Jan 25 16:24:00 piter named[7647]: adjusted limit on open files from 8192 to 1048576
Jan 25 16:24:00 piter named[7647]: found 2 CPUs, using 2 worker threads
Jan 25 16:24:00 piter named[7647]: using up to 4096 sockets
Jan 25 16:24:00 piter named[7647]: loading configuration from '/etc/named.conf'
Jan 25 16:24:00 piter named[7647]: using default UDP/IPv4 port range: [1024, 65535]
Jan 25 16:24:00 piter named[7647]: using default UDP/IPv6 port range: [1024, 65535]
Jan 25 16:24:00 piter named[7647]: listening on IPv6 interfaces, port 53
Jan 25 16:24:00 piter named[7647]: binding TCP socket: address in use
Jan 25 16:24:00 piter named[7647]: listening on IPv4 interface lo, 127.0.0.1#53
Jan 25 16:24:00 piter named[7647]: binding TCP socket: address in use
Jan 25 16:24:00 piter named[7647]: listening on IPv4 interface lo, 127.0.0.2#53
Jan 25 16:24:00 piter named[7647]: binding TCP socket: address in use
Jan 25 16:24:00 piter named[7647]: listening on IPv4 interface eth0, 192.168.0.200#53
Jan 25 16:24:00 piter named[7647]: binding TCP socket: address in use
Jan 25 16:24:00 piter named[7647]: generating session key for dynamic DNS
Jan 25 16:24:00 piter named[7647]: set up managed keys zone for view _default, file 'managed-keys.bind'
Jan 25 16:24:00 piter named[7647]: automatic empty zone: 0.IN-ADDR.ARPA
Jan 25 16:24:00 piter named[7647]: automatic empty zone: 127.IN-ADDR.ARPA
Jan 25 16:24:00 piter named[7647]: automatic empty zone: 254.169.IN-ADDR.ARPA
Jan 25 16:24:00 piter named[7647]: automatic empty zone: 2.0.192.IN-ADDR.ARPA
Jan 25 16:24:00 piter named[7647]: automatic empty zone: 100.51.198.IN-ADDR.ARPA
Jan 25 16:24:00 piter named[7647]: automatic empty zone: 113.0.203.IN-ADDR.ARPA
Jan 25 16:24:00 piter named[7647]: automatic empty zone: 255.255.255.255.IN-ADDR.ARPA
Jan 25 16:24:00 piter named[7647]: 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
Jan 25 16:24:00 piter named[7647]: automatic empty zone: D.F.IP6.ARPA
Jan 25 16:24:00 piter named[7647]: automatic empty zone: 8.E.F.IP6.ARPA
Jan 25 16:24:00 piter named[7647]: automatic empty zone: 9.E.F.IP6.ARPA
Jan 25 16:24:00 piter named[7647]: automatic empty zone: A.E.F.IP6.ARPA
Jan 25 16:24:00 piter named[7647]: automatic empty zone: B.E.F.IP6.ARPA
Jan 25 16:24:00 piter named[7647]: automatic empty zone: 8.B.D.0.1.0.0.2.IP6.ARPA
Jan 25 16:24:00 piter named[7647]: automatic empty zone: 0.1.1.0.0.2.IP6.ARPA
Jan 25 16:24:00 piter named[7647]: command channel listening on 127.0.0.1#953
Jan 25 16:24:00 piter named[7647]: command channel listening on ::1#953
Jan 25 16:24:00 piter named[7647]: the working directory is not writable
Jan 25 16:24:00 piter named[7647]: zone 0.0.127.in-addr.arpa/IN: loaded serial 42
Jan 25 16:24:00 piter named[7647]: zone 0.168.192.in-addr.arpa/IN: NS '200.0.168.192.in-addr.arpa' has no address records (A or AAAA)
Jan 25 16:24:00 piter named[7647]: zone 0.168.192.in-addr.arpa/IN: not loaded due to errors.
Jan 25 16:24:00 piter named[7647]: zone casa.com/IN: loaded serial 2011012400
Jan 25 16:24:00 piter named[7647]: zone localhost/IN: loaded serial 42
Jan 25 16:24:00 piter named[7647]: managed-keys-zone ./IN: loading from master file managed-keys.bind failed: file not found
Jan 25 16:24:00 piter named[7647]: managed-keys-zone ./IN: loaded serial 0
Jan 25 16:24:00 piter named[7647]: running
Jan 25 16:24:37 piter named[7647]: error (network unreachable) resolving 'news.opensuse.org/A/IN': 2001:503:ba3e::2:30#53
Jan 25 16:24:40 piter named[7647]: error (network unreachable) resolving 'news.opensuse.org/AAAA/IN': 2001:500:c::1#53
Jan 25 16:24:40 piter named[7647]: error (network unreachable) resolving 'news.opensuse.org/AAAA/IN': 2001:500:b::1#53
Jan 25 16:24:40 piter named[7647]: error (network unreachable) resolving 'news.opensuse.org/AAAA/IN': 2001:500:f::1#53
Jan 25 16:24:41 piter named[7647]: error (network unreachable) resolving 'planet.opensuse.org/AAAA/IN': 2001:500:c::1#53
Jan 25 16:24:42 piter named[7647]: error (network unreachable) resolving 'ns.novell.co.uk/A/IN': 2001:500:2f::f#53
Jan 25 16:24:44 piter named[7647]: error (network unreachable) resolving 'en-us.fxfeeds.mozilla.com/A/IN': 2001:503:a83e::2:30#53
Jan 25 16:24:44 piter named[7647]: error (network unreachable) resolving 'ns1.westnet.net/A/IN': 2001:dc3::35#53
Jan 25 16:24:44 piter named[7647]: error (network unreachable) resolving 'ns1.westnet.net/AAAA/IN': 2001:7fd::1#53
Jan 25 16:24:44 piter named[7647]: success resolving 'news.opensuse.org/AAAA' (in 'opensuse.org'?) after reducing the advertised EDNS UDP packet size to 512 octets
Jan 25 16:24:45 piter named[7647]: error (network unreachable) resolving 'www.linux4me.org/AAAA/IN': 2001:500:40::1#53
Jan 25 16:24:45 piter named[7647]: success resolving 'planet.opensuse.org/A' (in 'opensuse.org'?) after reducing the advertised EDNS UDP packet size to 512 octets
Jan 25 16:24:45 piter named[7647]: success resolving 'planet.opensuse.org/AAAA' (in 'opensuse.org'?) after reducing the advertised EDNS UDP packet size to 512 octets
Jan 25 16:24:46 piter named[7647]: error (network unreachable) resolving 'ns1.mozilla.org/A/IN': 2001:500:48::1#53
Jan 25 16:24:46 piter named[7647]: error (network unreachable) resolving 'ns1.mozilla.org/A/IN': 2001:500:e::1#53
Jan 25 16:24:46 piter named[7647]: error (network unreachable) resolving 'ns1.mozilla.org/A/IN': 2001:500:40::1#53
Jan 25 16:24:46 piter named[7647]: error (network unreachable) resolving 'ns1.mozilla.org/AAAA/IN': 2001:500:e::1#53
Jan 25 16:24:46 piter named[7647]: error (network unreachable) resolving 'ns1.mozilla.org/AAAA/IN': 2001:500:48::1#53
Jan 25 16:24:46 piter named[7647]: error (network unreachable) resolving 'ns2.mozilla.org/A/IN': 2001:500:40::1#53
Jan 25 16:24:46 piter named[7647]: error (network unreachable) resolving 'ns3.mozilla.org/A/IN': 2001:500:40::1#53
Jan 25 16:24:46 piter named[7647]: error (network unreachable) resolving 'ns3.mozilla.org/AAAA/IN': 2001:500:48::1#53
Jan 25 16:24:46 piter named[7647]: success resolving 'news.opensuse.org/A' (in 'opensuse.org'?) after reducing the advertised EDNS UDP packet size to 512 octets
Jan 25 16:24:46 piter named[7647]: error (network unreachable) resolving 'ns1.westnet.net/A/IN': 2001:503:231d::2:30#53
Jan 25 16:24:47 piter named[7647]: error (network unreachable) resolving 'linuxforum.ru/A/IN': 2001:660:3005:1::1:2#53
Jan 25 16:24:47 piter named[7647]: error (network unreachable) resolving 'linuxforum.ru/A/IN': 2001:678:16:0:194:85:252:62#53
Jan 25 16:24:47 piter named[7647]: error (network unreachable) resolving 'linuxforum.ru/A/IN': 2001:678:15:0:193:232:142:17#53
Jan 25 16:24:47 piter named[7647]: error (network unreachable) resolving 'linuxforum.ru/A/IN': 2001:678:17:0:193:232:128:6#53
Jan 25 16:24:47 piter named[7647]: error (network unreachable) resolving 'linuxforum.ru/A/IN': 2001:678:14:0:193:232:156:17#53
Jan 25 16:24:47 piter named[7647]: error (network unreachable) resolving 'linuxforum.ru/A/IN': 2001:678:13:0:194:85:105:17#53
Jan 25 16:24:47 piter named[7647]: error (network unreachable) resolving 'ns1.peterhost.ru/AAAA/IN': 2001:678:14:0:193:232:156:17#53
Jan 25 16:24:47 piter named[7647]: error (network unreachable) resolving 'ns1.peterhost.ru/AAAA/IN': 2001:678:17:0:193:232:128:6#53
Jan 25 16:24:47 piter named[7647]: error (network unreachable) resolving 'planet.opensu.se/A/IN': 2001:503:c27::2:30#53
Jan 25 16:24:47 piter named[7647]: error (network unreachable) resolving 'win.mail.ru/AAAA/IN': 2001:678:16:0:194:85:252:62#53
Jan 25 16:24:47 piter named[7647]: error (network unreachable) resolving 'img.imgsmail.ru/AAAA/IN': 2001:678:13:0:194:85:105:17#53
Jan 25 16:24:47 piter named[7647]: error (network unreachable) resolving 'img.imgsmail.ru/AAAA/IN': 2001:678:15:0:193:232:142:17#53
Jan 25 16:24:49 piter named[7647]: success resolving 'en-us.fxfeeds.mozilla.com/A' (in 'mozilla.com'?) after reducing the advertised EDNS UDP packet size to 512 octets
Jan 25 16:24:49 piter named[7647]: error (unexpected RCODE REFUSED) resolving 'ns1.westnet.net/A/IN': 128.110.124.120#53
Jan 25 16:24:51 piter named[7647]: success resolving 'en-us.fxfeeds.mozilla.com/AAAA' (in 'mozilla.com'?) after reducing the advertised EDNS UDP packet size to 512 octets
Jan 25 16:24:53 piter named[7647]: success resolving 'www.linux4me.org/A' (in 'linux4me.org'?) after reducing the advertised EDNS UDP packet size to 512 octets
Jan 25 16:24:53 piter named[7647]: success resolving 'www.linux4me.org/AAAA' (in 'linux4me.org'?) after reducing the advertised EDNS UDP packet size to 512 octets
Jan 25 16:24:54 piter named[7647]: success resolving 'linuxforum.ru/AAAA' (in 'linuxforum.ru'?) after reducing the advertised EDNS UDP packet size to 512 octets
Jan 25 16:24:54 piter named[7647]: error (network unreachable) resolving 'ns1.variomedia.de/A/IN': 2001:500:1::803f:235#53
Jan 25 16:24:54 piter named[7647]: error (network unreachable) resolving 'ns2.variomedia.de/A/IN': 2001:500:1::803f:235#53
Jan 25 16:24:54 piter named[7647]: error (network unreachable) resolving 'ns1.variomedia.de/AAAA/IN': 2001:500:1::803f:235#53
Jan 25 16:24:57 piter named[7647]: success resolving 'linuxforum.ru/A' (in 'linuxforum.ru'?) after reducing the advertised EDNS UDP packet size to 512 octets
Jan 25 16:24:57 piter named[7647]: error (network unreachable) resolving 'ns1.variomedia.de/A/IN': 2001:678:2::53#53
Jan 25 16:24:57 piter named[7647]: error (network unreachable) resolving 'ns1.variomedia.de/A/IN': 2a02:568:0:2::53#53
Jan 25 16:24:57 piter named[7647]: error (network unreachable) resolving 'ns1.variomedia.de/A/IN': 2001:668:1f:11::105#53
Jan 25 16:24:58 piter named[7647]: error (network unreachable) resolving 'ns2.variomedia.de/A/IN': 2001:678:2::53#53
Jan 25 16:24:58 piter named[7647]: error (network unreachable) resolving 'ns2.variomedia.de/AAAA/IN': 2001:668:1f:11::105#53
Jan 25 16:25:01 piter named[7647]: success resolving 'planet.opensu.se/A' (in 'opensu.se'?) after reducing the advertised EDNS UDP packet size to 512 octets
Jan 25 16:25:01 piter named[7647]: clients-per-query increased to 15
Jan 25 16:25:06 piter named[7647]: success resolving 'planet.opensu.se/AAAA' (in 'opensu.se'?) after reducing the advertised EDNS UDP packet size to 512 octets
Jan 25 16:25:12 piter named[7647]: success resolving 'www.tns-counter.ru/A' (in 'tns-counter.ru'?) after reducing the advertised EDNS UDP packet size to 512 octets
Jan 25 16:25:17 piter named[7647]: success resolving 'www.tns-counter.ru/AAAA' (in 'tns-counter.ru'?) after reducing the advertised EDNS UDP packet size to 512 octets
Jan 25 16:25:42 piter named[7647]: success resolving 'newsrss.bbc.net.uk/A' (in 'bbc.net.uk'?) after reducing the advertised EDNS UDP packet size to 512 octets
Jan 25 16:25:42 piter named[7647]: success resolving 'newsrss.bbc.net.uk/AAAA' (in 'bbc.net.uk'?) after reducing the advertised EDNS UDP packet size to 512 octets
Jan 25 16:26:49 piter named[7647]: success resolving 'corp.mail.ru/AAAA' (in 'corp.mail.ru'?) after reducing the advertised EDNS UDP packet size to 512 octets
Jan 25 16:27:11 piter named[7647]: received control channel command 'reload'
Jan 25 16:27:11 piter named[7647]: loading configuration from '/etc/named.conf'
Jan 25 16:27:11 piter named[7647]: using default UDP/IPv4 port range: [1024, 65535]
Jan 25 16:27:11 piter named[7647]: using default UDP/IPv6 port range: [1024, 65535]
Jan 25 16:27:11 piter named[7647]: set up managed keys zone for view _default, file 'managed-keys.bind'
Jan 25 16:27:11 piter named[7647]: the working directory is not writable
Jan 25 16:27:11 piter named[7647]: reloading configuration succeeded
Jan 25 16:27:11 piter named[7647]: zone 0.168.192.in-addr.arpa/IN: NS '200.0.168.192.in-addr.arpa' has no address records (A or AAAA)
Jan 25 16:27:11 piter named[7647]: zone 0.168.192.in-addr.arpa/IN: not loaded due to errors.
Jan 25 16:27:11 piter named[7647]: managed-keys-zone ./IN: loading from master file managed-keys.bind failed: file not found
Jan 25 16:27:11 piter named[7647]: managed-keys-zone ./IN: loaded serial 0
Jan 25 16:27:11 piter named[7647]: reloading zones succeeded
Jan 25 16:27:11 piter named[7647]: received control channel command 'reload'
Jan 25 16:27:11 piter named[7647]: loading configuration from '/etc/named.conf'
Jan 25 16:27:11 piter named[7647]: using default UDP/IPv4 port range: [1024, 65535]
Jan 25 16:27:11 piter named[7647]: using default UDP/IPv6 port range: [1024, 65535]
Jan 25 16:27:11 piter named[7647]: set up managed keys zone for view _default, file 'managed-keys.bind'
Jan 25 16:27:11 piter named[7647]: the working directory is not writable
Jan 25 16:27:11 piter named[7647]: reloading configuration succeeded
Jan 25 16:27:11 piter named[7647]: zone 0.168.192.in-addr.arpa/IN: NS '200.0.168.192.in-addr.arpa' has no address records (A or AAAA)
Jan 25 16:27:11 piter named[7647]: zone 0.168.192.in-addr.arpa/IN: not loaded due to errors.
Jan 25 16:27:11 piter named[7647]: managed-keys-zone ./IN: loading from master file managed-keys.bind failed: file not found
Jan 25 16:27:11 piter named[7647]: managed-keys-zone ./IN: loaded serial 0
Jan 25 16:27:11 piter named[7647]: reloading zones succeeded
Jan 25 16:30:03 piter named[7647]: error (network unreachable) resolving 'ru.wikinews.org/AAAA/IN': 2001:500:40::1#53
Jan 25 16:30:03 piter named[7647]: error (network unreachable) resolving 'ru.wikinews.org/AAAA/IN': 2001:500:c::1#53
Jan 25 16:30:16 piter named[7647]: error (network unreachable) resolving 'www.abc-it.lv/AAAA/IN': 2001:500:2f::f#53
Jan 25 16:30:16 piter named[7647]: error (network unreachable) resolving 'www.abc-it.lv/AAAA/IN': 2001:503:c27::2:30#53
Jan 25 16:30:17 piter named[7647]: success resolving 'www.abc-it.lv/AAAA' (in 'lv'?) after reducing the advertised EDNS UDP packet size to 512 octets
Jan 25 16:30:19 piter named[7647]: success resolving 'www.abc-it.lv/A' (in 'lv'?) after reducing the advertised EDNS UDP packet size to 512 octets
Jan 25 16:30:40 piter named[7647]: error (network unreachable) resolving 'microsin.ru/AAAA/IN': 2001:678:15:0:193:232:142:17#53
Jan 25 16:30:40 piter named[7647]: success resolving 'microsin.ru/A' (in 'microsin.ru'?) after reducing the advertised EDNS UDP packet size to 512 octets
Jan 25 16:30:41 piter named[7647]: success resolving 'microsin.ru/AAAA' (in 'microsin.ru'?) after reducing the advertised EDNS UDP packet size to 512 octets
Jan 25 16:47:08 piter named[7647]: received control channel command 'reload'
Jan 25 16:47:08 piter named[7647]: loading configuration from '/etc/named.conf'
Jan 25 16:47:08 piter named[7647]: using default UDP/IPv4 port range: [1024, 65535]
Jan 25 16:47:08 piter named[7647]: using default UDP/IPv6 port range: [1024, 65535]
Jan 25 16:47:08 piter named[7647]: set up managed keys zone for view _default, file 'managed-keys.bind'
Jan 25 16:47:08 piter named[7647]: the working directory is not writable
Jan 25 16:47:08 piter named[7647]: reloading configuration succeeded
Jan 25 16:47:08 piter named[7647]: zone 0.168.192.in-addr.arpa/IN: NS '200.0.168.192.in-addr.arpa' has no address records (A or AAAA)
Jan 25 16:47:08 piter named[7647]: zone 0.168.192.in-addr.arpa/IN: not loaded due to errors.
Jan 25 16:47:08 piter named[7647]: managed-keys-zone ./IN: loading from master file managed-keys.bind failed: file not found
Jan 25 16:47:08 piter named[7647]: managed-keys-zone ./IN: loaded serial 0
Jan 25 16:47:08 piter named[7647]: reloading zones succeeded
Jan 25 16:47:13 piter named[7647]: received control channel command 'reload'
Jan 25 16:47:13 piter named[7647]: loading configuration from '/etc/named.conf'
Jan 25 16:47:13 piter named[7647]: using default UDP/IPv4 port range: [1024, 65535]
Jan 25 16:47:13 piter named[7647]: using default UDP/IPv6 port range: [1024, 65535]
Jan 25 16:47:13 piter named[7647]: set up managed keys zone for view _default, file 'managed-keys.bind'
Jan 25 16:47:13 piter named[7647]: the working directory is not writable
Jan 25 16:47:13 piter named[7647]: reloading configuration succeeded
Jan 25 16:47:13 piter named[7647]: zone 0.168.192.in-addr.arpa/IN: NS '200.0.168.192.in-addr.arpa' has no address records (A or AAAA)
Jan 25 16:47:13 piter named[7647]: zone 0.168.192.in-addr.arpa/IN: not loaded due to errors.
Jan 25 16:47:13 piter named[7647]: managed-keys-zone ./IN: loading from master file managed-keys.bind failed: file not found
Jan 25 16:47:13 piter named[7647]: managed-keys-zone ./IN: loaded serial 0
Jan 25 16:47:13 piter named[7647]: reloading zones succeeded
Jan 25 16:54:26 piter named[7647]: received control channel command 'stop'
Jan 25 16:54:26 piter named[7647]: shutting down: flushing changes
Jan 25 16:54:26 piter named[7647]: stopping command channel on 127.0.0.1#953
Jan 25 16:54:26 piter named[7647]: stopping command channel on ::1#953
Jan 25 16:54:26 piter named[7647]: no longer listening on ::#53
Jan 25 16:54:26 piter named[7647]: no longer listening on 127.0.0.1#53
Jan 25 16:54:26 piter named[7647]: no longer listening on 127.0.0.2#53
Jan 25 16:54:26 piter named[7647]: no longer listening on 192.168.0.200#53
Jan 25 16:54:26 piter named[7647]: exiting
Jan 25 16:54:28 piter named[11170]: starting BIND 9.7.1-P2 -t /var/lib/named -u named
Jan 25 16:54:28 piter named[11170]: built with '--prefix=/usr' '--bindir=/usr/bin' '--sbindir=/usr/sbin' '--sysconfdir=/etc' '--localstatedir=/var' '--libdir=/usr/lib' '--includedir=/usr/include/bind' '--mandir=/usr/share/man' '--infodir=/usr/share/info' '--with-openssl' '--enable-threads' '--with-libtool' '--enable-runidn' '--with-libxml2' '--with-dlz-mysql' '--with-dlz-ldap' 'CFLAGS=-fomit-frame-pointer -fmessage-length=0 -O2 -Wall -D_FORTIFY_SOURCE=2 -fstack-protector -funwind-tables -fasynchronous-unwind-tables -g -fno-strict-aliasing' 'LDFLAGS=-L/usr/lib'
Jan 25 16:54:28 piter named[11170]: adjusted limit on open files from 8192 to 1048576
Jan 25 16:54:28 piter named[11170]: found 2 CPUs, using 2 worker threads
Jan 25 16:54:28 piter named[11170]: using up to 4096 sockets
Jan 25 16:54:28 piter named[11170]: loading configuration from '/etc/named.conf'
Jan 25 16:54:28 piter named[11170]: using default UDP/IPv4 port range: [1024, 65535]
Jan 25 16:54:28 piter named[11170]: using default UDP/IPv6 port range: [1024, 65535]
Jan 25 16:54:28 piter named[11170]: listening on IPv6 interfaces, port 53
Jan 25 16:54:28 piter named[11170]: binding TCP socket: address in use
Jan 25 16:54:28 piter named[11170]: listening on IPv4 interface lo, 127.0.0.1#53
Jan 25 16:54:28 piter named[11170]: binding TCP socket: address in use
Jan 25 16:54:28 piter named[11170]: listening on IPv4 interface lo, 127.0.0.2#53
Jan 25 16:54:28 piter named[11170]: binding TCP socket: address in use
Jan 25 16:54:28 piter named[11170]: listening on IPv4 interface eth0, 192.168.0.200#53
Jan 25 16:54:28 piter named[11170]: binding TCP socket: address in use
Jan 25 16:54:28 piter named[11170]: generating session key for dynamic DNS
Jan 25 16:54:28 piter named[11170]: set up managed keys zone for view _default, file 'managed-keys.bind'
Jan 25 16:54:28 piter named[11170]: automatic empty zone: 0.IN-ADDR.ARPA
Jan 25 16:54:28 piter named[11170]: automatic empty zone: 127.IN-ADDR.ARPA
Jan 25 16:54:28 piter named[11170]: automatic empty zone: 254.169.IN-ADDR.ARPA
Jan 25 16:54:28 piter named[11170]: automatic empty zone: 2.0.192.IN-ADDR.ARPA
Jan 25 16:54:28 piter named[11170]: automatic empty zone: 100.51.198.IN-ADDR.ARPA
Jan 25 16:54:28 piter named[11170]: automatic empty zone: 113.0.203.IN-ADDR.ARPA
Jan 25 16:54:28 piter named[11170]: automatic empty zone: 255.255.255.255.IN-ADDR.ARPA
Jan 25 16:54:28 piter named[11170]: 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
Jan 25 16:54:28 piter named[11170]: automatic empty zone: D.F.IP6.ARPA
Jan 25 16:54:28 piter named[11170]: automatic empty zone: 8.E.F.IP6.ARPA
Jan 25 16:54:28 piter named[11170]: automatic empty zone: 9.E.F.IP6.ARPA
Jan 25 16:54:28 piter named[11170]: automatic empty zone: A.E.F.IP6.ARPA
Jan 25 16:54:28 piter named[11170]: automatic empty zone: B.E.F.IP6.ARPA
Jan 25 16:54:28 piter named[11170]: automatic empty zone: 8.B.D.0.1.0.0.2.IP6.ARPA
Jan 25 16:54:28 piter named[11170]: automatic empty zone: 0.1.1.0.0.2.IP6.ARPA
Jan 25 16:54:28 piter named[11170]: command channel listening on 127.0.0.1#953
Jan 25 16:54:28 piter named[11170]: command channel listening on ::1#953
Jan 25 16:54:28 piter named[11170]: the working directory is not writable
Jan 25 16:54:28 piter named[11170]: zone 0.0.127.in-addr.arpa/IN: loaded serial 42
Jan 25 16:54:28 piter named[11170]: zone 0.168.192.in-addr.arpa/IN: NS '200.0.168.192.in-addr.arpa' has no address records (A or AAAA)
Jan 25 16:54:28 piter named[11170]: zone 0.168.192.in-addr.arpa/IN: not loaded due to errors.
Jan 25 16:54:28 piter named[11170]: zone casa.com/IN: loaded serial 2011012400
Jan 25 16:54:28 piter named[11170]: zone localhost/IN: loaded serial 42
Jan 25 16:54:28 piter named[11170]: managed-keys-zone ./IN: loading from master file managed-keys.bind failed: file not found
Jan 25 16:54:28 piter named[11170]: managed-keys-zone ./IN: loaded serial 0
Jan 25 16:54:28 piter named[11170]: running
Jan 25 16:55:31 piter named[11170]: received control channel command 'reload'
Jan 25 16:55:31 piter named[11170]: loading configuration from '/etc/named.conf'
Jan 25 16:55:31 piter named[11170]: using default UDP/IPv4 port range: [1024, 65535]
Jan 25 16:55:31 piter named[11170]: using default UDP/IPv6 port range: [1024, 65535]
Jan 25 16:55:31 piter named[11170]: set up managed keys zone for view _default, file 'managed-keys.bind'
Jan 25 16:55:31 piter named[11170]: the working directory is not writable
Jan 25 16:55:31 piter named[11170]: reloading configuration succeeded
Jan 25 16:55:31 piter named[11170]: zone 0.168.192.in-addr.arpa/IN: NS '0.168.192.in-addr.arpa' has no address records (A or AAAA)
Jan 25 16:55:31 piter named[11170]: zone 0.168.192.in-addr.arpa/IN: not loaded due to errors.
Jan 25 16:55:31 piter named[11170]: managed-keys-zone ./IN: loading from master file managed-keys.bind failed: file not found
Jan 25 16:55:31 piter named[11170]: managed-keys-zone ./IN: loaded serial 0
Jan 25 16:55:31 piter named[11170]: reloading zones succeeded
Jan 25 17:04:23 piter named[11170]: received control channel command 'reload'
Jan 25 17:04:23 piter named[11170]: loading configuration from '/etc/named.conf'
Jan 25 17:04:23 piter named[11170]: using default UDP/IPv4 port range: [1024, 65535]
Jan 25 17:04:23 piter named[11170]: using default UDP/IPv6 port range: [1024, 65535]
Jan 25 17:04:23 piter named[11170]: set up managed keys zone for view _default, file 'managed-keys.bind'
Jan 25 17:04:23 piter named[11170]: the working directory is not writable
Jan 25 17:04:23 piter named[11170]: reloading configuration succeeded
Jan 25 17:04:23 piter named[11170]: zone 0.168.192.in-addr.arpa/IN: NS '200.0.168.192.in-addr.arpa' has no address records (A or AAAA)
Jan 25 17:04:23 piter named[11170]: zone 0.168.192.in-addr.arpa/IN: not loaded due to errors.
Jan 25 17:04:23 piter named[11170]: managed-keys-zone ./IN: loading from master file managed-keys.bind failed: file not found
Jan 25 17:04:23 piter named[11170]: managed-keys-zone ./IN: loaded serial 0
Jan 25 17:04:23 piter named[11170]: reloading zones succeeded
Jan 25 17:04:38 piter named[11170]: received control channel command 'reload'
Jan 25 17:04:38 piter named[11170]: loading configuration from '/etc/named.conf'
Jan 25 17:04:38 piter named[11170]: using default UDP/IPv4 port range: [1024, 65535]
Jan 25 17:04:38 piter named[11170]: using default UDP/IPv6 port range: [1024, 65535]
Jan 25 17:04:38 piter named[11170]: set up managed keys zone for view _default, file 'managed-keys.bind'
Jan 25 17:04:38 piter named[11170]: the working directory is not writable
Jan 25 17:04:38 piter named[11170]: reloading configuration succeeded
Jan 25 17:04:38 piter named[11170]: zone 0.168.192.in-addr.arpa/IN: NS '200.0.168.192.in-addr.arpa' has no address records (A or AAAA)
Jan 25 17:04:38 piter named[11170]: zone 0.168.192.in-addr.arpa/IN: not loaded due to errors.
Jan 25 17:04:38 piter named[11170]: managed-keys-zone ./IN: loading from master file managed-keys.bind failed: file not found
Jan 25 17:04:38 piter named[11170]: managed-keys-zone ./IN: loaded serial 0
Jan 25 17:04:38 piter named[11170]: reloading zones succeeded
Jan 25 17:12:59 piter named[11170]: received control channel command 'stop'
Jan 25 17:12:59 piter named[11170]: shutting down: flushing changes
Jan 25 17:12:59 piter named[11170]: stopping command channel on 127.0.0.1#953
Jan 25 17:12:59 piter named[11170]: stopping command channel on ::1#953
Jan 25 17:12:59 piter named[11170]: no longer listening on ::#53
Jan 25 17:12:59 piter named[11170]: no longer listening on 127.0.0.1#53
Jan 25 17:12:59 piter named[11170]: no longer listening on 127.0.0.2#53
Jan 25 17:12:59 piter named[11170]: no longer listening on 192.168.0.200#53
Jan 25 17:12:59 piter named[11170]: exiting
Jan 25 17:13:01 piter named[15647]: starting BIND 9.7.1-P2 -t /var/lib/named -u named
Jan 25 17:13:01 piter named[15647]: built with '--prefix=/usr' '--bindir=/usr/bin' '--sbindir=/usr/sbin' '--sysconfdir=/etc' '--localstatedir=/var' '--libdir=/usr/lib' '--includedir=/usr/include/bind' '--mandir=/usr/share/man' '--infodir=/usr/share/info' '--with-openssl' '--enable-threads' '--with-libtool' '--enable-runidn' '--with-libxml2' '--with-dlz-mysql' '--with-dlz-ldap' 'CFLAGS=-fomit-frame-pointer -fmessage-length=0 -O2 -Wall -D_FORTIFY_SOURCE=2 -fstack-protector -funwind-tables -fasynchronous-unwind-tables -g -fno-strict-aliasing' 'LDFLAGS=-L/usr/lib'
Jan 25 17:13:01 piter named[15647]: adjusted limit on open files from 8192 to 1048576
Jan 25 17:13:01 piter named[15647]: found 2 CPUs, using 2 worker threads
Jan 25 17:13:01 piter named[15647]: using up to 4096 sockets
Jan 25 17:13:01 piter named[15647]: loading configuration from '/etc/named.conf'
Jan 25 17:13:01 piter named[15647]: using default UDP/IPv4 port range: [1024, 65535]
Jan 25 17:13:01 piter named[15647]: using default UDP/IPv6 port range: [1024, 65535]
Jan 25 17:13:01 piter named[15647]: listening on IPv6 interfaces, port 53
Jan 25 17:13:01 piter named[15647]: binding TCP socket: address in use
Jan 25 17:13:01 piter named[15647]: listening on IPv4 interface lo, 127.0.0.1#53
Jan 25 17:13:01 piter named[15647]: binding TCP socket: address in use
Jan 25 17:13:01 piter named[15647]: listening on IPv4 interface lo, 127.0.0.2#53
Jan 25 17:13:01 piter named[15647]: binding TCP socket: address in use
Jan 25 17:13:01 piter named[15647]: listening on IPv4 interface eth0, 192.168.0.200#53
Jan 25 17:13:01 piter named[15647]: binding TCP socket: address in use
Jan 25 17:13:01 piter named[15647]: generating session key for dynamic DNS
Jan 25 17:13:01 piter named[15647]: set up managed keys zone for view _default, file 'managed-keys.bind'
Jan 25 17:13:01 piter named[15647]: automatic empty zone: 0.IN-ADDR.ARPA
Jan 25 17:13:01 piter named[15647]: automatic empty zone: 127.IN-ADDR.ARPA
Jan 25 17:13:01 piter named[15647]: automatic empty zone: 254.169.IN-ADDR.ARPA
Jan 25 17:13:01 piter named[15647]: automatic empty zone: 2.0.192.IN-ADDR.ARPA
Jan 25 17:13:01 piter named[15647]: automatic empty zone: 100.51.198.IN-ADDR.ARPA
Jan 25 17:13:01 piter named[15647]: automatic empty zone: 113.0.203.IN-ADDR.ARPA
Jan 25 17:13:01 piter named[15647]: automatic empty zone: 255.255.255.255.IN-ADDR.ARPA
Jan 25 17:13:01 piter named[15647]: 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
Jan 25 17:13:01 piter named[15647]: automatic empty zone: D.F.IP6.ARPA
Jan 25 17:13:01 piter named[15647]: automatic empty zone: 8.E.F.IP6.ARPA
Jan 25 17:13:01 piter named[15647]: automatic empty zone: 9.E.F.IP6.ARPA
Jan 25 17:13:01 piter named[15647]: automatic empty zone: A.E.F.IP6.ARPA
Jan 25 17:13:01 piter named[15647]: automatic empty zone: B.E.F.IP6.ARPA
Jan 25 17:13:01 piter named[15647]: automatic empty zone: 8.B.D.0.1.0.0.2.IP6.ARPA
Jan 25 17:13:01 piter named[15647]: automatic empty zone: 0.1.1.0.0.2.IP6.ARPA
Jan 25 17:13:01 piter named[15647]: command channel listening on 127.0.0.1#953
Jan 25 17:13:01 piter named[15647]: command channel listening on ::1#953
Jan 25 17:13:01 piter named[15647]: the working directory is not writable
Jan 25 17:13:01 piter named[15647]: zone 0.0.127.in-addr.arpa/IN: loaded serial 42
Jan 25 17:13:01 piter named[15647]: zone 0.168.192.in-addr.arpa/IN: NS '200.0.168.192.in-addr.arpa' has no address records (A or AAAA)
Jan 25 17:13:01 piter named[15647]: zone 0.168.192.in-addr.arpa/IN: not loaded due to errors.
Jan 25 17:13:01 piter named[15647]: zone casa.com/IN: loaded serial 2011012400
Jan 25 17:13:01 piter named[15647]: zone localhost/IN: loaded serial 42
Jan 25 17:13:01 piter named[15647]: managed-keys-zone ./IN: loading from master file managed-keys.bind failed: file not found
Jan 25 17:13:01 piter named[15647]: managed-keys-zone ./IN: loaded serial 0
Jan 25 17:13:01 piter named[15647]: running
Jan 25 17:14:05 piter named[15647]: received control channel command 'reload'
Jan 25 17:14:05 piter named[15647]: loading configuration from '/etc/named.conf'
Jan 25 17:14:05 piter named[15647]: using default UDP/IPv4 port range: [1024, 65535]
Jan 25 17:14:05 piter named[15647]: using default UDP/IPv6 port range: [1024, 65535]
Jan 25 17:14:05 piter named[15647]: set up managed keys zone for view _default, file 'managed-keys.bind'
Jan 25 17:14:05 piter named[15647]: the working directory is not writable
Jan 25 17:14:05 piter named[15647]: reloading configuration succeeded
Jan 25 17:14:05 piter named[15647]: zone 0.168.192.in-addr.arpa/IN: NS '200.0.168.192.in-addr.arpa' has no address records (A or AAAA)
Jan 25 17:14:05 piter named[15647]: zone 0.168.192.in-addr.arpa/IN: not loaded due to errors.
Jan 25 17:14:05 piter named[15647]: managed-keys-zone ./IN: loading from master file managed-keys.bind failed: file not found
Jan 25 17:14:05 piter named[15647]: managed-keys-zone ./IN: loaded serial 0
Jan 25 17:14:05 piter named[15647]: reloading zones succeeded
Jan 25 17:14:05 piter named[15647]: zone casa.com/IN: loaded serial 2011012500
Jan 25 17:22:40 piter named[15647]: received control channel command 'reload'
Jan 25 17:22:40 piter named[15647]: loading configuration from '/etc/named.conf'
Jan 25 17:22:40 piter named[15647]: using default UDP/IPv4 port range: [1024, 65535]
Jan 25 17:22:40 piter named[15647]: using default UDP/IPv6 port range: [1024, 65535]
Jan 25 17:22:40 piter named[15647]: set up managed keys zone for view _default, file 'managed-keys.bind'
Jan 25 17:22:40 piter named[15647]: the working directory is not writable
Jan 25 17:22:40 piter named[15647]: reloading configuration succeeded
Jan 25 17:22:40 piter named[15647]: zone 0.168.192.in-addr.arpa/IN: NS '200.0.168.192.in-addr.arpa' has no address records (A or AAAA)
Jan 25 17:22:40 piter named[15647]: zone 0.168.192.in-addr.arpa/IN: not loaded due to errors.
Jan 25 17:22:40 piter named[15647]: managed-keys-zone ./IN: loading from master file managed-keys.bind failed: file not found
Jan 25 17:22:40 piter named[15647]: managed-keys-zone ./IN: loaded serial 0
Jan 25 17:22:40 piter named[15647]: zone casa.com/IN: zone serial (2011012500) unchanged. zone may fail to transfer to slaves.
Jan 25 17:22:40 piter named[15647]: zone casa.com/IN: loaded serial 2011012500
Jan 25 17:22:40 piter named[15647]: reloading zones succeeded




cat /etc/named.conf
# Copyright (c) 2001-2004 SuSE Linux AG, Nuernberg, Germany.
# All rights reserved.
#
# Author: Frank Bodammer, Lars Mueller <lmuelle@suse.de>
#
# /etc/named.conf
#
# This is a sample configuration file for the name server BIND 9.  It works as
# a caching only name server without modification.
#
# A sample configuration for setting up your own domain can be found in
# /usr/share/doc/packages/bind/sample-config.
#
# A description of all available options can be found in
# /usr/share/doc/packages/bind/misc/options.

options {

    # The directory statement defines the name server's working directory

    directory "/var/lib/named";

    # Write dump and statistics file to the log subdirectory.  The
    # pathenames are relative to the chroot jail.

    dump-file "/var/log/named_dump.db";
    statistics-file "/var/log/named.stats";

    # The forwarders record contains a list of servers to which queries
    # should be forwarded.  Enable this line and modify the IP address to
    # your provider's name server.  Up to three servers may be listed.

    #forwarders { 192.0.2.1; 192.0.2.2; };

    # Enable the next entry to prefer usage of the name server declared in
    # the forwarders section.

    #forward first;

    # The listen-on record contains a list of local network interfaces to
    # listen on.  Optionally the port can be specified.  Default is to
    # listen on all interfaces found on your system.  The default port is
    # 53.

    #listen-on port 53 { 127.0.0.1; };

    # The listen-on-v6 record enables or disables listening on IPv6
    # interfaces.  Allowed values are 'any' and 'none' or a list of
    # addresses.

    listen-on-v6 { any; };

    # The next three statements may be needed if a firewall stands between
    # the local server and the internet.

    #query-source address * port 53;
    #transfer-source * port 53;
    #notify-source * port 53;

    # The allow-query record contains a list of networks or IP addresses
    # to accept and deny queries from. The default is to allow queries
    # from all hosts.

    #allow-query { 127.0.0.1; };

    # If notify is set to yes (default), notify messages are sent to other
    # name servers when the the zone data is changed.  Instead of setting
    # a global 'notify' statement in the 'options' section, a separate
    # 'notify' can be added to each zone definition.

    notify no;

    disable-empty-zone "1.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";
    include "/etc/named.d/forwarders.conf";
};

# To configure named's logging remove the leading '#' characters of the
# following examples.
#logging {
#    # Log queries to a file limited to a size of 100 MB.
#    channel query_logging {
#        file "/var/log/named_querylog"
#            versions 3 size 100M;
#        print-time yes;            // timestamp log entries
#    };
#    category queries {
#        query_logging;
#    };
#
#    # Or log this kind alternatively to syslog.
#    channel syslog_queries {
#        syslog user;
#        severity info;
#    };
#    category queries { syslog_queries; };
#
#    # Log general name server errors to syslog.
#    channel syslog_errors {
#        syslog user;
#        severity error;
#    };
#    category default { syslog_errors;  };
#
#    # Don't log lame server messages.
#    category lame-servers { null; };
#};

# The following zone definitions don't need any modification.  The first one
# is the definition of the root name servers.  The second one defines
# localhost while the third defines the reverse lookup for localhost.

zone "." in {
    type hint;
    file "root.hint";
};

zone "localhost" in {
    type master;
    file "localhost.zone";
};

zone "0.0.127.in-addr.arpa" in {
    type master;
    file "127.0.0.zone";
};


# Include the meta include file generated by createNamedConfInclude.  This
# includes all files as configured in NAMED_CONF_INCLUDE_FILES from
# /etc/sysconfig/named

include "/etc/named.conf.include";
zone "casa.com" in {
    allow-transfer { any; };
    file "master/casa.comXX";
    type master;
};
zone "0.168.192.in-addr.arpa" in {
    allow-transfer { any; };
    file "master/0.168.192.in-addr.arpaXX";
    type master;
};
logging {
    category default { log_syslog; };
    channel log_syslog { syslog; };
};

# You can insert further zone records for your own domains below or create
# single files in /etc/named.d/ and add the file names to
# NAMED_CONF_INCLUDE_FILES.
# See /usr/share/doc/packages/bind/README.SUSE for more details

18 Ответ от andaks (25.01.2011 20:22:46 отредактировано andaks)

  • andaks
  • Пользователь
  • Неактивен
  • Зарегистрирован: 25.02.2010
  • Сообщений: 128
  • Репутация : [ 6 | 0 ]

сделайте так:

dig -x 127.0.0.1

и покажите результат

19 Ответ от petia

  • petia
  • Новичок
  • Неактивен
  • Зарегистрирован: 25.01.2011
  • Сообщений: 22
  • Репутация : [ 0 | 0 ]

dig -x 127.0.0.1

; <<>> DiG 9.7.1-P2 <<>> -x 127.0.0.1
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 41455
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 1, ADDITIONAL: 2

;; QUESTION SECTION:
;1.0.0.127.in-addr.arpa.        IN    PTR

;; ANSWER SECTION:
1.0.0.127.in-addr.arpa.    604800    IN    PTR    localhost.

;; AUTHORITY SECTION:
0.0.127.in-addr.arpa.    604800    IN    NS    localhost.

;; ADDITIONAL SECTION:
localhost.        604800    IN    A    127.0.0.1
localhost.        604800    IN    AAAA    ::1

;; Query time: 0 msec
;; SERVER: 127.0.0.1#53(127.0.0.1)
;; WHEN: Tue Jan 25 18:24:22 2011
;; MSG SIZE  rcvd: 121

20 Ответ от andaks

  • andaks
  • Пользователь
  • Неактивен
  • Зарегистрирован: 25.02.2010
  • Сообщений: 128
  • Репутация : [ 6 | 0 ]

Jan 25 17:22:40 piter named[15647]: zone 0.168.192.in-addr.arpa/IN: NS '200.0.168.192.in-addr.arpa' has no address records (A or AAAA)
Jan 25 17:22:40 piter named[15647]: zone 0.168.192.in-addr.arpa/IN: not loaded due to errors.

проверяйте синтаксис написания зоны.

21 Ответ от andaks

  • andaks
  • Пользователь
  • Неактивен
  • Зарегистрирован: 25.02.2010
  • Сообщений: 128
  • Репутация : [ 6 | 0 ]

приведите его к виду файла "127.0.0.zone"

22 Ответ от petia

  • petia
  • Новичок
  • Неактивен
  • Зарегистрирован: 25.01.2011
  • Сообщений: 22
  • Репутация : [ 0 | 0 ]

dig -x 192.168.0.200

; <<>> DiG 9.7.1-P2 <<>> -x 192.168.0.200
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 5796
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;200.0.168.192.in-addr.arpa.    IN    PTR

;; ANSWER SECTION:
200.0.168.192.in-addr.arpa. 172800 IN    PTR    piter.casa.com.

;; AUTHORITY SECTION:
0.168.192.in-addr.arpa.    172800    IN    NS    200.168.192.in-addr.arpa.

;; Query time: 0 msec
;; SERVER: 127.0.0.1#53(127.0.0.1)
;; WHEN: Tue Jan 25 18:51:22 2011
;; MSG SIZE  rcvd: 90

спасибо большое вам но по моему поличилось может я ошибаюсь

23 Ответ от andaks

  • andaks
  • Пользователь
  • Неактивен
  • Зарегистрирован: 25.02.2010
  • Сообщений: 128
  • Репутация : [ 6 | 0 ]

Вы не ошибаетесь, всё работает =) Не забудьте про зеленый +

+ petia

24 Ответ от drBatty

  • drBatty
  • drBatty
  • Пользователь
  • Неактивен
  • Откуда: Петербург
  • Зарегистрирован: 20.02.2010
  • Сообщений: 17,053
  • Репутация : [ 451 | 73 ]

если-бы вы ещё [тегами] пользовались-бы, так вообще хорошо было-бы...

Карусель разнесло по цепочке за час
Всех известий — конец
Да, весна началась!
(всё к лицу подлецу, как родному отцу, не рассказывай, батя, и так всё пройдёт)
+ petia