After installing updates - Server fails

8 posts / 0 new
Last post
#1 Sat, 07/26/2008 - 14:23
office@colesnicov.at

After installing updates - Server fails

Today I installed the recent updates my server fails afer 5-10 hours:

My log shows: Jul 26 21:02:13 server1 named[1922]: unexpected RCODE (SERVFAIL) resolving 'ns3.chello.at/AAAA/IN': 62.116.129.129#53 Jul 26 21:02:14 server1 named[1922]: unexpected RCODE (SERVFAIL) resolving '74.246.163.213.in-addr.arpa/PTR/IN': 62.116.129.129#53 Jul 26 21:02:14 server1 named[1922]: unexpected RCODE (SERVFAIL) resolving '166.33.127.85.in-addr.arpa/PTR/IN': 62.116.129.129#53 Jul 26 21:02:14 server1 named[1922]: unexpected RCODE (SERVFAIL) resolving '8.191.108.80.in-addr.arpa/PTR/IN': 62.116.129.129#53 Jul 26 21:02:14 server1 named[1922]: unexpected RCODE (SERVFAIL) resolving '150.216.112.91.in-addr.arpa/PTR/IN': 62.116.129.129#53 Jul 26 21:02:14 server1 named[1922]: unexpected RCODE (SERVFAIL) resolving 'cna-gdwi-2.cna.at/AAAA/IN': 62.116.163.100#53 Jul 26 21:02:14 server1 named[1922]: unexpected RCODE (SERVFAIL) resolving 'cna-gdwi-2.cna.at/A/IN': 62.116.163.100#53 Jul 26 21:02:14 server1 named[1922]: unexpected RCODE (SERVFAIL) resolving '166.33.127.85.in-addr.arpa/PTR/IN': 62.116.163.100#53 Jul 26 21:02:14 server1 named[1922]: unexpected RCODE (SERVFAIL) resolving 'ns2.home.nl/A/IN': 62.116.163.100#53 Jul 26 21:02:14 server1 named[1922]: unexpected RCODE (SERVFAIL) resolving 'ns1.home.nl/AAAA/IN': 62.116.163.100#53 Jul 26 21:02:14 server1 named[1922]: unexpected RCODE (SERVFAIL) resolving 'ns1.home.nl/A/IN': 62.116.163.100#53 Jul 26 21:02:14 server1 named[1922]: unexpected RCODE (SERVFAIL) resolving '8.191.108.80.in-addr.arpa/PTR/IN': 62.116.163.100#53 Jul 26 21:02:14 server1 named[1922]: unexpected RCODE (SERVFAIL) resolving 'ns2.home.nl/AAAA/IN': 62.116.163.100#53 Jul 26 21:02:15 server1 named[1922]: unexpected RCODE (SERVFAIL) resolving 'ns3.home.nl/AAAA/IN': 62.116.163.100#53 Jul 26 21:02:15 server1 named[1922]: unexpected RCODE (SERVFAIL) resolving 'ns3.home.nl/A/IN': 62.116.163.100#53 Jul 26 21:02:15 server1 named[1922]: unexpected RCODE (SERVFAIL) resolving '70.250.170.193.in-addr.arpa/PTR/IN': 62.116.163.100#53 Jul 26 21:02:15 server1 named[1922]: unexpected RCODE (SERVFAIL) resolving 'ns4.home.nl/AAAA/IN': 62.116.163.100#53 Jul 26 21:02:15 server1 named[1922]: unexpected RCODE (SERVFAIL) resolving 'ns4.home.nl/A/IN': 62.116.163.100#53 Jul 26 21:02:15 server1 named[1922]: unexpected RCODE (SERVFAIL) resolving '220.109.55.65.in-addr.arpa/PTR/IN': 62.116.163.100#53 Jul 26 21:02:15 server1 named[1922]: unexpected RCODE (SERVFAIL) resolving '21.238.85.209.in-addr.arpa/PTR/IN': 62.116.163.100#53 Jul 26 21:02:15 server1 named[1922]: unexpected RCODE (SERVFAIL) resolving '22.238.85.209.in-addr.arpa/PTR/IN': 62.116.163.100#53 Jul 26 21:02:15 server1 named[1922]: unexpected RCODE (SERVFAIL) resolving '67.52.110.77.in-addr.arpa/PTR/IN': 62.116.163.100#53 Jul 26 21:02:15 server1 named[1922]: unexpected RCODE (SERVFAIL) resolving 'cna-gdwi-1.cna.at/A/IN': 62.116.163.100#53 Jul 26 21:02:15 server1 named[1922]: unexpected RCODE (SERVFAIL) resolving 'cna-gdwi-1.cna.at/AAAA/IN': 62.116.163.100#53 Jul 26 21:02:15 server1 named[1922]: unexpected RCODE (SERVFAIL) resolving 'ns3.chello.at/A/IN': 62.116.163.100#53 Jul 26 21:02:16 server1 named[1922]: unexpected RCODE (SERVFAIL) resolving 'ns3.chello.at/AAAA/IN': 62.116.163.100#53 Jul 26 21:02:16 server1 named[1922]: unexpected RCODE (SERVFAIL) resolving '77.213.120.217.in-addr.arpa/PTR/IN': 62.116.163.100#53 Jul 26 21:02:16 server1 named[1922]: unexpected RCODE (SERVFAIL) resolving '8.191.108.80.in-addr.arpa/PTR/IN': 193.0.0.193#53 Jul 26 21:02:16 server1 named[1922]: unexpected RCODE (SERVFAIL) resolving '158.234.33.86.in-addr.arpa/PTR/IN': 62.116.163.100#53 Jul 26 21:02:16 server1 named[1922]: unexpected RCODE (SERVFAIL) resolving 'ns2.chello.at/A/IN': 62.116.163.100#53 Jul 26 21:02:16 server1 named[1922]: unexpected RCODE (SERVFAIL) resolving 'ns2.chello.at/AAAA/IN': 62.116.163.100#53 Jul 26 21:02:16 server1 named[1922]: unexpected RCODE (SERVFAIL) resolving '220.96.175.147.in-addr.arpa/PTR/IN': 62.116.163.100#53 Jul 26 21:02:16 server1 named[1922]: unexpected RCODE (SERVFAIL) resolving 'cna-gdwi-0.cna.at/A/IN': 62.116.163.100#53 Jul 26 21:02:16 server1 named[1922]: unexpected RCODE (SERVFAIL) resolving 'cna-gdwi-0.cna.at/AAAA/IN': 62.116.163.100#53 Jul 26 21:02:16 server1 named[1922]: unexpected RCODE (SERVFAIL) resolving '6.137.117.88.in-addr.arpa/PTR/IN': 62.116.163.100#53 Jul 26 21:02:17 server1 named[1922]: unexpected RCODE (SERVFAIL) resolving '2.154.99.62.in-addr.arpa/PTR/IN': 62.116.163.100#53 Jul 26 21:02:17 server1 named[1922]: unexpected RCODE (SERVFAIL) resolving '88.108.146.90.in-addr.arpa/PTR/IN': 62.116.163.100#53 Jul 26 21:02:17 server1 named[1922]: unexpected RCODE (SERVFAIL) resolving '77.213.120.217.in-addr.arpa/PTR/IN': 62.116.129.129#53 Jul 26 21:02:17 server1 named[1922]: unexpected RCODE (SERVFAIL) resolving '70.250.170.193.in-addr.arpa/PTR/IN': 62.116.129.129#53 Jul 26 21:02:17 server1 named[1922]: unexpected RCODE (SERVFAIL) resolving 'ns3.home.nl/AAAA/IN': 62.116.129.129#53 Jul 26 21:02:17 server1 named[1922]: unexpected RCODE (SERVFAIL) resolving 'ns3.home.nl/A/IN': 62.116.129.129#53 Jul 26 21:02:17 server1 named[1922]: unexpected RCODE (SERVFAIL) resolving 'ns4.home.nl/AAAA/IN': 62.116.129.129#53 Jul 26 21:02:18 server1 named[1922]: unexpected RCODE (SERVFAIL) resolving 'ns4.home.nl/A/IN': 62.116.129.129#53 Jul 26 21:02:18 server1 named[1922]: unexpected RCODE (SERVFAIL) resolving '71.207.14.91.in-addr.arpa/PTR/IN': 62.116.129.129#53 Jul 26 21:02:18 server1 named[1922]: unexpected RCODE (SERVFAIL) resolving '158.234.33.86.in-addr.arpa/PTR/IN': 62.116.129.129#53 Jul 26 21:02:18 server1 named[1922]: unexpected RCODE (SERVFAIL) resolving 'ns2.home.nl/A/IN': 62.116.129.129#53 Jul 26 21:02:18 server1 named[1922]: unexpected RCODE (SERVFAIL) resolving '220.96.175.147.in-addr.arpa/PTR/IN': 62.116.129.129#53 Jul 26 21:02:18 server1 named[1922]: unexpected RCODE (SERVFAIL) resolving '6.137.117.88.in-addr.arpa/PTR/IN': 62.116.129.129#53 Jul 26 21:02:18 server1 named[1922]: unexpected RCODE (SERVFAIL) resolving '35.11.186.91.in-addr.arpa/PTR/IN': 62.116.129.129#53 Jul 26 21:02:18 server1 named[1922]: unexpected RCODE (SERVFAIL) resolving 'rdns1.vaserv.com/A/IN': 62.116.129.129#53 Jul 26 21:02:18 server1 named[1922]: unexpected RCODE (SERVFAIL) resolving 'rdns1.vaserv.com/AAAA/IN': 62.116.129.129#53 Jul 26 21:02:18 server1 named[1922]: unexpected RCODE (SERVFAIL) resolving 'ns2.riksnet.se/A/IN': 62.116.129.129#53 Jul 26 21:02:18 server1 named[1922]: unexpected RCODE (SERVFAIL) resolving 'ns2.riksnet.se/AAAA/IN': 62.116.129.129#53 Jul 26 21:02:18 server1 named[1922]: unexpected RCODE (SERVFAIL) resolving '2.154.99.62.in-addr.arpa/PTR/IN': 62.116.129.129#53 Jul 26 21:02:18 server1 named[1922]: unexpected RCODE (SERVFAIL) resolving 'ns1.riksnet.se/A/IN': 62.116.129.129#53 Jul 26 21:02:19 server1 named[1922]: unexpected RCODE (SERVFAIL) resolving 'ns1.riksnet.se/AAAA/IN': 62.116.129.129#53 Jul 26 21:02:19 server1 named[1922]: unexpected RCODE (SERVFAIL) resolving '67.52.110.77.in-addr.arpa/PTR/IN': 62.116.129.129#53 Jul 26 21:02:19 server1 named[1922]: unexpected RCODE (SERVFAIL) resolving 'ns1.home.nl/AAAA/IN': 62.116.129.129#53 Jul 26 21:02:19 server1 named[1922]: unexpected RCODE (SERVFAIL) resolving 'ns1.home.nl/A/IN': 62.116.129.129#53 Jul 26 21:02:19 server1 named[1922]: unexpected RCODE (SERVFAIL) resolving '88.108.146.90.in-addr.arpa/PTR/IN': 62.116.129.129#53 Jul 26 21:02:19 server1 named[1922]: unexpected RCODE (SERVFAIL) resolving 'rdns2.vaserv.com/A/IN': 62.116.129.129#53 Jul 26 21:02:19 server1 named[1922]: unexpected RCODE (SERVFAIL) resolving 'rdns2.vaserv.com/AAAA/IN': 62.116.129.129#53 Jul 26 21:02:19 server1 named[1922]: unexpected RCODE (SERVFAIL) resolving '100.81.150.79.in-addr.arpa/PTR/IN': 62.116.129.129#53 Jul 26 21:02:19 server1 named[1922]: unexpected RCODE (SERVFAIL) resolving '122.159.116.88.in-addr.arpa/PTR/IN': 62.116.129.129#53 Jul 26 21:02:19 server1 named[1922]: unexpected RCODE (SERVFAIL) resolving '71.207.14.91.in-addr.arpa/PTR/IN': 62.116.163.100#53 Jul 26 21:02:19 server1 named[1922]: unexpected RCODE (SERVFAIL) resolving 'rdns1.vaserv.com/A/IN': 62.116.163.100#53 Jul 26 21:02:19 server1 named[1922]: unexpected RCODE (SERVFAIL) resolving 'rdns1.vaserv.com/AAAA/IN': 62.116.163.100#53 Jul 26 21:02:19 server1 named[1922]: unexpected RCODE (SERVFAIL) resolving 'ns2.riksnet.se/A/IN': 62.116.163.100#53 Jul 26 21:02:19 server1 named[1922]: unexpected RCODE (SERVFAIL) resolving '143.250.189.81.in-addr.arpa/PTR/IN': 62.116.129.129#53 Jul 26 21:02:20 server1 named[1922]: unexpected RCODE (SERVFAIL) resolving 'ns2.riksnet.se/AAAA/IN': 62.116.163.100#53 Jul 26 21:02:20 server1 named[1922]: unexpected RCODE (SERVFAIL) resolving '35.11.186.91.in-addr.arpa/PTR/IN': 62.116.163.100#53 Jul 26 21:02:20 server1 named[1922]: unexpected RCODE (SERVFAIL) resolving 'ns1.riksnet.se/A/IN': 62.116.163.100#53 Jul 26 21:02:20 server1 named[1922]: unexpected RCODE (SERVFAIL) resolving 'ns1.riksnet.se/AAAA/IN': 62.116.163.100#53 Jul 26 21:02:20 server1 named[1922]: unexpected RCODE (SERVFAIL) resolving 'rdns2.vaserv.com/A/IN': 62.116.163.100#53 Jul 26 21:02:21 server1 named[1922]: unexpected RCODE (SERVFAIL) resolving 'rdns2.vaserv.com/AAAA/IN': 62.116.163.100#53 Jul 26 21:02:21 server1 named[1922]: unexpected RCODE (SERVFAIL) resolving '100.81.150.79.in-addr.arpa/PTR/IN': 62.116.163.100#53 Jul 26 21:02:21 server1 named[1922]: unexpected RCODE (SERVFAIL) resolving '178.125.218.62.in-addr.arpa/PTR/IN': 62.116.163.100#53 Jul 26 21:02:21 server1 named[1922]: unexpected RCODE (SERVFAIL) resolving '20.113.153.194.in-addr.arpa/PTR/IN': 62.116.163.100#53 Jul 26 21:02:21 server1 named[1922]: unexpected RCODE (SERVFAIL) resolving 'wexio.dns.swip.net/AAAA/IN': 62.116.163.100#53 Jul 26 21:02:21 server1 named[1922]: unexpected RCODE (SERVFAIL) resolving 'wexio.dns.swip.net/A/IN': 62.116.163.100#53 Jul 26 21:02:21 server1 named[1922]: unexpected RCODE (SERVFAIL) resolving 'malmoe.dns.swip.net/AAAA/IN': 62.116.163.100#53

