Страница 1 из 1

Проблема с BIND'ом, DNS сервером.

Добавлено: 2014-04-16 21:47:38
ppvv
Помогите студенту!
Кэширующий BIND в локальной сети начал массово ругаться в лог вот такими сообщениями:
Иногда ето прикрощается, на пол дня или больше, потом опять.

Код: Выделить всё

Apr 16 21:33:25 ns1 named[8736]: DNS format error from 218.66.171.14#53 resolving odcvwrclgnmxqncx.www.siluke.com/A for client xx.xx.xx.115#30147: reply has no answer
Apr 16 21:33:25 ns1 named[8736]: DNS format error from 61.131.59.79#53 resolving vhmzedcyjlb.www.siluke.com/A for client xx.xx.xx.115#51409: reply has no answer
Apr 16 21:33:25 ns1 named[8736]: DNS format error from 218.66.171.14#53 resolving obpda.www.siluke.com/A for client xx.xx.xx.115#4092: reply has no answer
Apr 16 21:33:25 ns1 named[8736]: DNS format error from 61.131.59.79#53 resolving dqbtrrfckrlufqn.www.siluke.com/A for client xx.xx.xx.115#38680: reply has no answer
Apr 16 21:33:25 ns1 named[8736]: DNS format error from 61.131.59.79#53 resolving rtjutemcoexngfr.www.siluke.com/A for client xx.xx.xx.115#39549: reply has no answer
Apr 16 21:33:25 ns1 named[8736]: DNS format error from 61.131.59.78#53 resolving kocjwvildyi.www.siluke.com/A for client xx.xx.xx.115#40075: reply has no answer
Apr 16 21:33:25 ns1 named[8736]: DNS format error from 61.131.59.78#53 resolving nocdefthijxlz.www.siluke.com/A for client xx.xx.xx.115#53953: reply has no answer
Apr 16 21:33:25 ns1 named[8736]: DNS format error from 61.131.59.79#53 resolving aup.www.siluke.com/A for client xx.xx.xx.115#40589: reply has no answer
Apr 16 21:33:25 ns1 named[8736]: DNS format error from 61.131.59.79#53 resolving hogstgghmkhsiuk.www.siluke.com/A for client xx.xx.xx.115#48869: reply has no answer
Apr 16 21:33:25 ns1 named[8736]: DNS format error from 218.66.171.15#53 resolving adjge.www.siluke.com/A for client xx.xx.xx.115#34463: reply has no answer
xx.xx.xx.хх --- белые адреса Microtic на беспроводных роздачах (около 30 клиентов), также белые адреса ppoe клиентов.
Как ето исправить?

Re: Проблема с BIND'ом, DNS сервером.

Добавлено: 2014-04-16 21:58:55
FenX
named.conf

Код: Выделить всё

server ::/0 { edns no; };
server 0.0.0.0/0 { edns no; };
в кратце, DSL роутеры сыпят на днс большие UDP пакеты.

источник:
http://blog.kxr.me/2011/12/formerr-in-bind-9.html

Re: Проблема с BIND'ом, DNS сервером.

Добавлено: 2014-04-17 12:53:32
ppvv
Проблема в том на тех IP нет DSL модемов, там всюду беспроводные раздачи, раздает MikroTik. У клиентов тип подключения ppoe.

Re: Проблема с BIND'ом, DNS сервером.

