Re: New problem with lame-server after Dist-Upgrade
On Dec 28, 2011, at 8:56 PM, Chris Buxton wrote: On Dec 24, 2011, at 4:50 PM, Michelle Konzack wrote: Dec 25 01:39:02 storage000 named[29649]: lame-servers: info: error (network unreachable) resolving 'www4.l.google.com//IN': 2001:503:231d::2:30#53 Dec 25 01:40:10 storage000 named[29649]: lame-servers: info: error (network unreachable) resolving 'ns2.roka.net//IN': 2001:500:1::803f:235#53 Dec 25 01:40:10 storage000 named[29649]: lame-servers: info: error (network unreachable) resolving 'dns.roka.net//IN': 2001:748:100:70::2#53 Dec 25 01:42:02 storage000 named[29649]: lame-servers: info: error (network unreachable) resolving 'www.kaleme.com//IN': 2001:503:a83e::2:30#53 Dec 25 01:42:02 storage000 named[29649]: lame-servers: info: error (network unreachable) resolving 'pdns3.ultradns.org/A/IN': 2001:500:2f::f#53 Dec 25 01:42:02 storage000 named[29649]: lame-servers: info: error (network unreachable) resolving 'pdns4.ultradns.org/A/IN': 2001:500:2f::f#53 Dec 25 01:42:02 storage000 named[29649]: lame-servers: info: error (network unreachable) resolving 'pdns3.ultradns.org//IN': 2001:503:c27::2:30#53 Dec 25 01:42:02 storage000 named[29649]: lame-servers: info: error (network unreachable) resolving 'pdns4.ultradns.org//IN': 2001:503:ba3e::2:30#53 Dec 25 01:42:02 storage000 named[29649]: lame-servers: info: error (network unreachable) resolving 'pdns3.ultradns.org/A/IN': 2001:dc3::35#53 Dec 25 01:42:02 storage000 named[29649]: lame-servers: info: error (network unreachable) resolving 'pdns4.ultradns.org/A/IN': 2001:503:c27::2:30#53 Dec 25 01:42:02 storage000 named[29649]: lame-servers: info: error (network unreachable) resolving 'pdns4.ultradns.org/A/IN': 2001:503:ba3e::2:30#53 Dec 25 01:42:02 storage000 named[29649]: lame-servers: info: error (network unreachable) resolving 'pdns4.ultradns.org/A/IN': 2001:7fd::1#53 Dec 25 01:42:02 storage000 named[29649]: lame-servers: info: error (network unreachable) resolving 'pdns3.ultradns.org//IN': 2001:7fd::1#53 Dec 25 01:42:02 storage000 named[29649]: lame-servers: info: error (network unreachable) resolving 'pdns5.ultradns.info/A/IN': 2001:500:19::1#53 Dec 25 01:42:02 storage000 named[29649]: lame-servers: info: error (network unreachable) resolving 'pdns5.ultradns.info/A/IN': 2001:500:1a::1#53 Dec 25 01:42:02 storage000 named[29649]: lame-servers: info: error (network unreachable) resolving 'pdns4.ultradns.org//IN': 2001:500:40::1#53 Dec 25 01:42:02 storage000 named[29649]: lame-servers: info: error (network unreachable) resolving 'pdns4.ultradns.org/A/IN': 2001:502:4612::1#53 That tells me your IPv6 connectivity is probably broken. Either fix it or disable IPv6 in named by starting it with -4. So Bind's 'lame' log line includes the concept of 'unreachable'? I seem to recall the definition 'delegation target that answers without aa'. However, given the '(network unreachable)' comment, I agree with your diagnosis. John Wobus Cornell ___ Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
Re: New problem with lame-server after Dist-Upgrade
Sorry to come into the conversation late, but I've been on vacation. On Dec 24, 2011, at 4:50 PM, Michelle Konzack wrote: Dec 25 01:39:02 storage000 named[29649]: lame-servers: info: error (network unreachable) resolving 'www4.l.google.com//IN': 2001:503:231d::2:30#53 Dec 25 01:40:10 storage000 named[29649]: lame-servers: info: error (network unreachable) resolving 'ns2.roka.net//IN': 2001:500:1::803f:235#53 Dec 25 01:40:10 storage000 named[29649]: lame-servers: info: error (network unreachable) resolving 'dns.roka.net//IN': 2001:748:100:70::2#53 Dec 25 01:42:02 storage000 named[29649]: lame-servers: info: error (network unreachable) resolving 'www.kaleme.com//IN': 2001:503:a83e::2:30#53 Dec 25 01:42:02 storage000 named[29649]: lame-servers: info: error (network unreachable) resolving 'pdns3.ultradns.org/A/IN': 2001:500:2f::f#53 Dec 25 01:42:02 storage000 named[29649]: lame-servers: info: error (network unreachable) resolving 'pdns4.ultradns.org/A/IN': 2001:500:2f::f#53 Dec 25 01:42:02 storage000 named[29649]: lame-servers: info: error (network unreachable) resolving 'pdns3.ultradns.org//IN': 2001:503:c27::2:30#53 Dec 25 01:42:02 storage000 named[29649]: lame-servers: info: error (network unreachable) resolving 'pdns4.ultradns.org//IN': 2001:503:ba3e::2:30#53 Dec 25 01:42:02 storage000 named[29649]: lame-servers: info: error (network unreachable) resolving 'pdns3.ultradns.org/A/IN': 2001:dc3::35#53 Dec 25 01:42:02 storage000 named[29649]: lame-servers: info: error (network unreachable) resolving 'pdns4.ultradns.org/A/IN': 2001:503:c27::2:30#53 Dec 25 01:42:02 storage000 named[29649]: lame-servers: info: error (network unreachable) resolving 'pdns4.ultradns.org/A/IN': 2001:503:ba3e::2:30#53 Dec 25 01:42:02 storage000 named[29649]: lame-servers: info: error (network unreachable) resolving 'pdns4.ultradns.org/A/IN': 2001:7fd::1#53 Dec 25 01:42:02 storage000 named[29649]: lame-servers: info: error (network unreachable) resolving 'pdns3.ultradns.org//IN': 2001:7fd::1#53 Dec 25 01:42:02 storage000 named[29649]: lame-servers: info: error (network unreachable) resolving 'pdns5.ultradns.info/A/IN': 2001:500:19::1#53 Dec 25 01:42:02 storage000 named[29649]: lame-servers: info: error (network unreachable) resolving 'pdns5.ultradns.info/A/IN': 2001:500:1a::1#53 Dec 25 01:42:02 storage000 named[29649]: lame-servers: info: error (network unreachable) resolving 'pdns4.ultradns.org//IN': 2001:500:40::1#53 Dec 25 01:42:02 storage000 named[29649]: lame-servers: info: error (network unreachable) resolving 'pdns4.ultradns.org/A/IN': 2001:502:4612::1#53 That tells me your IPv6 connectivity is probably broken. Either fix it or disable IPv6 in named by starting it with -4. Regards, Chris Buxton BlueCat Networks ___ Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
New problem with lame-server after Dist-Upgrade
Hello *, my Inttranet NameServer (my DNS-Master) was running Debian Lenny/5.0 and is now upgraded to Debian Squeeze/6.0 and et I get per day very huge named.log files, because: [ '/var/log/named.log' ] Dec 25 00:21:01 dns named[29004]: lame-servers: info: error (unexpected RCODE REFUSED) resolving 'www.erdbeerlounge.de//IN': 78.47.247.21#53 Dec 25 00:21:01 dns named[29004]: lame-servers: info: error (unexpected RCODE REFUSED) resolving 'www.erdbeerlounge.de/A/IN': 78.47.247.21#53 Dec 25 00:21:01 dns named[29004]: lame-servers: info: error (connection refused) resolving 'www.erdbeerlounge.de//IN': 217.147.94.23#53 Dec 25 00:21:01 dns named[29004]: lame-servers: info: error (connection refused) resolving 'www.erdbeerlounge.de/A/IN': 217.147.94.23#53 Dec 25 00:21:01 dns named[29004]: lame-servers: info: error (unexpected RCODE REFUSED) resolving 'ns1.dns24.net/A/IN': 78.47.247.21#53 Dec 25 00:21:01 dns named[29004]: lame-servers: info: error (unexpected RCODE REFUSED) resolving 'ns2.dns24.net/A/IN': 78.47.247.21#53 Dec 25 00:21:01 dns named[29004]: lame-servers: info: error (unexpected RCODE REFUSED) resolving 'ns1.dns24.net//IN': 78.47.247.21#53 Dec 25 00:21:01 dns named[29004]: lame-servers: info: error (unexpected RCODE REFUSED) resolving 'ns2.dns24.net//IN': 78.47.247.21#53 Dec 25 00:21:01 dns named[29004]: lame-servers: info: error (unexpected RCODE REFUSED) resolving 'ns3.dns24.net/A/IN': 78.47.247.21#53 Dec 25 00:21:01 dns named[29004]: lame-servers: info: error (unexpected RCODE REFUSED) resolving 'ns4.dns24.net/A/IN': 78.47.247.21#53 Dec 25 00:21:01 dns named[29004]: lame-servers: info: error (unexpected RCODE REFUSED) resolving 'ns3.dns24.net//IN': 78.47.247.21#53 Dec 25 00:21:01 dns named[29004]: lame-servers: info: error (unexpected RCODE REFUSED) resolving 'ns4.dns24.net//IN': 78.47.247.21#53 Dec 25 00:21:01 dns named[29004]: lame-servers: info: error (unexpected RCODE REFUSED) resolving 'ns1.dns24.net/A/IN': 78.47.104.44#53 Dec 25 00:21:01 dns named[29004]: lame-servers: info: error (unexpected RCODE REFUSED) resolving 'ns2.dns24.net/A/IN': 78.47.104.44#53 Dec 25 00:21:01 dns named[29004]: lame-servers: info: error (unexpected RCODE REFUSED) resolving 'ns1.dns24.net//IN': 78.47.104.44#53 Dec 25 00:21:01 dns named[29004]: lame-servers: info: error (unexpected RCODE REFUSED) resolving 'ns2.dns24.net//IN': 78.47.104.44#53 Dec 25 00:21:01 dns named[29004]: lame-servers: info: error (unexpected RCODE REFUSED) resolving 'ns3.dns24.net/A/IN': 78.47.104.44#53 Dec 25 00:21:01 dns named[29004]: lame-servers: info: error (unexpected RCODE REFUSED) resolving 'ns4.dns24.net/A/IN': 78.47.104.44#53 Dec 25 00:21:01 dns named[29004]: lame-servers: info: error (unexpected RCODE REFUSED) resolving 'ns3.dns24.net//IN': 78.47.104.44#53 Dec 25 00:21:01 dns named[29004]: lame-servers: info: error (unexpected RCODE REFUSED) resolving 'ns4.dns24.net//IN': 78.47.104.44#53 Dec 25 00:21:02 dns named[29004]: lame-servers: info: error (connection refused) resolving 'ns1.dns24.net/A/IN': 217.147.94.23#53 Dec 25 00:21:02 dns named[29004]: lame-servers: info: error (connection refused) resolving 'ns2.dns24.net/A/IN': 217.147.94.23#53 Dec 25 00:21:02 dns named[29004]: lame-servers: info: error (connection refused) resolving 'ns1.dns24.net//IN': 217.147.94.23#53 Dec 25 00:21:02 dns named[29004]: lame-servers: info: error (connection refused) resolving 'ns2.dns24.net//IN': 217.147.94.23#53 Dec 25 00:21:02 dns named[29004]: lame-servers: info: error (unexpected RCODE REFUSED) resolving 'dns1.name-services.com/A/IN': 78.47.104.44#53 Dec 25 00:21:02 dns named[29004]: lame-servers: info: error (unexpected RCODE REFUSED) resolving 'dns2.name-services.com/A/IN': 78.47.104.44#53 Dec 25 00:21:02 dns named[29004]: lame-servers: info: error (unexpected RCODE REFUSED) resolving 'dns1.name-services.com//IN': 78.47.104.44#53 Dec 25 00:21:02 dns named[29004]: lame-servers: info: error (unexpected RCODE REFUSED) resolving 'dns2.name-services.com//IN': 78.47.104.44#53 Dec 25 00:21:02 dns named[29004]: lame-servers: info: error (unexpected RCODE REFUSED) resolving 'dns3.name-services.com/A/IN': 78.47.104.44#53 Dec 25 00:21:02 dns named[29004]: lame-servers: info: error (unexpected RCODE REFUSED) resolving 'dns4.name-services.com/A/IN': 78.47.104.44#53 Dec 25 00:21:02 dns named[29004]: lame-servers: info: error (unexpected RCODE REFUSED) resolving 'dns3.name-services.com//IN': 78.47.104.44#53 Dec 25 00:21:02 dns named[29004]: lame-servers: info: error (unexpected RCODE REFUSED) resolving 'dns4.name-services.com//IN': 78.47.104.44#53 Dec 25 00:21:02 dns named[29004]: lame-servers: info: error (unexpected RCODE REFUSED) resolving 'dns5.name-services.com/A/IN': 78.47.104.44#53 Dec 25 00:21:02 dns named[29004]: lame-servers: info: error (unexpected RCODE REFUSED) resolving
Re: New problem with lame-server after Dist-Upgrade
Did the BIND version change with the OS upgrade? -Ben Croswell On Dec 24, 2011 6:38 PM, Michelle Konzack linux4miche...@tamay-dogan.net wrote: Hello *, my Inttranet NameServer (my DNS-Master) was running Debian Lenny/5.0 and is now upgraded to Debian Squeeze/6.0 and et I get per day very huge named.log files, because: [ '/var/log/named.log' ] Dec 25 00:21:01 dns named[29004]: lame-servers: info: error (unexpected RCODE REFUSED) resolving 'www.erdbeerlounge.de//IN': 78.47.247.21#53 Dec 25 00:21:01 dns named[29004]: lame-servers: info: error (unexpected RCODE REFUSED) resolving 'www.erdbeerlounge.de/A/IN': 78.47.247.21#53 Dec 25 00:21:01 dns named[29004]: lame-servers: info: error (connection refused) resolving 'www.erdbeerlounge.de//IN': 217.147.94.23#53 Dec 25 00:21:01 dns named[29004]: lame-servers: info: error (connection refused) resolving 'www.erdbeerlounge.de/A/IN': 217.147.94.23#53 Dec 25 00:21:01 dns named[29004]: lame-servers: info: error (unexpected RCODE REFUSED) resolving 'ns1.dns24.net/A/IN': 78.47.247.21#53 Dec 25 00:21:01 dns named[29004]: lame-servers: info: error (unexpected RCODE REFUSED) resolving 'ns2.dns24.net/A/IN': 78.47.247.21#53 Dec 25 00:21:01 dns named[29004]: lame-servers: info: error (unexpected RCODE REFUSED) resolving 'ns1.dns24.net//IN': 78.47.247.21#53 Dec 25 00:21:01 dns named[29004]: lame-servers: info: error (unexpected RCODE REFUSED) resolving 'ns2.dns24.net//IN': 78.47.247.21#53 Dec 25 00:21:01 dns named[29004]: lame-servers: info: error (unexpected RCODE REFUSED) resolving 'ns3.dns24.net/A/IN': 78.47.247.21#53 Dec 25 00:21:01 dns named[29004]: lame-servers: info: error (unexpected RCODE REFUSED) resolving 'ns4.dns24.net/A/IN': 78.47.247.21#53 Dec 25 00:21:01 dns named[29004]: lame-servers: info: error (unexpected RCODE REFUSED) resolving 'ns3.dns24.net//IN': 78.47.247.21#53 Dec 25 00:21:01 dns named[29004]: lame-servers: info: error (unexpected RCODE REFUSED) resolving 'ns4.dns24.net//IN': 78.47.247.21#53 Dec 25 00:21:01 dns named[29004]: lame-servers: info: error (unexpected RCODE REFUSED) resolving 'ns1.dns24.net/A/IN': 78.47.104.44#53 Dec 25 00:21:01 dns named[29004]: lame-servers: info: error (unexpected RCODE REFUSED) resolving 'ns2.dns24.net/A/IN': 78.47.104.44#53 Dec 25 00:21:01 dns named[29004]: lame-servers: info: error (unexpected RCODE REFUSED) resolving 'ns1.dns24.net//IN': 78.47.104.44#53 Dec 25 00:21:01 dns named[29004]: lame-servers: info: error (unexpected RCODE REFUSED) resolving 'ns2.dns24.net//IN': 78.47.104.44#53 Dec 25 00:21:01 dns named[29004]: lame-servers: info: error (unexpected RCODE REFUSED) resolving 'ns3.dns24.net/A/IN': 78.47.104.44#53 Dec 25 00:21:01 dns named[29004]: lame-servers: info: error (unexpected RCODE REFUSED) resolving 'ns4.dns24.net/A/IN': 78.47.104.44#53 Dec 25 00:21:01 dns named[29004]: lame-servers: info: error (unexpected RCODE REFUSED) resolving 'ns3.dns24.net//IN': 78.47.104.44#53 Dec 25 00:21:01 dns named[29004]: lame-servers: info: error (unexpected RCODE REFUSED) resolving 'ns4.dns24.net//IN': 78.47.104.44#53 Dec 25 00:21:02 dns named[29004]: lame-servers: info: error (connection refused) resolving 'ns1.dns24.net/A/IN': 217.147.94.23#53 Dec 25 00:21:02 dns named[29004]: lame-servers: info: error (connection refused) resolving 'ns2.dns24.net/A/IN': 217.147.94.23#53 Dec 25 00:21:02 dns named[29004]: lame-servers: info: error (connection refused) resolving 'ns1.dns24.net//IN': 217.147.94.23#53 Dec 25 00:21:02 dns named[29004]: lame-servers: info: error (connection refused) resolving 'ns2.dns24.net//IN': 217.147.94.23#53 Dec 25 00:21:02 dns named[29004]: lame-servers: info: error (unexpected RCODE REFUSED) resolving 'dns1.name-services.com/A/IN': 78.47.104.44#53 Dec 25 00:21:02 dns named[29004]: lame-servers: info: error (unexpected RCODE REFUSED) resolving 'dns2.name-services.com/A/IN': 78.47.104.44#53 Dec 25 00:21:02 dns named[29004]: lame-servers: info: error (unexpected RCODE REFUSED) resolving 'dns1.name-services.com//IN': 78.47.104.44#53 Dec 25 00:21:02 dns named[29004]: lame-servers: info: error (unexpected RCODE REFUSED) resolving 'dns2.name-services.com//IN': 78.47.104.44#53 Dec 25 00:21:02 dns named[29004]: lame-servers: info: error (unexpected RCODE REFUSED) resolving 'dns3.name-services.com/A/IN': 78.47.104.44#53 Dec 25 00:21:02 dns named[29004]: lame-servers: info: error (unexpected RCODE REFUSED) resolving 'dns4.name-services.com/A/IN': 78.47.104.44#53 Dec 25 00:21:02 dns named[29004]: lame-servers: info: error (unexpected RCODE REFUSED) resolving 'dns3.name-services.com//IN': 78.47.104.44#53 Dec 25 00:21:02 dns named[29004]: lame-servers: info: error (unexpected RCODE REFUSED) resolving 'dns4.name-services.com//IN': 78.47.104.44#53 Dec 25 00:21:02 dns named[29004]: lame-servers: info: error (unexpected RCODE REFUSED)
Re: New problem with lame-server after Dist-Upgrade
Hello Ben Croswell, Am 2011-12-24 18:42:09, hacktest Du folgendes herunter: Did the BIND version change with the OS upgrade? Yes. I had this problem some years ago: 8-- Mark Andrews marka at isc.org Tue Aug 3 22:32:29 UTC 2010 * Previous message: unexpected RCODE (REFUSED) resolving * Next message: unexpected RCODE (REFUSED) resolving * Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] In message 20100803142625.GC27217 at tamay-dogan.net, Michelle Konzack writes: This is a MIME-formatted message. If you see this text it means that your E-mail software does not support MIME-formatted messages. Hello, since today morning (~06:30 CEST) I get several 1.000 errors like: [ '/var/log/named.log' ] Aug 3 10:12:39 dns1 named[26425]: 03-Aug-2010 10:12:39.951 lame-servers: i= nfo: unexpected RCODE (REFUSED) resolving 'lists.colo.xensource.com/A/IN': = 68.156.138.136#53 Basically you need to complain to the administators for xensource.com to get the delegation cleaned up or the server configured. xensource.com is delegated to 68.156.138.136 but that server is refusing to answer queries for the xensource.com. Additionally according to ns1.xensource.com both ns0.xensource.com and ns2.xensource.com no longer exist. The administrators for xensource.com need to clean up the delegation by contacting their registrar and removing ns0.xensource.com from delegation. They also need to clean up the delegation for colo.xensource.com as that has ns0 and ns2 listed which don't exist. 8-- but if I follow his answer, it mean, more than 800 servers have this issue! This can not be... Or are those admins realy braindamaged? Sometimes I see a bunch of lines lame-servers and following by edns-disabled lines with the same servers queried... Thanks, Greetings and nice Day/Evening Michelle Konzack -- # Debian GNU/Linux Consultant ## Development of Intranet and Embedded Systems with Debian GNU/Linux Internet Service Provider, Cloud Computing http://www.itsystems.tamay-dogan.net/ itsystems@tdnet Jabber linux4miche...@jabber.ccc.de Owner Michelle Konzack Gewerbe Strasse 3 Tel office: +49-176-86004575 77694 Kehl Tel mobil: +49-177-9351947 Germany Tel mobil: +33-6-61925193 (France) USt-ID: DE 278 049 239 Linux-User #280138 with the Linux Counter, http://counter.li.org/ signature.pgp Description: Digital signature ___ Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
Re: New problem with lame-server after Dist-Upgrade
For soem seconds I have read a message (not from me) where someone asked, whether forwarders where configured and do not accept queries... So I have removed my forwarders and restarted bind9: --[ '/var/log/named.log' ]-- Dec 25 01:36:09 storage000 named[2009]: general: info: received control channel command 'stop -p' Dec 25 01:36:09 storage000 named[2009]: general: info: shutting down: flushing changes Dec 25 01:36:09 storage000 named[2009]: general: notice: stopping command channel on 127.0.0.1#953 Dec 25 01:36:09 storage000 named[2009]: network: info: no longer listening on ::#53 Dec 25 01:36:09 storage000 named[2009]: network: info: no longer listening on 192.168.0.11#53 Dec 25 01:36:09 storage000 named[2009]: general: notice: exiting Dec 25 01:36:10 storage000 named[29649]: general: info: zone 0.in-addr.arpa/IN: loaded serial 1 Dec 25 01:36:10 storage000 named[29649]: general: info: zone 127.in-addr.arpa/IN: loaded serial 1 Dec 25 01:36:10 storage000 named[29649]: general: warning: /etc/bind/db.192.168.0:3: using RFC1035 TTL semantics Dec 25 01:36:10 storage000 named[29649]: general: info: zone 0.168.192.in-addr.arpa/IN: loaded serial 1324544307 Dec 25 01:36:10 storage000 named[29649]: general: info: zone 255.in-addr.arpa/IN: loaded serial 1 Dec 25 01:36:10 storage000 named[29649]: general: warning: /etc/bind/DNS_TRASH:3: using RFC1035 TTL semantics Dec 25 01:36:10 storage000 named[29649]: general: info: zone google-analytics.com/IN: loaded serial 1301273151 Dec 25 01:36:10 storage000 named[29649]: general: warning: /etc/bind/DNS_TRASH:3: using RFC1035 TTL semantics Dec 25 01:36:10 storage000 named[29649]: general: info: zone googleadservices.com/IN: loaded serial 1301273151 Dec 25 01:36:10 storage000 named[29649]: general: warning: /etc/bind/DNS_TRASH:3: using RFC1035 TTL semantics Dec 25 01:36:10 storage000 named[29649]: general: info: zone googlesyndication.com/IN: loaded serial 1301273151 Dec 25 01:36:10 storage000 named[29649]: general: info: zone tdaerospace.com/IN: loaded serial 1324032239 (DNSSEC signed) Dec 25 01:36:10 storage000 named[29649]: general: info: zone tdnet.eu/IN: loaded serial 1324032239 (DNSSEC signed) Dec 25 01:36:10 storage000 named[29649]: general: info: zone localhost/IN: loaded serial 2 Dec 25 01:36:10 storage000 named[29649]: general: info: zone tamay-dogan.net/IN: loaded serial 1324032239 (DNSSEC signed) Dec 25 01:36:10 storage000 named[29649]: general: info: zone cybercenter.tamay-dogan.net/IN: loaded serial 1324032239 (DNSSEC signed) Dec 25 01:36:10 storage000 named[29649]: general: info: zone debian.tamay-dogan.net/IN: loaded serial 1324032239 (DNSSEC signed) Dec 25 01:36:10 storage000 named[29649]: general: info: zone ecocity.tamay-dogan.net/IN: loaded serial 1324032239 (DNSSEC signed) Dec 25 01:36:10 storage000 named[29649]: general: info: zone electronica.tamay-dogan.net/IN: loaded serial 1324032239 (DNSSEC signed) Dec 25 01:36:10 storage000 named[29649]: general: info: zone energia.tamay-dogan.net/IN: loaded serial 1324032239 (DNSSEC signed) Dec 25 01:36:10 storage000 named[29649]: general: info: zone geoip.tamay-dogan.net/IN: loaded serial 1324032239 (DNSSEC signed) Dec 25 01:36:10 storage000 named[29649]: general: info: zone home.tamay-dogan.net/IN: loaded serial 1324032239 (DNSSEC signed) Dec 25 01:36:10 storage000 named[29649]: general: info: zone intranet1.tamay-dogan.net/IN: loaded serial 1324032240 (DNSSEC signed) Dec 25 01:36:10 storage000 named[29649]: general: info: zone intranet2.tamay-dogan.net/IN: loaded serial 1324032240 (DNSSEC signed) Dec 25 01:36:10 storage000 named[29649]: general: info: zone itsystems.tamay-dogan.net/IN: loaded serial 1324032239 (DNSSEC signed) Dec 25 01:36:10 storage000 named[29649]: general: info: zone onlinestore.tamay-dogan.net/IN: loaded serial 1324032239 (DNSSEC signed) Dec 25 01:36:10 storage000 named[29649]: general: info: zone pmcos.tamay-dogan.net/IN: loaded serial 1324032240 (DNSSEC signed) Dec 25 01:36:10 storage000 named[29649]: general: info: zone private.tamay-dogan.net/IN: loaded serial 1324032239 (DNSSEC signed) Dec 25 01:36:10 storage000 named[29649]: general: info: zone redhat.tamay-dogan.net/IN: loaded serial 1324032239 (DNSSEC signed) Dec 25 01:36:10 storage000 named[29649]: general: info: zone tdaerospace.net/IN: loaded serial 1324032239 (DNSSEC signed) Dec 25 01:36:10 storage000 named[29649]: general: info: zone tdcloud.net/IN: loaded serial 1324032240 (DNSSEC signed) Dec 25 01:36:10 storage000 named[29649]: general: info: zone tdhome.net/IN: loaded serial 1324032240 (DNSSEC signed) Dec 25 01:36:10 storage000 named[29649]: general: info: zone tdipmedia.net/IN: loaded serial 1324032240 (DNSSEC signed) Dec 25 01:36:10 storage000 named[29649]: general: info: zone tdvoip.net/IN: loaded serial 1324032240 (DNSSEC signed) Dec 25 01:36:10 storage000 named[29649]: general: info: zone tdwave.net/IN: loaded serial 1324032239 (DNSSEC