and so on, and so on.

What is the reason of this error? my virtual cache is filling up! from 0-94 MB in 10 minutes.

Sat, 07/26/2008 - 15:58
sgrayban

looks like bind is messed up -- restart it and make sure /etc/resolv.conf has "nameserver 127.0.0.1" in it.

I tested one of the domains listed and it resolved for me.

$ host ns1.riksnet.se
ns1.riksnet.se has address 85.11.0.250

Sat, 07/26/2008 - 19:02 (Reply to #2)
ronald
ronald's picture

i think your server does not allow itself to be used as a tool for anyone to query domains, which is a good thing.
I have these entries as well and got them after I allowed recursive queries only to its own IP's (so local clients can still do a whois)

if you set "recursive no" these messages will probably go away.
I have not tested this myself though, as I assume my settings are correct.

Sun, 06/07/2009 - 07:27 (Reply to #3)
sgrayban

You can ignore the "lame server" stuff -- in fact you should add

[code:1]category lame-servers { null; };[/code:1]

to your logging.

As for the <i>FORMERR</i> error google has tons of returns for that.

Sun, 06/07/2009 - 07:27 (Reply to #4)
sgrayban

You can ignore the &quot;lame server&quot; stuff -- in fact you should add

[code:1]category lame-servers { null; };[/code:1]

to your logging.

As for the <i>FORMERR</i> error google has tons of returns for that.

Sun, 06/07/2009 - 07:27 (Reply to #5)
ronald
ronald's picture

in named.conf add:

allow-recursion { localhost; };

It will then allow only your own server to do recursive queries.

Mon, 07/28/2008 - 01:51
office@colesnicov.at

Hy.

/etc/resolv.conf has &quot;nameserver 127.0.0.1&quot; in it. I think, there was an error from my firewall. But there are still messages in te log:

[code:1]Jul 28 12:01:25 server1 named[1832]: lame server resolving '161.189.231.66.in-addr.arpa' (in '189.231.66.in-addr.arpa'?): 66.231.188.229#53
Jul 28 12:01:25 server1 named[1832]: lame server resolving '161.189.231.66.in-addr.arpa' (in '189.231.66.in-addr.arpa'?): 66.231.188.181#53
Jul 28 12:14:54 server1 named[1832]: FORMERR resolving 'free4life.us/MX/IN': 204.13.161.15#53
Jul 28 12:14:54 server1 named[1832]: FORMERR resolving 'free4life.us/MX/IN': 204.13.160.15#53
Jul 28 12:14:54 server1 named[1832]: FORMERR resolving 'NS1.DSREDIRECTION.COM/AAAA/IN': 204.13.161.15#53
Jul 28 12:14:54 server1 named[1832]: FORMERR resolving 'NS2.DSREDIRECTION.COM/AAAA/IN': 204.13.161.15#53
Jul 28 12:14:54 server1 named[1832]: FORMERR resolving 'NS1.DSREDIRECTION.COM/AAAA/IN': 204.13.160.15#53
Jul 28 12:14:54 server1 named[1832]: FORMERR resolving 'NS2.DSREDIRECTION.COM/AAAA/IN': 204.13.160.15#53
Jul 28 12:14:55 server1 named[1832]: FORMERR resolving 'ns2.DSREDIRECTION.COM/AAAA/IN': 204.13.161.15#53
Jul 28 12:14:55 server1 named[1832]: FORMERR resolving 'NS1.DSREDIRECTION.COM/AAAA/IN': 204.13.161.15#53
Jul 28 12:14:55 server1 named[1832]: FORMERR resolving 'ns2.DSREDIRECTION.COM/AAAA/IN': 204.13.160.15#53
Jul 28 12:14:55 server1 named[1832]: FORMERR resolving 'NS1.DSREDIRECTION.COM/AAAA/IN': 204.13.160.15#53
Jul 28 12:37:04 server1 named[1832]: lame server resolving '126-241-124-91.pool.ukrtel.net' (in 'ukrtel.net'?): 198.6.1.82#53
Jul 28 12:43:34 server1 named[1832]: unexpected RCODE (SERVFAIL) resolving 'dnsa01m-jca4.net.orange.es/A/IN': 62.37.237.140#53
Jul 28 12:43:34 server1 named[1832]: unexpected RCODE (SERVFAIL) resolving 'dnsa01m-jca4.net.orange.es/AAAA/IN': 62.37.237.140#53[/code:1]

what does FORMERR and lame server resolving mean?

Mon, 07/28/2008 - 02:08
sgrayban

BTW you only need to paste a FEW lines not the whole bloody log.