Добавлено: 2014-04-17 20:32:51
FenX
хмм... микротики как-то мимо глаз пролетели, обратил внимание на пппое, отсюда и про дсл`ы разговор.
все же попробуй решение, предложенное выше.

Re: Проблема с BIND'ом, DNS сервером.

Добавлено: 2014-04-17 21:31:54
ppvv
Попробовал вроде норм. Но также єсть решения и тут: http://trafficpanel.scand.com/library/faq?lang=ru

Re: Проблема с BIND'ом, DNS сервером.

Добавлено: 2014-04-17 22:54:15
FenX
ну собственно там же и описана причина, почему возникает

Re: Проблема с BIND'ом, DNS сервером.

Добавлено: 2014-04-18 9:03:02
ppvv
Лог дальше, не могу найти решения. Помогите а то уже достало разгребать старые ошибки.

Код: Выделить всё

Apr 18 03:16:06 ns1 named[31109]: clients-per-query decreased to 24
Apr 18 03:19:08 ns1 named[31109]: socket: file descriptor exceeds limit (4096/4096)
Apr 18 03:19:09 ns1 last message repeated 92 times
Apr 18 03:36:06 ns1 named[31109]: clients-per-query decreased to 23
Apr 18 03:39:19 ns1 named[31109]: socket: file descriptor exceeds limit (4096/4096)
Apr 18 03:39:20 ns1 last message repeated 302 times
Apr 18 03:56:06 ns1 named[31109]: clients-per-query decreased to 22
Apr 18 04:09:09 ns1 named[31109]: socket: file descriptor exceeds limit (4096/4096)
Apr 18 04:09:09 ns1 last message repeated 42 times
Apr 18 04:16:06 ns1 named[31109]: clients-per-query decreased to 21
Apr 18 04:16:53 ns1 named[31109]: clients-per-query increased to 26
Apr 18 04:24:24 ns1 named[31109]: socket: file descriptor exceeds limit (4096/4096)
Apr 18 04:24:25 ns1 last message repeated 200 times
Apr 18 04:36:53 ns1 named[31109]: clients-per-query decreased to 25
Apr 18 04:56:53 ns1 named[31109]: clients-per-query decreased to 24
Apr 18 05:16:53 ns1 named[31109]: clients-per-query decreased to 23
Apr 18 05:36:53 ns1 named[31109]: clients-per-query decreased to 22
Apr 18 05:56:53 ns1 named[31109]: clients-per-query decreased to 21
Apr 18 06:16:53 ns1 named[31109]: clients-per-query decreased to 20
Apr 18 06:36:53 ns1 named[31109]: clients-per-query decreased to 19
Apr 18 06:56:53 ns1 named[31109]: clients-per-query decreased to 18
Apr 18 07:16:53 ns1 named[31109]: clients-per-query decreased to 17
Apr 18 07:36:53 ns1 named[31109]: clients-per-query decreased to 16
Apr 18 07:56:53 ns1 named[31109]: clients-per-query decreased to 15
Apr 18 08:16:53 ns1 named[31109]: clients-per-query decreased to 14
Apr 18 08:29:27 ns1 named[31109]: DNS format error from 117.25.132.187#53 resolving ns2.51dns.com/AAAA: reply has no answer
Apr 18 08:29:28 ns1 named[31109]: DNS format error from 121.14.154.250#53 resolving ns2.51dns.com/AAAA: reply has no answer
Apr 18 08:29:28 ns1 named[31109]: DNS format error from 61.131.59.91#53 resolving ns2.51dns.com/AAAA: reply has no answer
Apr 18 08:29:29 ns1 named[31109]: DNS format error from 218.66.171.26#53 resolving ns2.51dns.com/AAAA: reply has no answer
Apr 18 08:29:29 ns1 named[31109]: DNS format error from 113.105.158.59#53 resolving ns2.51dns.com/AAAA: reply has no answer
Apr 18 08:29:29 ns1 named[31109]: DNS format error from 113.105.158.58#53 resolving ns2.51dns.com/AAAA: reply has no answer
Apr 18 08:29:30 ns1 named[31109]: DNS format error from 117.25.132.187#53 resolving ns1.51dns.com/AAAA: reply has no answer
Apr 18 08:29:30 ns1 named[31109]: DNS format error from 218.66.171.27#53 resolving ns2.51dns.com/AAAA: reply has no answer
Apr 18 08:29:30 ns1 named[31109]: DNS format error from 121.14.154.250#53 resolving ns1.51dns.com/AAAA: reply has no answer