Re: ISC BIND 9.7.0 syslog recorded notices
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/ 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/ 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/ 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/ 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/ 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/ 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/ 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/ 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/ 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/ 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/ 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/ 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/ 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/ 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/ 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/ 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:
Re: ISC BIND 9.7.0 syslog recorded notices
On Fri, 19 Feb 2010, ic.nssip wrote: 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. Hi. This is a new feature as listed in CHANGES file: 2770. [cleanup] Add log messages to resolver.c to indicate events causing FORMERR responses. [RT #20526] Yes, it does seem busy for you. Some loggings maybe could be made more clear, for example: stats.surfaid.ihost.com/ no SOA returned ns6.chordhurry.ru./ In SOA . is not chordhurry.ru. ns1.dayeither.com. In SOA . is not dayeither.com ___ bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
Re: ISC BIND 9.7.0 syslog recorded notices
On Fri, 19 Feb 2010, Jeremy C. Reed wrote: Some loggings maybe could be made more clear, for example: stats.surfaid.ihost.com/ no SOA returned Not sure why I saw that. Looking again I see com. But I have other problems there too. ___ bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
