I just installed ISC 9.7.0 on one of our x86 SUN Solaris 10 machines.
I did a fresh local compiled install with all default settings.
It looks that DNS is working fine for customers (anyway the time is too
short to conclude that), but my syslog suddenly got populated with tones of
daemon.notice messages about all kind of "DNS format errors" from different
other servers.
Is it something wrong with my DNS server?
Were no notices like these before when I was running BIND 9.6.1-P1.
I attached a short capture from syslog.
Any advice would be appreciated.
Thank you,
Julian
Feb 19 14:39:46 my.domain.net named[20234]: [ID 873579 daemon.notice] DNS
format error from 209.235.30.142#53 resolving stats.surfaid.ihost.com/AAAA for
client 216.108.16.225#2025: invalid response
Feb 19 14:39:46 my.domain.net last message repeated 1 time
Feb 19 14:39:46 my.domain.net named[20234]: [ID 873579 daemon.notice] DNS
format error from 204.77.28.20#53 resolving stats.surfaid.ihost.com/AAAA for
client 216.108.16.225#2025: invalid response
Feb 19 14:39:46 my.domain.net last message repeated 1 time
Feb 19 14:39:47 my.domain.net named[20234]: [ID 873579 daemon.notice] DNS
format error from 66.179.173.211#53 resolving stats.surfaid.ihost.com/AAAA for
client 216.108.16.225#2025: invalid response
Feb 19 14:39:47 my.domain.net last message repeated 2 times
Feb 19 14:39:47 my.domain.net named[20234]: [ID 873579 daemon.notice] DNS
format error from 204.77.28.20#53 resolving stats.surfaid.ihost.com/AAAA for
client 216.108.16.225#2025: invalid response
Feb 19 14:39:47 my.domain.net named[20234]: [ID 873579 daemon.notice] DNS
format error from 209.235.30.142#53 resolving stats.surfaid.ihost.com/AAAA for
client 216.108.16.225#2025: invalid response
Feb 19 14:39:47 my.domain.net named[20234]: [ID 873579 daemon.notice] DNS
format error from 61.235.117.75#53 resolving ns1.dayeither.com/AAAA for client
216.108.160.30#53683: invalid response
Feb 19 14:39:47 my.domain.net last message repeated 1 time
Feb 19 14:39:48 my.domain.net named[20234]: [ID 873579 daemon.notice] DNS
format error from 222.241.12.32#53 resolving ns5.chordhurry.ru/AAAA for client
216.108.160.30#18164: invalid response
Feb 19 14:39:48 my.domain.net named[20234]: [ID 873579 daemon.notice] DNS
format error from 218.10.19.172#53 resolving ns5.chordhurry.ru/AAAA for client
216.108.160.30#18164: invalid response
Feb 19 14:39:48 my.domain.net named[20234]: [ID 873579 daemon.notice] DNS
format error from 222.241.12.32#53 resolving ns5.chordhurry.ru/AAAA for client
216.108.160.30#48687: invalid response
Feb 19 14:39:48 my.domain.net named[20234]: [ID 873579 daemon.notice] DNS
format error from 61.235.117.75#53 resolving ns1.dayeither.com/AAAA for client
216.108.160.30#31770: invalid response
Feb 19 14:39:48 my.domain.net named[20234]: [ID 873579 daemon.notice] DNS
format error from 218.10.19.172#53 resolving ns5.chordhurry.ru/AAAA for client
216.108.160.30#48687: invalid response
Feb 19 14:39:51 my.domain.net named[20234]: [ID 873579 daemon.notice] DNS
format error from 212.217.1.12#53 resolving
adsl196-171-180-217-196.adsl196-14.iam.net.ma/A for client
216.108.160.30#11987: sideways referral
Feb 19 14:39:51 my.domain.net named[20234]: [ID 873579 daemon.notice] DNS
format error from 212.217.1.1#53 resolving
adsl196-171-180-217-196.adsl196-14.iam.net.ma/A for client
216.108.160.30#11987: sideways referral
Feb 19 14:39:52 my.domain.net named[20234]: [ID 873579 daemon.notice] DNS
format error from 212.217.0.1#53 resolving
adsl196-171-180-217-196.adsl196-14.iam.net.ma/A for client
216.108.160.30#11987: sideways referral
Feb 19 14:40:08 my.domain.net named[20234]: [ID 873579 daemon.notice] DNS
format error from 209.235.30.142#53 resolving stats.surfaid.ihost.com/AAAA for
client 216.108.16.225#2064: invalid response
Feb 19 14:40:08 my.domain.net last message repeated 1 time
Feb 19 14:40:08 my.domain.net named[20234]: [ID 873579 daemon.notice] DNS
format error from 204.77.28.20#53 resolving stats.surfaid.ihost.com/AAAA for
client 216.108.16.225#2064: invalid response
Feb 19 14:40:08 my.domain.net last message repeated 1 time
Feb 19 14:40:09 my.domain.net named[20234]: [ID 873579 daemon.notice] DNS
format error from 66.179.173.211#53 resolving stats.surfaid.ihost.com/AAAA for
client 216.108.16.225#2064: invalid response
Feb 19 14:40:09 my.domain.net last message repeated 2 times
Feb 19 14:40:09 my.domain.net named[20234]: [ID 873579 daemon.notice] DNS
format error from 204.77.28.20#53 resolving stats.surfaid.ihost.com/AAAA for
client 216.108.16.225#2064: invalid response
Feb 19 14:40:09 my.domain.net named[20234]: [ID 873579 daemon.notice] DNS
format error from 209.235.30.142#53 resolving stats.surfaid.ihost.com/AAAA for
client 216.108.16.225#2064: invalid response
Feb 19 14:40:13 my.domain.net named[20234]: [ID 873579 daemon.notice] DNS
format error from 200.142.130.10#53 resolving 227.136.98.189.in-addr.arpa/PTR
for client 216.108.31.252#29100: sideways referral
Feb 19 14:40:23 my.domain.net named[20234]: [ID 873579 daemon.notice] DNS
format error from 80.252.128.254#53 resolving 94-253-47-250.dynvpn.flex.ru/A
for client 216.108.160.30#30374: invalid response
Feb 19 14:40:37 my.domain.net named[20234]: [ID 873579 daemon.notice] DNS
format error from 222.138.97.36#53 resolving ns6.0v9.ru/AAAA: invalid response
Feb 19 14:40:37 my.domain.net named[20234]: [ID 873579 daemon.notice] DNS
format error from 222.138.97.36#53 resolving ns5.0v9.ru/AAAA: invalid response
Feb 19 14:40:39 my.domain.net named[20234]: [ID 873579 daemon.notice] DNS
format error from 68.179.114.125#53 resolving www.sonystyle.ca/AAAA for client
216.108.160.20#26187: invalid response
Feb 19 14:40:39 my.domain.net named[20234]: [ID 873579 daemon.notice] DNS
format error from 206.47.171.206#53 resolving www.sonystyle.ca/AAAA for client
216.108.160.20#26187: invalid response
Feb 19 14:40:39 my.domain.net named[20234]: [ID 873579 daemon.notice] DNS
format error from 206.47.171.206#53 resolving www.sonystyle.ca/AAAA for client
216.108.160.20#6781: invalid response
Feb 19 14:40:39 my.domain.net named[20234]: [ID 873579 daemon.notice] DNS
format error from 68.179.114.125#53 resolving www.sonystyle.ca/AAAA for client
216.108.160.20#6781: invalid response
Feb 19 14:40:40 my.domain.net named[20234]: [ID 873579 daemon.notice] DNS
format error from 206.47.171.206#53 resolving www.sonystyle.ca/AAAA for client
216.108.160.20#47370: invalid response
Feb 19 14:40:40 my.domain.net named[20234]: [ID 873579 daemon.notice] DNS
format error from 222.138.97.36#53 resolving ns6.0v9.ru/AAAA: invalid response
Feb 19 14:40:40 my.domain.net named[20234]: [ID 873579 daemon.notice] DNS
format error from 68.179.114.125#53 resolving www.sonystyle.ca/AAAA for client
216.108.160.20#47370: invalid response
Feb 19 14:40:40 my.domain.net named[20234]: [ID 873579 daemon.notice] DNS
format error from 68.179.114.125#53 resolving www.sonystyle.ca/AAAA for client
216.108.160.20#17568: invalid response
Feb 19 14:40:40 my.domain.net named[20234]: [ID 873579 daemon.notice] DNS
format error from 222.138.97.36#53 resolving ns5.0v9.ru/AAAA: invalid response
Feb 19 14:40:40 my.domain.net named[20234]: [ID 873579 daemon.notice] DNS
format error from 206.47.171.206#53 resolving www.sonystyle.ca/AAAA for client
216.108.160.20#17568: invalid response
Feb 19 14:40:43 my.domain.net named[20234]: [ID 873579 daemon.notice] DNS
format error from 74.54.83.122#53 resolving lesmars.com/AAAA for client
216.108.1.129#65048: invalid response
Feb 19 14:40:43 my.domain.net named[20234]: [ID 873579 daemon.notice] DNS
format error from 74.54.82.122#53 resolving lesmars.com/AAAA for client
216.108.1.129#65048: invalid response
Feb 19 14:40:44 my.domain.net named[20234]: [ID 873579 daemon.notice] DNS
format error from 74.54.82.122#53 resolving lesmars.com/AAAA for client
216.108.1.129#53218: invalid response
Feb 19 14:40:44 my.domain.net named[20234]: [ID 873579 daemon.notice] DNS
format error from 74.54.83.122#53 resolving lesmars.com/AAAA for client
216.108.1.129#53218: invalid response
Feb 19 14:40:46 my.domain.net named[20234]: [ID 873579 daemon.notice] DNS
format error from 198.151.36.1#53 resolving cendant.com/A for client
216.108.190.1#55921: sideways referral
Feb 19 14:40:47 my.domain.net named[20234]: [ID 873579 daemon.notice] DNS
format error from 222.138.97.36#53 resolving ns1.droolorder.com/AAAA: invalid
response
Feb 19 14:40:47 my.domain.net named[20234]: [ID 873579 daemon.notice] DNS
format error from 222.138.97.36#53 resolving ns2.droolorder.com/AAAA: invalid
response
Feb 19 14:40:49 my.domain.net named[20234]: [ID 873579 daemon.notice] DNS
format error from 206.47.171.206#53 resolving www.sonystyle.ca/AAAA for client
216.108.160.30#20052: invalid response
Feb 19 14:40:49 my.domain.net named[20234]: [ID 873579 daemon.notice] DNS
format error from 68.179.114.125#53 resolving www.sonystyle.ca/AAAA for client
216.108.160.30#20052: invalid response
Feb 19 14:40:49 my.domain.net named[20234]: [ID 873579 daemon.notice] DNS
format error from 68.179.114.125#53 resolving www.sonystyle.ca/AAAA for client
216.108.160.30#34659: invalid response
Feb 19 14:40:49 my.domain.net named[20234]: [ID 873579 daemon.notice] DNS
format error from 206.47.171.206#53 resolving www.sonystyle.ca/AAAA for client
216.108.160.30#34659: invalid response
Feb 19 14:40:50 my.domain.net named[20234]: [ID 873579 daemon.notice] DNS
format error from 206.47.171.206#53 resolving www.sonystyle.ca/AAAA for client
216.108.160.30#47699: invalid response
Feb 19 14:40:50 my.domain.net named[20234]: [ID 873579 daemon.notice] DNS
format error from 68.179.114.125#53 resolving www.sonystyle.ca/AAAA for client
216.108.160.30#47699: invalid response
Feb 19 14:40:50 my.domain.net named[20234]: [ID 873579 daemon.notice] DNS
format error from 206.47.171.206#53 resolving www.sonystyle.ca/AAAA for client
216.108.160.30#35857: invalid response
Feb 19 14:40:50 my.domain.net named[20234]: [ID 873579 daemon.notice] DNS
format error from 68.179.114.125#53 resolving www.sonystyle.ca/AAAA for client
216.108.160.30#35857: invalid response
Feb 19 14:40:57 my.domain.net named[20234]: [ID 873579 daemon.notice] DNS
format error from 222.138.97.36#53 resolving ns2.droolorder.com/AAAA: invalid
response
Feb 19 14:40:57 my.domain.net named[20234]: [ID 873579 daemon.notice] DNS
format error from 222.138.97.36#53 resolving ns1.droolorder.com/AAAA: invalid
response
Feb 19 14:40:57 my.domain.net named[20234]: [ID 873579 daemon.notice] DNS
format error from 222.138.97.36#53 resolving ns4.droolorder.com/AAAA: invalid
response
Feb 19 14:40:57 my.domain.net named[20234]: [ID 873579 daemon.notice] DNS
format error from 222.138.97.36#53 resolving ns3.droolorder.com/AAAA: invalid
response
Feb 19 14:41:00 my.domain.net named[20234]: [ID 873579 daemon.notice] DNS
format error from 174.120.121.51#53 resolving arcelorstainless.com/AAAA for
client 216.108.1.129#64301: invalid response
Feb 19 14:41:01 my.domain.net named[20234]: [ID 873579 daemon.notice] DNS
format error from 174.120.120.51#53 resolving arcelorstainless.com/AAAA for
client 216.108.1.129#64301: invalid response
Feb 19 14:41:01 my.domain.net named[20234]: [ID 873579 daemon.notice] DNS
format error from 174.120.120.51#53 resolving arcelorstainless.com/AAAA for
client 216.108.1.129#49879: invalid response
Feb 19 14:41:01 my.domain.net named[20234]: [ID 873579 daemon.notice] DNS
format error from 174.120.121.51#53 resolving arcelorstainless.com/AAAA for
client 216.108.1.129#49879: invalid response
Feb 19 14:41:02 my.domain.net named[20234]: [ID 873579 daemon.notice] DNS
format error from 209.234.234.42#53 resolving ad.wsod.com/AAAA for client
216.108.160.20#9930: invalid response
Feb 19 14:41:02 my.domain.net named[20234]: [ID 873579 daemon.notice] DNS
format error from 209.234.224.42#53 resolving ad.wsod.com/AAAA for client
216.108.160.20#9930: invalid response
Feb 19 14:41:02 my.domain.net named[20234]: [ID 873579 daemon.notice] DNS
format error from 66.150.28.2#53 resolving ad.wsod.com/AAAA for client
216.108.160.20#9930: invalid response
Feb 19 14:41:02 my.domain.net named[20234]: [ID 873579 daemon.notice] DNS
format error from 209.234.234.42#53 resolving ad.wsod.com/AAAA for client
216.108.160.20#36957: invalid response
Feb 19 14:41:02 my.domain.net named[20234]: [ID 873579 daemon.notice] DNS
format error from 209.234.224.42#53 resolving ad.wsod.com/AAAA for client
216.108.160.20#36957: invalid response
Feb 19 14:41:02 my.domain.net named[20234]: [ID 873579 daemon.notice] DNS
format error from 66.150.28.2#53 resolving ad.wsod.com/AAAA for client
216.108.160.20#36957: invalid response
Feb 19 14:41:04 my.domain.net named[20234]: [ID 873579 daemon.notice] DNS
format error from 66.150.28.2#53 resolving ad.wsod.com/AAAA for client
216.108.160.20#61573: invalid response
Feb 19 14:41:04 my.domain.net named[20234]: [ID 873579 daemon.notice] DNS
format error from 209.234.224.42#53 resolving ad.wsod.com/AAAA for client
216.108.160.20#61573: invalid response
Feb 19 14:41:05 my.domain.net named[20234]: [ID 873579 daemon.notice] DNS
format error from 209.234.234.42#53 resolving ad.wsod.com/AAAA for client
216.108.160.20#61573: invalid response
Feb 19 14:41:05 my.domain.net named[20234]: [ID 873579 daemon.notice] DNS
format error from 209.234.224.42#53 resolving ad.wsod.com/AAAA for client
216.108.160.20#57146: invalid response
Feb 19 14:41:05 my.domain.net named[20234]: [ID 873579 daemon.notice] DNS
format error from 66.64.198.70#53 resolving lifeintherapids.com/A for client
216.108.178.61#61116: sideways referral
Feb 19 14:41:05 my.domain.net named[20234]: [ID 873579 daemon.notice] DNS
format error from 66.150.28.2#53 resolving ad.wsod.com/AAAA for client
216.108.160.20#57146: invalid response
Feb 19 14:41:05 my.domain.net named[20234]: [ID 873579 daemon.notice] DNS
format error from 209.234.234.42#53 resolving ad.wsod.com/AAAA for client
216.108.160.20#57146: invalid response
Feb 19 14:41:06 my.domain.net named[20234]: [ID 873579 daemon.notice] DNS
format error from 66.150.28.2#53 resolving ad.wsod.com/AAAA for client
216.108.160.20#64598: invalid response
Feb 19 14:41:06 my.domain.net named[20234]: [ID 873579 daemon.notice] DNS
format error from 209.234.224.42#53 resolving ad.wsod.com/AAAA for client
216.108.160.20#64598: invalid response
Feb 19 14:41:07 my.domain.net named[20234]: [ID 873579 daemon.notice] DNS
format error from 209.234.234.42#53 resolving ad.wsod.com/AAAA for client
216.108.160.20#64598: invalid response
Feb 19 14:41:07 my.domain.net named[20234]: [ID 873579 daemon.notice] DNS
format error from 209.234.234.42#53 resolving ad.wsod.com/AAAA for client
216.108.160.20#41424: invalid response
Feb 19 14:41:07 my.domain.net named[20234]: [ID 873579 daemon.notice] DNS
format error from 209.234.224.42#53 resolving ad.wsod.com/AAAA for client
216.108.160.20#41424: invalid response
Feb 19 14:41:07 my.domain.net named[20234]: [ID 873579 daemon.notice] DNS
format error from 66.150.28.2#53 resolving ad.wsod.com/AAAA for client
216.108.160.20#41424: invalid response
Feb 19 14:41:08 my.domain.net named[20234]: [ID 873579 daemon.notice] DNS
format error from 209.234.234.42#53 resolving ad.wsod.com/AAAA for client
216.108.160.30#24053: invalid response
Feb 19 14:41:08 my.domain.net named[20234]: [ID 873579 daemon.notice] DNS
format error from 209.234.224.42#53 resolving ad.wsod.com/AAAA for client
216.108.160.30#24053: invalid response
Feb 19 14:41:08 my.domain.net named[20234]: [ID 873579 daemon.notice] DNS
format error from 66.150.28.2#53 resolving ad.wsod.com/AAAA for client
216.108.160.30#24053: invalid response
Feb 19 14:41:08 my.domain.net named[20234]: [ID 873579 daemon.notice] DNS
format error from 209.234.224.42#53 resolving ad.wsod.com/AAAA for client
216.108.160.30#58014: invalid response
Feb 19 14:41:08 my.domain.net named[20234]: [ID 873579 daemon.notice] DNS
format error from 209.234.234.42#53 resolving ad.wsod.com/AAAA for client
216.108.160.30#58014: invalid response
Feb 19 14:41:08 my.domain.net named[20234]: [ID 873579 daemon.notice] DNS
format error from 66.150.28.2#53 resolving ad.wsod.com/AAAA for client
216.108.160.30#58014: invalid response
Feb 19 14:41:09 my.domain.net named[20234]: [ID 873579 daemon.notice] DNS
format error from 66.150.28.2#53 resolving ad.wsod.com/AAAA for client
216.108.160.20#36939: invalid response
Feb 19 14:41:09 my.domain.net named[20234]: [ID 873579 daemon.notice] DNS
format error from 209.234.224.42#53 resolving ad.wsod.com/AAAA for client
216.108.160.20#36939: invalid response
Feb 19 14:41:09 my.domain.net named[20234]: [ID 873579 daemon.notice] DNS
format error from 209.234.234.42#53 resolving ad.wsod.com/AAAA for client
216.108.160.20#36939: invalid response
Feb 19 14:41:09 my.domain.net named[20234]: [ID 873579 daemon.notice] DNS
format error from 66.150.28.2#53 resolving ad.wsod.com/AAAA for client
216.108.160.20#30691: invalid response
Feb 19 14:41:09 my.domain.net named[20234]: [ID 873579 daemon.notice] DNS
format error from 209.234.224.42#53 resolving ad.wsod.com/AAAA for client
216.108.160.20#30691: invalid response
Feb 19 14:41:09 my.domain.net named[20234]: [ID 873579 daemon.notice] DNS
format error from 209.234.234.42#53 resolving ad.wsod.com/AAAA for client
216.108.160.20#30691: invalid response
Feb 19 14:41:10 my.domain.net named[20234]: [ID 873579 daemon.notice] DNS
format error from 209.234.234.42#53 resolving ad.wsod.com/AAAA for client
216.108.160.30#36195: invalid response
Feb 19 14:41:10 my.domain.net named[20234]: [ID 873579 daemon.notice] DNS
format error from 209.234.224.42#53 resolving ad.wsod.com/AAAA for client
216.108.160.30#36195: invalid response
Feb 19 14:41:10 my.domain.net named[20234]: [ID 873579 daemon.notice] DNS
format error from 66.150.28.2#53 resolving ad.wsod.com/AAAA for client
216.108.160.30#36195: invalid response
Feb 19 14:41:11 my.domain.net named[20234]: [ID 873579 daemon.notice] DNS
format error from 209.234.224.42#53 resolving ad.wsod.com/AAAA for client
216.108.160.30#23231: invalid response
Feb 19 14:41:11 my.domain.net named[20234]: [ID 873579 daemon.notice] DNS
format error from 209.234.234.42#53 resolving ad.wsod.com/AAAA for client
216.108.160.30#23231: invalid response
Feb 19 14:41:11 my.domain.net named[20234]: [ID 873579 daemon.notice] DNS
format error from 66.150.28.2#53 resolving ad.wsod.com/AAAA for client
216.108.160.30#23231: invalid response
Feb 19 14:41:12 my.domain.net named[20234]: [ID 873579 daemon.notice] DNS
format error from 209.234.234.42#53 resolving ad.wsod.com/AAAA for client
216.108.160.30#25692: invalid response
Feb 19 14:41:12 my.domain.net named[20234]: [ID 873579 daemon.notice] DNS
format error from 66.150.28.2#53 resolving ad.wsod.com/AAAA for client
216.108.160.30#25692: invalid response
Feb 19 14:41:12 my.domain.net named[20234]: [ID 873579 daemon.notice] DNS
format error from 209.234.224.42#53 resolving ad.wsod.com/AAAA for client
216.108.160.30#25692: invalid response
Feb 19 14:41:13 my.domain.net named[20234]: [ID 873579 daemon.notice] DNS
format error from 209.234.234.42#53 resolving ad.wsod.com/AAAA for client
216.108.160.30#23163: invalid response
Feb 19 14:41:13 my.domain.net named[20234]: [ID 873579 daemon.notice] DNS
format error from 66.150.28.2#53 resolving ad.wsod.com/AAAA for client
216.108.160.30#23163: invalid response
Feb 19 14:41:13 my.domain.net named[20234]: [ID 873579 daemon.notice] DNS
format error from 209.234.224.42#53 resolving ad.wsod.com/AAAA for client
216.108.160.30#23163: invalid response
Feb 19 14:41:13 my.domain.net named[20234]: [ID 873579 daemon.notice] DNS
format error from 66.45.244.194#53 resolving payupnow.com/AAAA for client
216.108.1.129#61741: invalid response
Feb 19 14:41:13 my.domain.net last message repeated 1 time
Feb 19 14:41:13 my.domain.net named[20234]: [ID 873579 daemon.notice] DNS
format error from 66.45.244.194#53 resolving ns1.serverhome.com/AAAA: invalid
response
Feb 19 14:41:13 my.domain.net named[20234]: [ID 873579 daemon.notice] DNS
format error from 66.45.244.194#53 resolving ns2.serverhome.com/AAAA: invalid
response
Feb 19 14:41:13 my.domain.net last message repeated 1 time
Feb 19 14:41:13 my.domain.net named[20234]: [ID 873579 daemon.notice] DNS
format error from 66.45.244.194#53 resolving ns1.serverhome.com/AAAA: invalid
response
Feb 19 14:41:13 my.domain.net named[20234]: [ID 873579 daemon.notice] DNS
format error from 212.217.1.12#53 resolving
adsl-221-223-192-81.adsl2.iam.net.ma/A for client 216.108.160.30#26810:
sideways referral
Feb 19 14:41:13 my.domain.net named[20234]: [ID 873579 daemon.notice] DNS
format error from 66.45.244.194#53 resolving ns1.serverhome.com/AAAA: invalid
response
Feb 19 14:41:14 my.domain.net last message repeated 1 time
Feb 19 14:41:14 my.domain.net named[20234]: [ID 873579 daemon.notice] DNS
format error from 66.45.244.194#53 resolving payupnow.com/AAAA for client
216.108.1.129#58126: invalid response
Feb 19 14:41:14 my.domain.net named[20234]: [ID 873579 daemon.notice] DNS
format error from 212.217.1.1#53 resolving
adsl-221-223-192-81.adsl2.iam.net.ma/A for client 216.108.160.30#26810:
sideways referral
Feb 19 14:41:14 my.domain.net named[20234]: [ID 873579 daemon.notice] DNS
format error from 66.45.244.194#53 resolving ns2.serverhome.com/AAAA: invalid
response
Feb 19 14:41:14 my.domain.net named[20234]: [ID 873579 daemon.notice] DNS
format error from 66.45.244.194#53 resolving payupnow.com/AAAA for client
216.108.1.129#58126: invalid response
Feb 19 14:41:14 my.domain.net named[20234]: [ID 873579 daemon.notice] DNS
format error from 66.45.244.194#53 resolving ns2.serverhome.com/AAAA: invalid
response
Feb 19 14:41:15 my.domain.net named[20234]: [ID 873579 daemon.notice] DNS
format error from 209.234.234.42#53 resolving ad.wsod.com/AAAA for client
216.108.160.30#42508: invalid response
Feb 19 14:41:15 my.domain.net named[20234]: [ID 873579 daemon.notice] DNS
format error from 66.150.28.2#53 resolving ad.wsod.com/AAAA for client
216.108.160.30#42508: invalid response
Feb 19 14:41:15 my.domain.net named[20234]: [ID 873579 daemon.notice] DNS
format error from 209.234.224.42#53 resolving ad.wsod.com/AAAA for client
216.108.160.30#42508: invalid response
Feb 19 14:41:15 my.domain.net named[20234]: [ID 873579 daemon.notice] DNS
format error from 209.234.224.42#53 resolving ad.wsod.com/AAAA for client
216.108.160.30#13925: invalid response
Feb 19 14:41:15 my.domain.net named[20234]: [ID 873579 daemon.notice] DNS
format error from 209.234.234.42#53 resolving ad.wsod.com/AAAA for client
216.108.160.30#13925: invalid response
Feb 19 14:41:15 my.domain.net named[20234]: [ID 873579 daemon.notice] DNS
format error from 66.150.28.2#53 resolving ad.wsod.com/AAAA for client
216.108.160.30#13925: invalid response
Feb 19 14:41:18 my.domain.net named[20234]: [ID 873579 daemon.notice] DNS
format error from 209.235.30.142#53 resolving data.coremetrics.com/AAAA for
client 216.108.160.20#56267: invalid response
Feb 19 14:41:18 my.domain.net named[20234]: [ID 873579 daemon.notice] DNS
format error from 66.179.173.211#53 resolving data.coremetrics.com/AAAA for
client 216.108.160.20#56267: invalid response
Feb 19 14:41:18 my.domain.net named[20234]: [ID 873579 daemon.notice] DNS
format error from 204.77.28.20#53 resolving data.coremetrics.com/AAAA for
client 216.108.160.20#56267: invalid response
Feb 19 14:41:18 my.domain.net last message repeated 1 time
Feb 19 14:41:18 my.domain.net named[20234]: [ID 873579 daemon.notice] DNS
format error from 209.235.30.142#53 resolving data.coremetrics.com/AAAA for
client 216.108.160.20#56267: invalid response
Feb 19 14:41:18 my.domain.net last message repeated 1 time
Feb 19 14:41:18 my.domain.net named[20234]: [ID 873579 daemon.notice] DNS
format error from 66.179.173.211#53 resolving data.coremetrics.com/AAAA for
client 216.108.160.20#56267: invalid response
Feb 19 14:41:19 my.domain.net named[20234]: [ID 873579 daemon.notice] DNS
format error from 204.77.28.20#53 resolving data.coremetrics.com/AAAA for
client 216.108.160.20#56267: invalid response
Feb 19 14:41:19 my.domain.net named[20234]: [ID 873579 daemon.notice] DNS
format error from 66.179.173.211#53 resolving data.coremetrics.com/AAAA for
client 216.108.160.20#56267: invalid response
Feb 19 14:41:19 my.domain.net named[20234]: [ID 873579 daemon.notice] DNS
format error from 66.179.173.211#53 resolving data.coremetrics.com/AAAA for
client 216.108.160.20#33526: invalid response
Feb 19 14:41:19 my.domain.net last message repeated 2 times
Feb 19 14:41:19 my.domain.net named[20234]: [ID 873579 daemon.notice] DNS
format error from 209.235.30.142#53 resolving data.coremetrics.com/AAAA for
client 216.108.160.20#33526: invalid response
Feb 19 14:41:19 my.domain.net last message repeated 1 time
Feb 19 14:41:19 my.domain.net named[20234]: [ID 873579 daemon.notice] DNS
format error from 204.77.28.20#53 resolving data.coremetrics.com/AAAA for
client 216.108.160.20#33526: invalid response
Feb 19 14:41:20 my.domain.net last message repeated 2 times
Feb 19 14:41:20 my.domain.net named[20234]: [ID 873579 daemon.notice] DNS
format error from 209.235.30.142#53 resolving data.coremetrics.com/AAAA for
client 216.108.160.20#33526: invalid response
Feb 19 14:41:21 my.domain.net named[20234]: [ID 873579 daemon.notice] DNS
format error from 212.217.0.12#53 resolving
adsl196-174-122-206-196.adsl196-4.iam.net.ma/A for client 216.108.160.20#3428:
sideways referral
Feb 19 14:41:21 my.domain.net named[20234]: [ID 873579 daemon.notice] DNS
format error from 212.217.1.1#53 resolving
adsl196-174-122-206-196.adsl196-4.iam.net.ma/A for client 216.108.160.20#3428:
sideways referral
Feb 19 14:41:22 my.domain.net named[20234]: [ID 873579 daemon.notice] DNS
format error from 212.217.1.12#53 resolving
adsl196-174-122-206-196.adsl196-4.iam.net.ma/A for client 216.108.160.20#3428:
sideways referral
Feb 19 14:41:25 my.domain.net named[20234]: [ID 873579 daemon.notice] DNS
format error from 209.235.30.142#53 resolving data.coremetrics.com/AAAA for
client 216.108.160.20#13252: invalid response
Feb 19 14:41:25 my.domain.net named[20234]: [ID 873579 daemon.notice] DNS
format error from 204.77.28.20#53 resolving data.coremetrics.com/AAAA for
client 216.108.160.20#13252: invalid response
Feb 19 14:41:25 my.domain.net named[20234]: [ID 873579 daemon.notice] DNS
format error from 66.179.173.211#53 resolving data.coremetrics.com/AAAA for
client 216.108.160.20#13252: invalid response
Feb 19 14:41:25 my.domain.net named[20234]: [ID 873579 daemon.notice] DNS
format error from 204.77.28.20#53 resolving data.coremetrics.com/AAAA for
client 216.108.160.20#13252: invalid response
Feb 19 14:41:25 my.domain.net named[20234]: [ID 873579 daemon.notice] DNS
format error from 66.179.173.211#53 resolving data.coremetrics.com/AAAA for
client 216.108.160.20#13252: invalid response
Feb 19 14:41:25 my.domain.net named[20234]: [ID 873579 daemon.notice] DNS
format error from 209.235.30.142#53 resolving data.coremetrics.com/AAAA for
client 216.108.160.20#13252: invalid response
Feb 19 14:41:26 my.domain.net named[20234]: [ID 873579 daemon.notice] DNS
format error from 66.179.173.211#53 resolving data.coremetrics.com/AAAA for
client 216.108.160.20#13252: invalid response
Feb 19 14:41:26 my.domain.net named[20234]: [ID 873579 daemon.notice] DNS
format error from 209.235.30.142#53 resolving data.coremetrics.com/AAAA for
client 216.108.160.20#13252: invalid response
Feb 19 14:41:26 my.domain.net named[20234]: [ID 873579 daemon.notice] DNS
format error from 204.77.28.20#53 resolving data.coremetrics.com/AAAA for
client 216.108.160.20#13252: invalid response
Feb 19 14:41:26 my.domain.net named[20234]: [ID 873579 daemon.notice] DNS
format error from 204.77.28.20#53 resolving data.coremetrics.com/AAAA for
client 216.108.160.20#14781: invalid response
Feb 19 14:41:26 my.domain.net named[20234]: [ID 873579 daemon.notice] DNS
format error from 66.179.173.211#53 resolving data.coremetrics.com/AAAA for
client 216.108.160.20#14781: invalid response
Feb 19 14:41:26 my.domain.net last message repeated 1 time
Feb 19 14:41:26 my.domain.net named[20234]: [ID 873579 daemon.notice] DNS
format error from 209.235.30.142#53 resolving data.coremetrics.com/AAAA for
client 216.108.160.20#14781: invalid response
Feb 19 14:41:26 my.domain.net named[20234]: [ID 873579 daemon.notice] DNS
format error from 204.77.28.20#53 resolving data.coremetrics.com/AAAA for
client 216.108.160.20#14781: invalid response
Feb 19 14:41:26 my.domain.net last message repeated 1 time
Feb 19 14:41:27 my.domain.net named[20234]: [ID 873579 daemon.notice] DNS
format error from 66.179.173.211#53 resolving data.coremetrics.com/AAAA for
client 216.108.160.20#14781: invalid response
Feb 19 14:41:27 my.domain.net named[20234]: [ID 873579 daemon.notice] DNS
format error from 209.235.30.142#53 resolving data.coremetrics.com/AAAA for
client 216.108.160.20#14781: invalid response
Feb 19 14:41:27 my.domain.net last message repeated 1 time
Feb 19 14:41:50 my.domain.net named[20234]: [ID 873579 daemon.notice] DNS
format error from 200.124.247.199#53 resolving dns02.telmex.ec/AAAA: unrelated
AAAA dns02.telmex.ec in dns02.telmex.ec.telmex.ec authority section
Feb 19 14:41:50 my.domain.net named[20234]: [ID 873579 daemon.notice] DNS
format error from 200.124.224.201#53 resolving dns03.telmex.ec/AAAA: unrelated
AAAA dns03.telmex.ec in dns03.telmex.ec.telmex.ec authority section
Feb 19 14:41:50 my.domain.net named[20234]: [ID 873579 daemon.notice] DNS
format error from 200.124.247.199#53 resolving dns01.telmex.ec/AAAA: unrelated
AAAA dns01.telmex.ec in dns01.telmex.ec.telmex.ec authority section
Feb 19 14:41:50 my.domain.net named[20234]: [ID 873579 daemon.notice] DNS
format error from 200.124.224.201#53 resolving dns04.telmex.ec/AAAA: unrelated
AAAA dns04.telmex.ec in dns04.telmex.ec.telmex.ec authority section
Feb 19 14:41:51 my.domain.net named[20234]: [ID 873579 daemon.notice] DNS
format error from 200.124.247.199#53 resolving dns03.telmex.ec/AAAA: unrelated
AAAA dns03.telmex.ec in dns03.telmex.ec.telmex.ec authority section
Feb 19 14:41:51 my.domain.net named[20234]: [ID 873579 daemon.notice] DNS
format error from 200.124.224.201#53 resolving dns02.telmex.ec/AAAA: unrelated
AAAA dns02.telmex.ec in dns02.telmex.ec.telmex.ec authority section
Feb 19 14:41:51 my.domain.net named[20234]: [ID 873579 daemon.notice] DNS
format error from 200.124.224.201#53 resolving dns01.telmex.ec/AAAA: unrelated
AAAA dns01.telmex.ec in dns01.telmex.ec.telmex.ec authority section
Feb 19 14:41:51 my.domain.net named[20234]: [ID 873579 daemon.notice] DNS
format error from 200.124.247.201#53 resolving dns04.telmex.ec/AAAA: unrelated
AAAA dns04.telmex.ec in dns04.telmex.ec.telmex.ec authority section
Feb 19 14:41:51 my.domain.net named[20234]: [ID 873579 daemon.notice] DNS
format error from 200.124.247.201#53 resolving dns03.telmex.ec/AAAA: unrelated
AAAA dns03.telmex.ec in dns03.telmex.ec.telmex.ec authority section
Feb 19 14:41:51 my.domain.net named[20234]: [ID 873579 daemon.notice] DNS
format error from 200.124.224.199#53 resolving dns02.telmex.ec/AAAA: unrelated
AAAA dns02.telmex.ec in dns02.telmex.ec.telmex.ec authority section
Feb 19 14:41:51 my.domain.net named[20234]: [ID 873579 daemon.notice] DNS
format error from 200.124.224.199#53 resolving dns01.telmex.ec/AAAA: unrelated
AAAA dns01.telmex.ec in dns01.telmex.ec.telmex.ec authority section
Feb 19 14:41:51 my.domain.net named[20234]: [ID 873579 daemon.notice] DNS
format error from 200.124.224.199#53 resolving dns04.telmex.ec/AAAA: unrelated
AAAA dns04.telmex.ec in dns04.telmex.ec.telmex.ec authority section
Feb 19 14:41:51 my.domain.net named[20234]: [ID 873579 daemon.notice] DNS
format error from 200.124.224.199#53 resolving dns03.telmex.ec/AAAA: unrelated
AAAA dns03.telmex.ec in dns03.telmex.ec.telmex.ec authority section
Feb 19 14:41:51 my.domain.net named[20234]: [ID 873579 daemon.notice] DNS
format error from 200.124.247.201#53 resolving dns02.telmex.ec/AAAA: unrelated
AAAA dns02.telmex.ec in dns02.telmex.ec.telmex.ec authority section
Feb 19 14:41:51 my.domain.net named[20234]: [ID 873579 daemon.notice] DNS
format error from 200.124.247.201#53 resolving dns01.telmex.ec/AAAA: unrelated
AAAA dns01.telmex.ec in dns01.telmex.ec.telmex.ec authority section
Feb 19 14:41:51 my.domain.net named[20234]: [ID 873579 daemon.notice] DNS
format error from 200.124.247.199#53 resolving dns04.telmex.ec/AAAA: unrelated
AAAA dns04.telmex.ec in dns04.telmex.ec.telmex.ec authority section
Feb 19 14:41:51 my.domain.net named[20234]: [ID 873579 daemon.notice] DNS
format error from 200.124.224.199#53 resolving dns03.telmex.ec/AAAA: unrelated
AAAA dns03.telmex.ec in dns03.telmex.ec.telmex.ec authority section
Feb 19 14:41:51 my.domain.net named[20234]: [ID 873579 daemon.notice] DNS
format error from 200.124.247.199#53 resolving dns01.telmex.ec/AAAA: unrelated
AAAA dns01.telmex.ec in dns01.telmex.ec.telmex.ec authority section
Feb 19 14:41:52 my.domain.net named[20234]: [ID 873579 daemon.notice] DNS
format error from 200.124.247.199#53 resolving dns02.telmex.ec/AAAA: unrelated
AAAA dns02.telmex.ec in dns02.telmex.ec.telmex.ec authority section
Feb 19 14:41:52 my.domain.net named[20234]: [ID 873579 daemon.notice] DNS
format error from 200.124.247.199#53 resolving dns04.telmex.ec/AAAA: unrelated
AAAA dns04.telmex.ec in dns04.telmex.ec.telmex.ec authority section
Feb 19 14:41:52 my.domain.net named[20234]: [ID 873579 daemon.notice] DNS
format error from 200.124.224.201#53 resolving dns03.telmex.ec/AAAA: unrelated
AAAA dns03.telmex.ec in dns03.telmex.ec.telmex.ec authority section
Feb 19 14:41:52 my.domain.net named[20234]: [ID 873579 daemon.notice] DNS
format error from 200.124.247.201#53 resolving dns01.telmex.ec/AAAA: unrelated
AAAA dns01.telmex.ec in dns01.telmex.ec.telmex.ec authority section
Feb 19 14:41:52 my.domain.net named[20234]: [ID 873579 daemon.notice] DNS
format error from 200.124.224.199#53 resolving dns02.telmex.ec/AAAA: unrelated
AAAA dns02.telmex.ec in dns02.telmex.ec.telmex.ec authority section
Feb 19 14:41:52 my.domain.net named[20234]: [ID 873579 daemon.notice] DNS
format error from 200.124.224.201#53 resolving dns04.telmex.ec/AAAA: unrelated
AAAA dns04.telmex.ec in dns04.telmex.ec.telmex.ec authority section
Feb 19 14:41:52 my.domain.net named[20234]: [ID 873579 daemon.notice] DNS
format error from 200.124.247.201#53 resolving dns03.telmex.ec/AAAA: unrelated
AAAA dns03.telmex.ec in dns03.telmex.ec.telmex.ec authority section
Feb 19 14:41:52 my.domain.net named[20234]: [ID 873579 daemon.notice] DNS
format error from 200.124.224.201#53 resolving dns01.telmex.ec/AAAA: unrelated
AAAA dns01.telmex.ec in dns01.telmex.ec.telmex.ec authority section
Feb 19 14:41:52 my.domain.net named[20234]: [ID 873579 daemon.notice] DNS
format error from 200.124.224.201#53 resolving dns02.telmex.ec/AAAA: unrelated
AAAA dns02.telmex.ec in dns02.telmex.ec.telmex.ec authority section
Feb 19 14:41:52 my.domain.net named[20234]: [ID 873579 daemon.notice] DNS
format error from 200.124.224.199#53 resolving dns04.telmex.ec/AAAA: unrelated
AAAA dns04.telmex.ec in dns04.telmex.ec.telmex.ec authority section
Feb 19 14:41:52 my.domain.net named[20234]: [ID 873579 daemon.notice] DNS
format error from 200.124.247.199#53 resolving dns03.telmex.ec/AAAA: unrelated
AAAA dns03.telmex.ec in dns03.telmex.ec.telmex.ec authority section
Feb 19 14:41:52 my.domain.net named[20234]: [ID 873579 daemon.notice] DNS
format error from 200.124.224.199#53 resolving dns01.telmex.ec/AAAA: unrelated
AAAA dns01.telmex.ec in dns01.telmex.ec.telmex.ec authority section
Feb 19 14:41:52 my.domain.net named[20234]: [ID 873579 daemon.notice] DNS
format error from 200.124.247.201#53 resolving dns02.telmex.ec/AAAA: unrelated
AAAA dns02.telmex.ec in dns02.telmex.ec.telmex.ec authority section
Feb 19 14:41:52 my.domain.net named[20234]: [ID 873579 daemon.notice] DNS
format error from 200.124.247.201#53 resolving dns04.telmex.ec/AAAA: unrelated
AAAA dns04.telmex.ec in dns04.telmex.ec.telmex.ec authority section
Feb 19 14:42:01 my.domain.net named[20234]: [ID 873579 daemon.notice] DNS
format error from 212.217.1.12#53 resolving
adsl196-144-46-217-196.adsl196-10.iam.net.ma/A for client 216.108.160.20#24429:
sideways referral
Feb 19 14:42:01 my.domain.net named[20234]: [ID 873579 daemon.notice] DNS
format error from 212.217.0.1#53 resolving
adsl196-144-46-217-196.adsl196-10.iam.net.ma/A for client 216.108.160.20#24429:
sideways referral
Feb 19 14:42:02 my.domain.net named[20234]: [ID 873579 daemon.notice] DNS
format error from 212.217.1.1#53 resolving
adsl196-144-46-217-196.adsl196-10.iam.net.ma/A for client 216.108.160.20#24429:
sideways referral
Feb 19 14:42:14 my.domain.net named[20234]: [ID 873579 daemon.notice] DNS
format error from 200.142.130.10#53 resolving 96.16.117.187.in-addr.arpa/PTR
for client 216.108.160.20#36612: sideways referral
Feb 19 14:42:22 my.domain.net named[20234]: [ID 873579 daemon.notice] DNS
format error from 212.217.1.12#53 resolving
adsl196-128-206-206-196.adsl196-7.iam.net.ma/A for client 216.108.160.30#11889:
sideways referral
_______________________________________________
bind-users mailing list
bind-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/bind-users
