Article View: alt.pl.freesco
Article #159Re: Podtrzymywanie połączenia NEO+
From: Mak
Date: Sat, 01 Mar 2003 19:00
Date: Sat, 01 Mar 2003 19:00
1858 lines
81880 bytes
81880 bytes
Wkleje tu log z freesco, może wy coś wykombinujecie :( Mar 1 19:39:41 - syslogd 1.3-3: restart (remote reception). Mar 1 19:39:42 - kernel: Kernel logging (proc) started. Mar 1 19:39:42 - kernel: Memory: sized by int13 088h Mar 1 19:39:42 - kernel: Console: 16 point font, 480 scans Mar 1 19:39:42 - kernel: Console: colour VGA+ 80x30, 1 virtual console (max 63) Mar 1 19:39:42 - kernel: pcibios_init : BIOS32 Service Directory structure at 0x000fb2b0 Mar 1 19:39:42 - kernel: pcibios_init : BIOS32 Service Directory entry at 0xfb740 Mar 1 19:39:42 - kernel: pcibios_init : PCI BIOS revision 2.10 entry at 0xfb770 Mar 1 19:39:42 - kernel: Probing PCI hardware. Mar 1 19:39:42 - kernel: Calibrating delay loop.. ok - 29.90 BogoMIPS Mar 1 19:39:42 - kernel: Memory: 22156k/24576k available (696k kernel code, 384k reserved, 612k data) Mar 1 19:39:42 - kernel: Swansea University Computer Society NET3.035 for Linux 2.0 Mar 1 19:39:42 - kernel: NET3: Unix domain sockets 0.13 for Linux NET3.035. Mar 1 19:39:42 - kernel: Swansea University Computer Society TCP/IP for NET3.034 Mar 1 19:39:42 - kernel: IP Protocols: IGMP, ICMP, UDP, TCP Mar 1 19:39:42 - kernel: Linux IP multicast router 0.07. Mar 1 19:39:42 - kernel: Checking 'hlt' instruction... disabled Mar 1 19:39:42 - kernel: Intel Pentium with F0 0F bug - workaround enabled. Mar 1 19:39:42 - kernel: alias mapping IDT readonly ... ... done Mar 1 19:39:42 - kernel: Linux version 2.0.38 (root@localhost.localdomain) (gcc version 2.7.2.3) #4 Wed May 17 22:55:01 EDT 2000 Mar 1 19:39:42 - kernel: Starting kswapd v 1.4.2.2 Mar 1 19:39:42 - kernel: Serial driver version 4.13p1 with no serial options enabled Mar 1 19:39:42 - kernel: ttyS00 at 0x03f8 (irq = 4) is a 16550A Mar 1 19:39:42 - kernel: ttyS01 at 0x02f8 (irq = 3) is a 16550A Mar 1 19:39:42 - kernel: lp1 at 0x0378, (polling) Mar 1 19:39:42 - kernel: Real Time Clock Driver v1.09 Mar 1 19:39:42 - kernel: Ramdisk driver initialized : 16 ramdisks of 4096K size Mar 1 19:39:42 - kernel: loop: registered device at major 7 Mar 1 19:39:42 - kernel: Floppy drive(s): fd0 is 1.44M Mar 1 19:39:42 - kernel: FDC 0 is a post-1991 82077 Mar 1 19:39:42 - kernel: Ethernet Bridge 002 for NET3.035 (Linux 2.0) Mar 1 19:39:42 - kernel: PPP: version 2.3.10 (demand dialling) Mar 1 19:39:42 - kernel: TCP compression code copyright 1989 Regents of the University of California Mar 1 19:39:42 - kernel: PPP line discipline registered. Mar 1 19:39:42 - kernel: SLIP: version 0.8.4-NET3.019-NEWTTY (dynamic channels, max=256). Mar 1 19:39:42 - kernel: CSLIP: code copyright 1989 Regents of the University of California. Mar 1 19:39:42 - kernel: RAMDISK: Compressed image found at block 0 Mar 1 19:39:42 - kernel: EXT2-fs warning: checktime reached, running e2fsck is recommended Mar 1 19:39:42 - kernel: VFS: Mounted root (ext2 filesystem). Mar 1 19:39:42 - kernel: VFS: Disk change detected on device 02:00 Mar 1 19:39:43 - kernel: UMSDOS Beta 0.6 (compatibility level 0.4, fast msdos) Mar 1 19:39:58 - syslogd 1.3-3: restart (remote reception). Mar 1 19:40:02 - kernel: ip_masq_icq: using TCP port range 60200-61000 Mar 1 19:40:02 - kernel: ip_masq_icq: loaded support on port 4000/UDP Mar 1 19:40:03 - kernel: Init module Mar 1 19:40:03 - kernel: H323: loaded support on port[0] = 1720 Mar 1 19:40:03 - insmod: Cannot open /mnt/router/drv/*.o Mar 1 19:40:03 - insmod: Cannot open /mnt/router/drv/*.o Mar 1 19:40:03 - insmod: Symbol 'io' not found Mar 1 19:40:03 - last message repeated 7 times Mar 1 19:40:03 - kernel: smc-ultra.c: No SMC Ultra card found (i/o = 0x300). Mar 1 19:40:03 - insmod: Initialization of /tmp/net/smc-ultra.o.A0 failed Mar 1 19:40:03 - kernel: smc-ultra.c: No SMC Ultra card found (i/o = 0x300). Mar 1 19:40:03 - insmod: Initialization of /tmp/net/smc-ultra.o.B0 failed Mar 1 19:40:03 - insmod: Symbol 'io' not found Mar 1 19:40:03 - insmod: Symbol 'io' not found Mar 1 19:40:03 - kernel: ne.c: No NE*000 card found at i/o = 0x300 Mar 1 19:40:03 - insmod: Initialization of /tmp/prm/ne.o.A0 failed Mar 1 19:40:03 - kernel: ne.c: No NE*000 card found at i/o = 0x300 Mar 1 19:40:03 - insmod: Initialization of /tmp/prm/ne.o.B0 failed Mar 1 19:40:03 - insmod: Cannot open /mnt/router/drv/*.o Mar 1 19:40:03 - insmod: Cannot open /mnt/router/drv/*.o Mar 1 19:40:03 - insmod: Symbol 'io' not found Mar 1 19:40:03 - last message repeated 7 times Mar 1 19:40:03 - kernel: smc-ultra.c: Presently autoprobing (not recommended) for a single card. Mar 1 19:40:03 - kernel: smc-ultra.c: No SMC Ultra card found (i/o = 0x0). Mar 1 19:40:03 - insmod: Initialization of /tmp/net/smc-ultra.o.A1 failed Mar 1 19:40:04 - kernel: smc-ultra.c: Presently autoprobing (not recommended) for a single card. Mar 1 19:40:04 - kernel: smc-ultra.c: No SMC Ultra card found (i/o = 0x0). Mar 1 19:40:04 - insmod: Initialization of /tmp/net/smc-ultra.o.B1 failed Mar 1 19:40:04 - insmod: Symbol 'io' not found Mar 1 19:40:04 - insmod: Symbol 'io' not found Mar 1 19:40:04 - kernel: ne.c: PCI BIOS reports NE 2000 clone at i/o 0x6000, irq 9. Mar 1 19:40:04 - kernel: ne.c:v1.10 9/23/94 Donald Becker (becker@cesdis.gsfc.nasa.gov) Mar 1 19:40:04 - kernel: NE*000 ethercard probe at 0x6000: 00 c0 df f2 d0 60 Mar 1 19:40:04 - kernel: eth0: NE2000 found at 0x6000, using IRQ 9. Mar 1 19:40:04 - kernel: ne.c: PCI BIOS reports NE 2000 clone at i/o 0x6100, irq 11. Mar 1 19:40:04 - kernel: NE*000 ethercard probe at 0x6100: 00 c0 df f2 d7 e3 Mar 1 19:40:04 - kernel: eth1: NE2000 found at 0x6100, using IRQ 11. Mar 1 19:40:04 - insmod: Cannot open /mnt/router/drv/*.o Mar 1 19:40:04 - insmod: Cannot open /mnt/router/drv/*.o Mar 1 19:40:04 - insmod: Symbol 'io' not found Mar 1 19:40:04 - last message repeated 7 times Mar 1 19:40:04 - kernel: smc-ultra.c: Presently autoprobing (not recommended) for a single card. Mar 1 19:40:04 - kernel: smc-ultra.c: No SMC Ultra card found (i/o = 0x0). Mar 1 19:40:04 - insmod: Initialization of /tmp/net/smc-ultra.o.A2 failed Mar 1 19:40:04 - kernel: smc-ultra.c: Presently autoprobing (not recommended) for a single card. Mar 1 19:40:04 - kernel: smc-ultra.c: No SMC Ultra card found (i/o = 0x0). Mar 1 19:40:04 - insmod: Initialization of /tmp/net/smc-ultra.o.B2 failed Mar 1 19:40:04 - insmod: Symbol 'io' not found Mar 1 19:40:04 - insmod: Symbol 'io' not found Mar 1 19:40:04 - kernel: ne.c: No PCI cards found. Use "io=0xNNN" value(s) for ISA cards. Mar 1 19:40:04 - insmod: Initialization of /tmp/prm/ne.o.A2 failed Mar 1 19:40:04 - kernel: ne.c: No PCI cards found. Use "io=0xNNN" value(s) for ISA cards. Mar 1 19:40:04 - insmod: Initialization of /tmp/prm/ne.o.B2 failed Mar 1 19:40:04 - insmod: Cannot open /mnt/router/drv/*.o Mar 1 19:40:04 - insmod: Initialization of /tmp/net/3c509.o.C failed Mar 1 19:40:04 - kernel: 3c59x.c:v0.99H 11/17/98 Donald Becker http://cesdis.gsfc.nasa.gov/linux/drivers/vortex.html Mar 1 19:40:04 - insmod: Initialization of /tmp/net/3c59x.o.C failed Mar 1 19:40:05 - kernel: ne2k-pci.c:v0.99L 2/7/98 D. Becker/P. Gortmaker http://cesdis.gsfc.nasa.gov/linux/drivers/ne2k-pci.html Mar 1 19:40:05 - insmod: Initialization of /tmp/net/ne2k-pci.o.C failed Mar 1 19:40:05 - kernel: rtl8139.c:v1.04 9/22/98 Donald Becker http://cesdis.gsfc.nasa.gov/linux/drivers/rtl8139.html Mar 1 19:40:05 - kernel: eth2: RealTek RTL8139 Fast Ethernet at 0x6200, IRQ 10, 00:30:4f:17:10:54. Mar 1 19:40:05 - kernel: smc-ultra.c: Presently autoprobing (not recommended) for a single card. Mar 1 19:40:05 - kernel: smc-ultra.c: No SMC Ultra card found (i/o = 0x0). Mar 1 19:40:05 - insmod: Initialization of /tmp/net/smc-ultra.o.C failed Mar 1 19:40:05 - insmod: Initialization of /tmp/net/tulip.o.C failed Mar 1 19:40:05 - kernel: ne.c: No PCI cards found. Use "io=0xNNN" value(s) for ISA cards. Mar 1 19:40:05 - insmod: Initialization of /tmp/prm/ne.o.C failed Mar 1 19:40:05 - mode: User 'init' issued 'mode ethernet' Mar 1 19:40:06 - kernel: registered device ppp0 Mar 1 19:40:06 - pppd[133]: pppd 2.3.8 started by root, uid 0 Mar 1 19:40:06 - pppd[133]: Serial connection established. Mar 1 19:40:06 - pppd[133]: Using interface ppp0 Mar 1 19:40:06 - pppd[133]: Connect: ppp0 <--> /dev/ttyp0 Mar 1 19:40:07 - pppoe[140]: PADS: Service-Name: '' Mar 1 19:40:07 - pppoe[140]: PPP session is 4059 Mar 1 19:40:07 - named[169]: starting. named 4.9.3-BETA26 Sun Nov 26 20:58:49 CST 1995 ^Iroot@fuzzy:/tmp/bind-4.9.3-BETA26/named Mar 1 19:40:07 - named[169]: cache zone "" loaded (serial 0) Mar 1 19:40:07 - named[169]: primary zone "net" loaded (serial 1999317) Mar 1 19:40:07 - named[169]: primary zone "10.in-addr.arpa" loaded (serial 1999317) Mar 1 19:40:07 - named[169]: primary zone "16.172.in-addr.arpa" loaded (serial 1999317) Mar 1 19:40:07 - named[169]: primary zone "168.192.in-addr.arpa" loaded (serial 1999317) Mar 1 19:40:07 - named[169]: primary zone "0.0.127.in-addr.arpa" loaded (serial 1999317) Mar 1 19:40:07 - named[170]: Ready to answer queries. Mar 1 19:40:10 - pppd[133]: local IP address 80.50.36.222 Mar 1 19:40:10 - pppd[133]: remote IP address 213.25.2.41 Mar 1 19:40:11 - named[170]: No root nameservers for class IN Mar 01 19:40:13 localhost thttpd[346]: thttpd/2.05 09nov99 starting on port 82 Mar 01 19:40:13 localhost thttpd[346]: started as root without requesting chroot(), warning only Mar 1 15:40:15 - ntpdate[360]: step time server 192.5.16.65 offset -14398.820035 sec Mar 1 19:40:22 - login: ROOT LOGIN ON tty1 Mar 1 19:47:44 - login: ROOT LOGIN ON ttyp1 FROM 192.168.1.2 Mar 1 20:11:03 - pppd[133]: Modem hangup Mar 1 20:11:03 - pppd[133]: Connection terminated. Mar 1 20:11:03 - pppd[133]: Connect time 31.0 minutes. Mar 1 20:11:03 - pppd[133]: Sent 9383626 bytes, received 9749228 bytes. Mar 1 20:11:03 - pppd[133]: Serial connection established. Mar 1 20:11:03 - pppd[133]: Using interface ppp0 Mar 1 20:11:03 - pppd[133]: Connect: ppp0 <--> /dev/ttyp1 Mar 1 20:11:33 - pppd[133]: LCP: timeout sending Config-Requests Mar 1 20:11:33 - pppd[133]: Connection terminated. Mar 1 20:11:38 - pppoe[1163]: Timeout waiting for PADO packets Mar 1 20:11:50 - named[170]: ns_forw: sendto([194.204.159.1].53): Network is unreachable Mar 1 20:12:03 - pppd[133]: Serial connection established. Mar 1 20:12:03 - pppd[133]: Using interface ppp0 Mar 1 20:12:03 - pppd[133]: Connect: ppp0 <--> /dev/ttyp0 Mar 1 20:12:33 - pppd[133]: LCP: timeout sending Config-Requests Mar 1 20:12:33 - pppd[133]: Connection terminated. Mar 1 20:12:38 - pppoe[1191]: Timeout waiting for PADO packets Mar 1 20:13:03 - pppd[133]: Serial connection established. Mar 1 20:13:03 - pppd[133]: Using interface ppp0 Mar 1 20:13:03 - pppd[133]: Connect: ppp0 <--> /dev/ttyp0 Mar 1 20:13:28 - pppoe[1238]: PADS: Service-Name: '' Mar 1 20:13:28 - pppoe[1238]: PPP session is 4413 Mar 1 20:13:31 - pppd[133]: local IP address 80.50.36.222 Mar 1 20:13:31 - pppd[133]: remote IP address 213.25.2.41 Mar 1 20:14:01 - named[170]: sysquery: findns error (3) on A.GTLD-SERVERS.NET? Mar 1 20:14:01 - named[170]: sysquery: findns error (3) on G.GTLD-SERVERS.NET? Mar 1 20:14:01 - named[170]: sysquery: findns error (3) on H.GTLD-SERVERS.NET? Mar 1 20:14:01 - named[170]: sysquery: findns error (3) on C.GTLD-SERVERS.NET? Mar 1 20:14:01 - named[170]: sysquery: findns error (3) on I.GTLD-SERVERS.NET? Mar 1 20:14:01 - named[170]: sysquery: findns error (3) on B.GTLD-SERVERS.NET? Mar 1 20:14:01 - named[170]: sysquery: findns error (3) on D.GTLD-SERVERS.NET? Mar 1 20:14:01 - named[170]: sysquery: findns error (3) on L.GTLD-SERVERS.NET? Mar 1 20:14:01 - named[170]: sysquery: findns error (3) on F.GTLD-SERVERS.NET? Mar 1 20:14:01 - named[170]: sysquery: findns error (3) on J.GTLD-SERVERS.NET? Mar 1 20:14:01 - named[170]: sysquery: findns error (3) on K.GTLD-SERVERS.NET? Mar 1 20:14:01 - named[170]: sysquery: findns error (3) on E.GTLD-SERVERS.NET? Mar 1 20:14:01 - named[170]: sysquery: findns error (3) on M.GTLD-SERVERS.NET? Mar 1 20:15:28 - named[170]: sysquery: findns error (3) on A.GTLD-SERVERS.NET? Mar 1 20:15:28 - named[170]: sysquery: findns error (3) on G.GTLD-SERVERS.NET? Mar 1 20:15:28 - named[170]: sysquery: findns error (3) on H.GTLD-SERVERS.NET? Mar 1 20:15:28 - named[170]: sysquery: findns error (3) on C.GTLD-SERVERS.NET? Mar 1 20:15:28 - named[170]: sysquery: findns error (3) on I.GTLD-SERVERS.NET? Mar 1 20:15:28 - named[170]: sysquery: findns error (3) on B.GTLD-SERVERS.NET? Mar 1 20:15:28 - named[170]: sysquery: findns error (3) on D.GTLD-SERVERS.NET? Mar 1 20:15:28 - named[170]: sysquery: findns error (3) on L.GTLD-SERVERS.NET? Mar 1 20:15:28 - named[170]: sysquery: findns error (3) on F.GTLD-SERVERS.NET? Mar 1 20:15:28 - named[170]: sysquery: findns error (3) on J.GTLD-SERVERS.NET? Mar 1 20:15:28 - named[170]: sysquery: findns error (3) on K.GTLD-SERVERS.NET? Mar 1 20:15:28 - named[170]: sysquery: findns error (3) on E.GTLD-SERVERS.NET? Mar 1 20:15:28 - named[170]: sysquery: findns error (3) on M.GTLD-SERVERS.NET? Mar 1 20:15:30 - named[170]: sysquery: findns error (3) on A.GTLD-SERVERS.NET? Mar 1 20:15:30 - named[170]: sysquery: findns error (3) on G.GTLD-SERVERS.NET? Mar 1 20:15:30 - named[170]: sysquery: findns error (3) on H.GTLD-SERVERS.NET? Mar 1 20:15:30 - named[170]: sysquery: findns error (3) on C.GTLD-SERVERS.NET? Mar 1 20:15:30 - named[170]: sysquery: findns error (3) on I.GTLD-SERVERS.NET? Mar 1 20:15:30 - named[170]: sysquery: findns error (3) on B.GTLD-SERVERS.NET? Mar 1 20:15:30 - named[170]: sysquery: findns error (3) on D.GTLD-SERVERS.NET? Mar 1 20:15:30 - named[170]: sysquery: findns error (3) on L.GTLD-SERVERS.NET? Mar 1 20:15:30 - named[170]: sysquery: findns error (3) on F.GTLD-SERVERS.NET? Mar 1 20:15:30 - named[170]: sysquery: findns error (3) on J.GTLD-SERVERS.NET? Mar 1 20:15:30 - named[170]: sysquery: findns error (3) on K.GTLD-SERVERS.NET? Mar 1 20:15:30 - named[170]: sysquery: findns error (3) on E.GTLD-SERVERS.NET? Mar 1 20:15:30 - named[170]: sysquery: findns error (3) on M.GTLD-SERVERS.NET? Mar 1 20:22:23 - named[170]: sysquery: findns error (3) on A.GTLD-SERVERS.NET? Mar 1 20:22:23 - named[170]: sysquery: findns error (3) on G.GTLD-SERVERS.NET? Mar 1 20:22:23 - named[170]: sysquery: findns error (3) on H.GTLD-SERVERS.NET? Mar 1 20:22:23 - named[170]: sysquery: findns error (3) on C.GTLD-SERVERS.NET? Mar 1 20:22:23 - named[170]: sysquery: findns error (3) on I.GTLD-SERVERS.NET? Mar 1 20:22:23 - named[170]: sysquery: findns error (3) on B.GTLD-SERVERS.NET? Mar 1 20:22:23 - named[170]: sysquery: findns error (3) on D.GTLD-SERVERS.NET? Mar 1 20:22:23 - named[170]: sysquery: findns error (3) on L.GTLD-SERVERS.NET? Mar 1 20:22:23 - named[170]: sysquery: findns error (3) on F.GTLD-SERVERS.NET? Mar 1 20:22:23 - named[170]: sysquery: findns error (3) on J.GTLD-SERVERS.NET? Mar 1 20:22:23 - named[170]: sysquery: findns error (3) on K.GTLD-SERVERS.NET? Mar 1 20:22:23 - named[170]: sysquery: findns error (3) on E.GTLD-SERVERS.NET? Mar 1 20:22:23 - named[170]: sysquery: findns error (3) on M.GTLD-SERVERS.NET? Mar 1 20:25:30 - named[170]: sysquery: findns error (3) on A.GTLD-SERVERS.NET? Mar 1 20:25:30 - named[170]: sysquery: findns error (3) on G.GTLD-SERVERS.NET? Mar 1 20:25:30 - named[170]: sysquery: findns error (3) on H.GTLD-SERVERS.NET? Mar 1 20:25:30 - named[170]: sysquery: findns error (3) on C.GTLD-SERVERS.NET? Mar 1 20:25:30 - named[170]: sysquery: findns error (3) on I.GTLD-SERVERS.NET? Mar 1 20:25:30 - named[170]: sysquery: findns error (3) on B.GTLD-SERVERS.NET? Mar 1 20:25:30 - named[170]: sysquery: findns error (3) on D.GTLD-SERVERS.NET? Mar 1 20:25:30 - named[170]: sysquery: findns error (3) on L.GTLD-SERVERS.NET? Mar 1 20:25:30 - named[170]: sysquery: findns error (3) on F.GTLD-SERVERS.NET? Mar 1 20:25:30 - named[170]: sysquery: findns error (3) on J.GTLD-SERVERS.NET? Mar 1 20:25:30 - named[170]: sysquery: findns error (3) on K.GTLD-SERVERS.NET? Mar 1 20:25:30 - named[170]: sysquery: findns error (3) on E.GTLD-SERVERS.NET? Mar 1 20:25:30 - named[170]: sysquery: findns error (3) on M.GTLD-SERVERS.NET? Mar 1 20:26:19 - kernel: 323 init Mar 1 20:26:29 - kernel: 323 done Mar 1 20:27:31 - named[170]: sysquery: findns error (3) on A.GTLD-SERVERS.NET? Mar 1 20:27:31 - named[170]: sysquery: findns error (3) on G.GTLD-SERVERS.NET? Mar 1 20:27:31 - named[170]: sysquery: findns error (3) on H.GTLD-SERVERS.NET? Mar 1 20:27:31 - named[170]: sysquery: findns error (3) on C.GTLD-SERVERS.NET? Mar 1 20:27:31 - named[170]: sysquery: findns error (3) on I.GTLD-SERVERS.NET? Mar 1 20:27:31 - named[170]: sysquery: findns error (3) on B.GTLD-SERVERS.NET? Mar 1 20:27:31 - named[170]: sysquery: findns error (3) on D.GTLD-SERVERS.NET? Mar 1 20:27:31 - named[170]: sysquery: findns error (3) on L.GTLD-SERVERS.NET? Mar 1 20:27:31 - named[170]: sysquery: findns error (3) on F.GTLD-SERVERS.NET? Mar 1 20:27:31 - named[170]: sysquery: findns error (3) on J.GTLD-SERVERS.NET? Mar 1 20:27:31 - named[170]: sysquery: findns error (3) on K.GTLD-SERVERS.NET? Mar 1 20:27:31 - named[170]: sysquery: findns error (3) on E.GTLD-SERVERS.NET? Mar 1 20:27:31 - named[170]: sysquery: findns error (3) on M.GTLD-SERVERS.NET? Mar 1 20:32:41 - named[170]: sysquery: findns error (3) on A.GTLD-SERVERS.NET? Mar 1 20:32:41 - named[170]: sysquery: findns error (3) on G.GTLD-SERVERS.NET? Mar 1 20:32:41 - named[170]: sysquery: findns error (3) on H.GTLD-SERVERS.NET? Mar 1 20:32:41 - named[170]: sysquery: findns error (3) on C.GTLD-SERVERS.NET? Mar 1 20:32:41 - named[170]: sysquery: findns error (3) on I.GTLD-SERVERS.NET? Mar 1 20:32:41 - named[170]: sysquery: findns error (3) on B.GTLD-SERVERS.NET? Mar 1 20:32:41 - named[170]: sysquery: findns error (3) on D.GTLD-SERVERS.NET? Mar 1 20:32:41 - named[170]: sysquery: findns error (3) on L.GTLD-SERVERS.NET? Mar 1 20:32:41 - named[170]: sysquery: findns error (3) on F.GTLD-SERVERS.NET? Mar 1 20:32:41 - named[170]: sysquery: findns error (3) on J.GTLD-SERVERS.NET? Mar 1 20:32:41 - named[170]: sysquery: findns error (3) on K.GTLD-SERVERS.NET? Mar 1 20:32:41 - named[170]: sysquery: findns error (3) on E.GTLD-SERVERS.NET? Mar 1 20:32:41 - named[170]: sysquery: findns error (3) on M.GTLD-SERVERS.NET? Mar 1 20:39:11 - named[170]: sysquery: findns error (3) on A.GTLD-SERVERS.NET? Mar 1 20:39:11 - named[170]: sysquery: findns error (3) on G.GTLD-SERVERS.NET? Mar 1 20:39:11 - named[170]: sysquery: findns error (3) on H.GTLD-SERVERS.NET? Mar 1 20:39:11 - named[170]: sysquery: findns error (3) on C.GTLD-SERVERS.NET? Mar 1 20:39:11 - named[170]: sysquery: findns error (3) on I.GTLD-SERVERS.NET? Mar 1 20:39:11 - named[170]: sysquery: findns error (3) on B.GTLD-SERVERS.NET? Mar 1 20:39:11 - named[170]: sysquery: findns error (3) on D.GTLD-SERVERS.NET? Mar 1 20:39:11 - named[170]: sysquery: findns error (3) on L.GTLD-SERVERS.NET? Mar 1 20:39:11 - named[170]: sysquery: findns error (3) on F.GTLD-SERVERS.NET? Mar 1 20:39:11 - named[170]: sysquery: findns error (3) on J.GTLD-SERVERS.NET? Mar 1 20:39:11 - named[170]: sysquery: findns error (3) on K.GTLD-SERVERS.NET? Mar 1 20:39:11 - named[170]: sysquery: findns error (3) on E.GTLD-SERVERS.NET? Mar 1 20:39:11 - named[170]: sysquery: findns error (3) on M.GTLD-SERVERS.NET? Mar 1 20:40:07 - named[170]: NSTATS 1046551207 1046547607 A=144 PTR=1 Mar 1 20:40:07 - named[170]: XSTATS 1046551207 1046547607 RQ=145 RR=51 RIQ=0 RNXD=0 RFwdQ=56 RFwdR=50 RDupQ=32 RDupR=0 RFail=0 RFErr=0 RErr=0 RTCP=0 RAXFR=0 RLame=0 ROpts=0 SSysQ=1 SAns=57 SFwdQ=56 SFwdR=50 SDupQ=13 SFail=6 SFErr=0 SErr=7 RNotNsQ=145 SNaAns=42 SNXD=15 Mar 1 20:44:21 - named[170]: sysquery: findns error (3) on A.GTLD-SERVERS.NET? Mar 1 20:44:21 - named[170]: sysquery: findns error (3) on G.GTLD-SERVERS.NET? Mar 1 20:44:21 - named[170]: sysquery: findns error (3) on H.GTLD-SERVERS.NET? Mar 1 20:44:21 - named[170]: sysquery: findns error (3) on C.GTLD-SERVERS.NET? Mar 1 20:44:21 - named[170]: sysquery: findns error (3) on I.GTLD-SERVERS.NET? Mar 1 20:44:21 - named[170]: sysquery: findns error (3) on B.GTLD-SERVERS.NET? Mar 1 20:44:21 - named[170]: sysquery: findns error (3) on D.GTLD-SERVERS.NET? Mar 1 20:44:21 - named[170]: sysquery: findns error (3) on L.GTLD-SERVERS.NET? Mar 1 20:44:21 - named[170]: sysquery: findns error (3) on F.GTLD-SERVERS.NET? Mar 1 20:44:21 - named[170]: sysquery: findns error (3) on J.GTLD-SERVERS.NET? Mar 1 20:44:21 - named[170]: sysquery: findns error (3) on K.GTLD-SERVERS.NET? Mar 1 20:44:21 - named[170]: sysquery: findns error (3) on E.GTLD-SERVERS.NET? Mar 1 20:44:21 - named[170]: sysquery: findns error (3) on M.GTLD-SERVERS.NET? Mar 1 20:45:31 - named[170]: sysquery: findns error (3) on A.GTLD-SERVERS.NET? Mar 1 20:45:31 - named[170]: sysquery: findns error (3) on G.GTLD-SERVERS.NET? Mar 1 20:45:31 - named[170]: sysquery: findns error (3) on H.GTLD-SERVERS.NET? Mar 1 20:45:31 - named[170]: sysquery: findns error (3) on C.GTLD-SERVERS.NET? Mar 1 20:45:31 - named[170]: sysquery: findns error (3) on I.GTLD-SERVERS.NET? Mar 1 20:45:31 - named[170]: sysquery: findns error (3) on B.GTLD-SERVERS.NET? Mar 1 20:45:31 - named[170]: sysquery: findns error (3) on D.GTLD-SERVERS.NET? Mar 1 20:45:31 - named[170]: sysquery: findns error (3) on L.GTLD-SERVERS.NET? Mar 1 20:45:31 - named[170]: sysquery: findns error (3) on F.GTLD-SERVERS.NET? Mar 1 20:45:31 - named[170]: sysquery: findns error (3) on J.GTLD-SERVERS.NET? Mar 1 20:45:31 - named[170]: sysquery: findns error (3) on K.GTLD-SERVERS.NET? Mar 1 20:45:31 - named[170]: sysquery: findns error (3) on E.GTLD-SERVERS.NET? Mar 1 20:45:31 - named[170]: sysquery: findns error (3) on M.GTLD-SERVERS.NET? Mar 1 20:45:31 - named[170]: sysquery: findns error (3) on A.GTLD-SERVERS.NET? Mar 1 20:45:31 - named[170]: sysquery: findns error (3) on G.GTLD-SERVERS.NET? Mar 1 20:45:31 - named[170]: sysquery: findns error (3) on H.GTLD-SERVERS.NET? Mar 1 20:45:31 - named[170]: sysquery: findns error (3) on C.GTLD-SERVERS.NET? Mar 1 20:45:31 - named[170]: sysquery: findns error (3) on I.GTLD-SERVERS.NET? Mar 1 20:45:31 - named[170]: sysquery: findns error (3) on B.GTLD-SERVERS.NET? Mar 1 20:45:31 - named[170]: sysquery: findns error (3) on D.GTLD-SERVERS.NET? Mar 1 20:45:31 - named[170]: sysquery: findns error (3) on L.GTLD-SERVERS.NET? Mar 1 20:45:31 - named[170]: sysquery: findns error (3) on F.GTLD-SERVERS.NET? Mar 1 20:45:31 - named[170]: sysquery: findns error (3) on J.GTLD-SERVERS.NET? Mar 1 20:45:31 - named[170]: sysquery: findns error (3) on K.GTLD-SERVERS.NET? Mar 1 20:45:31 - named[170]: sysquery: findns error (3) on E.GTLD-SERVERS.NET? Mar 1 20:45:31 - named[170]: sysquery: findns error (3) on M.GTLD-SERVERS.NET? Mar 1 20:53:32 - named[170]: sysquery: findns error (3) on A.GTLD-SERVERS.NET? Mar 1 20:53:32 - named[170]: sysquery: findns error (3) on G.GTLD-SERVERS.NET? Mar 1 20:53:32 - named[170]: sysquery: findns error (3) on H.GTLD-SERVERS.NET? Mar 1 20:53:32 - named[170]: sysquery: findns error (3) on C.GTLD-SERVERS.NET? Mar 1 20:53:32 - named[170]: sysquery: findns error (3) on I.GTLD-SERVERS.NET? Mar 1 20:53:32 - named[170]: sysquery: findns error (3) on B.GTLD-SERVERS.NET? Mar 1 20:53:32 - named[170]: sysquery: findns error (3) on D.GTLD-SERVERS.NET? Mar 1 20:53:32 - named[170]: sysquery: findns error (3) on L.GTLD-SERVERS.NET? Mar 1 20:53:32 - named[170]: sysquery: findns error (3) on F.GTLD-SERVERS.NET? Mar 1 20:53:32 - named[170]: sysquery: findns error (3) on J.GTLD-SERVERS.NET? Mar 1 20:53:32 - named[170]: sysquery: findns error (3) on K.GTLD-SERVERS.NET? Mar 1 20:53:32 - named[170]: sysquery: findns error (3) on E.GTLD-SERVERS.NET? Mar 1 20:53:32 - named[170]: sysquery: findns error (3) on M.GTLD-SERVERS.NET? Mar 1 20:53:41 - named[170]: sysquery: findns error (3) on A.GTLD-SERVERS.NET? Mar 1 20:53:41 - named[170]: sysquery: findns error (3) on G.GTLD-SERVERS.NET? Mar 1 20:53:41 - named[170]: sysquery: findns error (3) on H.GTLD-SERVERS.NET? Mar 1 20:53:41 - named[170]: sysquery: findns error (3) on C.GTLD-SERVERS.NET? Mar 1 20:53:41 - named[170]: sysquery: findns error (3) on I.GTLD-SERVERS.NET? Mar 1 20:53:41 - named[170]: sysquery: findns error (3) on B.GTLD-SERVERS.NET? Mar 1 20:53:41 - named[170]: sysquery: findns error (3) on D.GTLD-SERVERS.NET? Mar 1 20:53:41 - named[170]: sysquery: findns error (3) on L.GTLD-SERVERS.NET? Mar 1 20:53:41 - named[170]: sysquery: findns error (3) on F.GTLD-SERVERS.NET? Mar 1 20:53:41 - named[170]: sysquery: findns error (3) on J.GTLD-SERVERS.NET? Mar 1 20:53:41 - named[170]: sysquery: findns error (3) on K.GTLD-SERVERS.NET? Mar 1 20:53:41 - named[170]: sysquery: findns error (3) on E.GTLD-SERVERS.NET? Mar 1 20:53:41 - named[170]: sysquery: findns error (3) on M.GTLD-SERVERS.NET? Mar 1 20:54:35 - kernel: floppy0: disk absent or changed during operation Mar 1 20:54:35 - kernel: end_request: I/O error, dev 02:00, sector 17 Mar 1 20:54:35 - kernel: floppy0: disk absent or changed during operation Mar 1 20:54:35 - kernel: end_request: I/O error, dev 02:00, sector 2 Mar 1 20:54:35 - kernel: 2nd bread in fat_access failed Mar 1 20:54:35 - kernel: floppy0: disk absent or changed during operation Mar 1 20:54:35 - kernel: end_request: I/O error, dev 02:00, sector 2 Mar 1 20:54:35 - kernel: 2nd bread in fat_access failed Mar 1 20:54:59 - kernel: floppy0: disk absent or changed during operation Mar 1 20:54:59 - kernel: end_request: I/O error, dev 02:00, sector 2 Mar 1 20:54:59 - kernel: 2nd bread in fat_access failed Mar 1 20:54:59 - kernel: Filesystem panic (dev 02:00, mounted on 01:00:162) Mar 1 20:54:59 - kernel: fat_free: deleting beyond EOF Mar 1 20:54:59 - kernel: File system has been set read-only Mar 1 20:54:59 - kernel: floppy0: disk absent or changed during operation Mar 1 20:54:59 - kernel: end_request: I/O error, dev 02:00, sector 2 Mar 1 20:54:59 - kernel: bread in fat_access failed Mar 1 20:54:59 - kernel: floppy0: disk absent or changed during operation Mar 1 20:54:59 - kernel: end_request: I/O error, dev 02:00, sector 2 Mar 1 20:54:59 - kernel: bread in fat_access failed Mar 1 20:54:59 - kernel: file_cluster badly computed!!! 0 <> 1 Mar 1 20:55:31 - named[170]: sysquery: findns error (3) on A.GTLD-SERVERS.NET? Mar 1 20:55:31 - named[170]: sysquery: findns error (3) on G.GTLD-SERVERS.NET? Mar 1 20:55:31 - named[170]: sysquery: findns error (3) on H.GTLD-SERVERS.NET? Mar 1 20:55:31 - named[170]: sysquery: findns error (3) on C.GTLD-SERVERS.NET? Mar 1 20:55:31 - named[170]: sysquery: findns error (3) on I.GTLD-SERVERS.NET? Mar 1 20:55:31 - named[170]: sysquery: findns error (3) on B.GTLD-SERVERS.NET? Mar 1 20:55:31 - named[170]: sysquery: findns error (3) on D.GTLD-SERVERS.NET? Mar 1 20:55:31 - named[170]: sysquery: findns error (3) on L.GTLD-SERVERS.NET? Mar 1 20:55:31 - named[170]: sysquery: findns error (3) on F.GTLD-SERVERS.NET? Mar 1 20:55:31 - named[170]: sysquery: findns error (3) on J.GTLD-SERVERS.NET? Mar 1 20:55:31 - named[170]: sysquery: findns error (3) on K.GTLD-SERVERS.NET? Mar 1 20:55:31 - named[170]: sysquery: findns error (3) on E.GTLD-SERVERS.NET? Mar 1 20:55:31 - named[170]: sysquery: findns error (3) on M.GTLD-SERVERS.NET? Mar 1 20:58:51 - named[170]: sysquery: findns error (3) on A.GTLD-SERVERS.NET? Mar 1 20:58:51 - named[170]: sysquery: findns error (3) on G.GTLD-SERVERS.NET? Mar 1 20:58:51 - named[170]: sysquery: findns error (3) on H.GTLD-SERVERS.NET? Mar 1 20:58:51 - named[170]: sysquery: findns error (3) on C.GTLD-SERVERS.NET? Mar 1 20:58:51 - named[170]: sysquery: findns error (3) on I.GTLD-SERVERS.NET? Mar 1 20:58:51 - named[170]: sysquery: findns error (3) on B.GTLD-SERVERS.NET? Mar 1 20:58:51 - named[170]: sysquery: findns error (3) on D.GTLD-SERVERS.NET? Mar 1 20:58:51 - named[170]: sysquery: findns error (3) on L.GTLD-SERVERS.NET? Mar 1 20:58:51 - named[170]: sysquery: findns error (3) on F.GTLD-SERVERS.NET? Mar 1 20:58:51 - named[170]: sysquery: findns error (3) on J.GTLD-SERVERS.NET? Mar 1 20:58:51 - named[170]: sysquery: findns error (3) on K.GTLD-SERVERS.NET? Mar 1 20:58:51 - named[170]: sysquery: findns error (3) on E.GTLD-SERVERS.NET? Mar 1 20:58:51 - named[170]: sysquery: findns error (3) on M.GTLD-SERVERS.NET? Mar 1 21:01:06 - named[170]: sysquery: findns error (3) on A.GTLD-SERVERS.NET? Mar 1 21:01:06 - named[170]: sysquery: findns error (3) on G.GTLD-SERVERS.NET? Mar 1 21:01:06 - named[170]: sysquery: findns error (3) on H.GTLD-SERVERS.NET? Mar 1 21:01:06 - named[170]: sysquery: findns error (3) on C.GTLD-SERVERS.NET? Mar 1 21:01:06 - named[170]: sysquery: findns error (3) on I.GTLD-SERVERS.NET? Mar 1 21:01:06 - named[170]: sysquery: findns error (3) on B.GTLD-SERVERS.NET? Mar 1 21:01:06 - named[170]: sysquery: findns error (3) on D.GTLD-SERVERS.NET? Mar 1 21:01:06 - named[170]: sysquery: findns error (3) on L.GTLD-SERVERS.NET? Mar 1 21:01:06 - named[170]: sysquery: findns error (3) on F.GTLD-SERVERS.NET? Mar 1 21:01:06 - named[170]: sysquery: findns error (3) on J.GTLD-SERVERS.NET? Mar 1 21:01:06 - named[170]: sysquery: findns error (3) on K.GTLD-SERVERS.NET? Mar 1 21:01:06 - named[170]: sysquery: findns error (3) on E.GTLD-SERVERS.NET? Mar 1 21:01:06 - named[170]: sysquery: findns error (3) on M.GTLD-SERVERS.NET? Mar 1 21:15:30 - named[170]: sysquery: findns error (3) on A.GTLD-SERVERS.NET? Mar 1 21:15:30 - named[170]: sysquery: findns error (3) on G.GTLD-SERVERS.NET? Mar 1 21:15:30 - named[170]: sysquery: findns error (3) on H.GTLD-SERVERS.NET? Mar 1 21:15:30 - named[170]: sysquery: findns error (3) on C.GTLD-SERVERS.NET? Mar 1 21:15:30 - named[170]: sysquery: findns error (3) on I.GTLD-SERVERS.NET? Mar 1 21:15:30 - named[170]: sysquery: findns error (3) on B.GTLD-SERVERS.NET? Mar 1 21:15:30 - named[170]: sysquery: findns error (3) on D.GTLD-SERVERS.NET? Mar 1 21:15:30 - named[170]: sysquery: findns error (3) on L.GTLD-SERVERS.NET? Mar 1 21:15:30 - named[170]: sysquery: findns error (3) on F.GTLD-SERVERS.NET? Mar 1 21:15:30 - named[170]: sysquery: findns error (3) on J.GTLD-SERVERS.NET? Mar 1 21:15:30 - named[170]: sysquery: findns error (3) on K.GTLD-SERVERS.NET? Mar 1 21:15:30 - named[170]: sysquery: findns error (3) on E.GTLD-SERVERS.NET? Mar 1 21:15:30 - named[170]: sysquery: findns error (3) on M.GTLD-SERVERS.NET? Mar 1 21:15:33 - named[170]: sysquery: findns error (3) on A.GTLD-SERVERS.NET? Mar 1 21:15:33 - named[170]: sysquery: findns error (3) on G.GTLD-SERVERS.NET? Mar 1 21:15:33 - named[170]: sysquery: findns error (3) on H.GTLD-SERVERS.NET? Mar 1 21:15:33 - named[170]: sysquery: findns error (3) on C.GTLD-SERVERS.NET? Mar 1 21:15:33 - named[170]: sysquery: findns error (3) on I.GTLD-SERVERS.NET? Mar 1 21:15:33 - named[170]: sysquery: findns error (3) on B.GTLD-SERVERS.NET? Mar 1 21:15:33 - named[170]: sysquery: findns error (3) on D.GTLD-SERVERS.NET? Mar 1 21:15:33 - named[170]: sysquery: findns error (3) on L.GTLD-SERVERS.NET? Mar 1 21:15:33 - named[170]: sysquery: findns error (3) on F.GTLD-SERVERS.NET? Mar 1 21:15:33 - named[170]: sysquery: findns error (3) on J.GTLD-SERVERS.NET? Mar 1 21:15:33 - named[170]: sysquery: findns error (3) on K.GTLD-SERVERS.NET? Mar 1 21:15:33 - named[170]: sysquery: findns error (3) on E.GTLD-SERVERS.NET? Mar 1 21:15:33 - named[170]: sysquery: findns error (3) on M.GTLD-SERVERS.NET? Mar 1 21:15:51 - named[170]: sysquery: findns error (3) on A.GTLD-SERVERS.NET? Mar 1 21:15:51 - named[170]: sysquery: findns error (3) on G.GTLD-SERVERS.NET? Mar 1 21:15:51 - named[170]: sysquery: findns error (3) on H.GTLD-SERVERS.NET? Mar 1 21:15:51 - named[170]: sysquery: findns error (3) on C.GTLD-SERVERS.NET? Mar 1 21:15:51 - named[170]: sysquery: findns error (3) on I.GTLD-SERVERS.NET? Mar 1 21:15:51 - named[170]: sysquery: findns error (3) on B.GTLD-SERVERS.NET? Mar 1 21:15:51 - named[170]: sysquery: findns error (3) on D.GTLD-SERVERS.NET? Mar 1 21:15:51 - named[170]: sysquery: findns error (3) on L.GTLD-SERVERS.NET? Mar 1 21:15:51 - named[170]: sysquery: findns error (3) on F.GTLD-SERVERS.NET? Mar 1 21:15:51 - named[170]: sysquery: findns error (3) on J.GTLD-SERVERS.NET? Mar 1 21:15:51 - named[170]: sysquery: findns error (3) on K.GTLD-SERVERS.NET? Mar 1 21:15:51 - named[170]: sysquery: findns error (3) on E.GTLD-SERVERS.NET? Mar 1 21:15:51 - named[170]: sysquery: findns error (3) on M.GTLD-SERVERS.NET? Mar 1 21:35:03 - named[170]: sysquery: findns error (3) on A.GTLD-SERVERS.NET? Mar 1 21:35:03 - named[170]: sysquery: findns error (3) on G.GTLD-SERVERS.NET? Mar 1 21:35:03 - named[170]: sysquery: findns error (3) on H.GTLD-SERVERS.NET? Mar 1 21:35:03 - named[170]: sysquery: findns error (3) on C.GTLD-SERVERS.NET? Mar 1 21:35:03 - named[170]: sysquery: findns error (3) on I.GTLD-SERVERS.NET? Mar 1 21:35:03 - named[170]: sysquery: findns error (3) on B.GTLD-SERVERS.NET? Mar 1 21:35:03 - named[170]: sysquery: findns error (3) on D.GTLD-SERVERS.NET? Mar 1 21:35:03 - named[170]: sysquery: findns error (3) on L.GTLD-SERVERS.NET? Mar 1 21:35:03 - named[170]: sysquery: findns error (3) on F.GTLD-SERVERS.NET? Mar 1 21:35:03 - named[170]: sysquery: findns error (3) on J.GTLD-SERVERS.NET? Mar 1 21:35:03 - named[170]: sysquery: findns error (3) on K.GTLD-SERVERS.NET? Mar 1 21:35:03 - named[170]: sysquery: findns error (3) on E.GTLD-SERVERS.NET? Mar 1 21:35:03 - named[170]: sysquery: findns error (3) on M.GTLD-SERVERS.NET? Mar 1 21:35:34 - named[170]: sysquery: findns error (3) on A.GTLD-SERVERS.NET? Mar 1 21:35:34 - named[170]: sysquery: findns error (3) on G.GTLD-SERVERS.NET? Mar 1 21:35:34 - named[170]: sysquery: findns error (3) on H.GTLD-SERVERS.NET? Mar 1 21:35:34 - named[170]: sysquery: findns error (3) on C.GTLD-SERVERS.NET? Mar 1 21:35:34 - named[170]: sysquery: findns error (3) on I.GTLD-SERVERS.NET? Mar 1 21:35:34 - named[170]: sysquery: findns error (3) on B.GTLD-SERVERS.NET? Mar 1 21:35:34 - named[170]: sysquery: findns error (3) on D.GTLD-SERVERS.NET? Mar 1 21:35:34 - named[170]: sysquery: findns error (3) on L.GTLD-SERVERS.NET? Mar 1 21:35:34 - named[170]: sysquery: findns error (3) on F.GTLD-SERVERS.NET? Mar 1 21:35:34 - named[170]: sysquery: findns error (3) on J.GTLD-SERVERS.NET? Mar 1 21:35:34 - named[170]: sysquery: findns error (3) on K.GTLD-SERVERS.NET? Mar 1 21:35:34 - named[170]: sysquery: findns error (3) on E.GTLD-SERVERS.NET? Mar 1 21:35:34 - named[170]: sysquery: findns error (3) on M.GTLD-SERVERS.NET? Mar 1 21:35:35 - named[170]: sysquery: findns error (3) on A.GTLD-SERVERS.NET? Mar 1 21:35:35 - named[170]: sysquery: findns error (3) on G.GTLD-SERVERS.NET? Mar 1 21:35:35 - named[170]: sysquery: findns error (3) on H.GTLD-SERVERS.NET? Mar 1 21:35:35 - named[170]: sysquery: findns error (3) on C.GTLD-SERVERS.NET? Mar 1 21:35:35 - named[170]: sysquery: findns error (3) on I.GTLD-SERVERS.NET? Mar 1 21:35:35 - named[170]: sysquery: findns error (3) on B.GTLD-SERVERS.NET? Mar 1 21:35:35 - named[170]: sysquery: findns error (3) on D.GTLD-SERVERS.NET? Mar 1 21:35:35 - named[170]: sysquery: findns error (3) on L.GTLD-SERVERS.NET? Mar 1 21:35:35 - named[170]: sysquery: findns error (3) on F.GTLD-SERVERS.NET? Mar 1 21:35:35 - named[170]: sysquery: findns error (3) on J.GTLD-SERVERS.NET? Mar 1 21:35:35 - named[170]: sysquery: findns error (3) on K.GTLD-SERVERS.NET? Mar 1 21:35:35 - named[170]: sysquery: findns error (3) on E.GTLD-SERVERS.NET? Mar 1 21:35:35 - named[170]: sysquery: findns error (3) on M.GTLD-SERVERS.NET? Mar 1 21:38:13 - named[170]: sysquery: findns error (3) on A.GTLD-SERVERS.NET? Mar 1 21:38:13 - named[170]: sysquery: findns error (3) on G.GTLD-SERVERS.NET? Mar 1 21:38:13 - named[170]: sysquery: findns error (3) on H.GTLD-SERVERS.NET? Mar 1 21:38:13 - named[170]: sysquery: findns error (3) on C.GTLD-SERVERS.NET? Mar 1 21:38:13 - named[170]: sysquery: findns error (3) on I.GTLD-SERVERS.NET? Mar 1 21:38:13 - named[170]: sysquery: findns error (3) on B.GTLD-SERVERS.NET? Mar 1 21:38:13 - named[170]: sysquery: findns error (3) on D.GTLD-SERVERS.NET? Mar 1 21:38:13 - named[170]: sysquery: findns error (3) on L.GTLD-SERVERS.NET? Mar 1 21:38:13 - named[170]: sysquery: findns error (3) on F.GTLD-SERVERS.NET? Mar 1 21:38:13 - named[170]: sysquery: findns error (3) on J.GTLD-SERVERS.NET? Mar 1 21:38:13 - named[170]: sysquery: findns error (3) on K.GTLD-SERVERS.NET? Mar 1 21:38:13 - named[170]: sysquery: findns error (3) on E.GTLD-SERVERS.NET? Mar 1 21:38:13 - named[170]: sysquery: findns error (3) on M.GTLD-SERVERS.NET? Mar 1 21:40:07 - named[170]: NSTATS 1046554807 1046547607 A=219 PTR=1 Mar 1 21:40:07 - named[170]: XSTATS 1046554807 1046547607 RQ=220 RR=94 RIQ=0 RNXD=0 RFwdQ=98 RFwdR=92 RDupQ=41 RDupR=0 RFail=0 RFErr=0 RErr=0 RTCP=0 RAXFR=0 RLame=0 ROpts=0 SSysQ=2 SAns=81 SFwdQ=98 SFwdR=92 SDupQ=13 SFail=6 SFErr=0 SErr=7 RNotNsQ=220 SNaAns=65 SNXD=15 Mar 1 21:40:12 - named[170]: sysquery: findns error (3) on A.GTLD-SERVERS.NET? Mar 1 21:40:12 - named[170]: sysquery: findns error (3) on G.GTLD-SERVERS.NET? Mar 1 21:40:12 - named[170]: sysquery: findns error (3) on H.GTLD-SERVERS.NET? Mar 1 21:40:12 - named[170]: sysquery: findns error (3) on C.GTLD-SERVERS.NET? Mar 1 21:40:12 - named[170]: sysquery: findns error (3) on I.GTLD-SERVERS.NET? Mar 1 21:40:12 - named[170]: sysquery: findns error (3) on B.GTLD-SERVERS.NET? Mar 1 21:40:12 - named[170]: sysquery: findns error (3) on D.GTLD-SERVERS.NET? Mar 1 21:40:12 - named[170]: sysquery: findns error (3) on L.GTLD-SERVERS.NET? Mar 1 21:40:12 - named[170]: sysquery: findns error (3) on F.GTLD-SERVERS.NET? Mar 1 21:40:12 - named[170]: sysquery: findns error (3) on J.GTLD-SERVERS.NET? Mar 1 21:40:12 - named[170]: sysquery: findns error (3) on K.GTLD-SERVERS.NET? Mar 1 21:40:12 - named[170]: sysquery: findns error (3) on E.GTLD-SERVERS.NET? Mar 1 21:40:12 - named[170]: sysquery: findns error (3) on M.GTLD-SERVERS.NET? Mar 1 21:40:32 - named[170]: sysquery: findns error (3) on A.GTLD-SERVERS.NET? Mar 1 21:40:32 - named[170]: sysquery: findns error (3) on G.GTLD-SERVERS.NET? Mar 1 21:40:32 - named[170]: sysquery: findns error (3) on H.GTLD-SERVERS.NET? Mar 1 21:40:32 - named[170]: sysquery: findns error (3) on C.GTLD-SERVERS.NET? Mar 1 21:40:32 - named[170]: sysquery: findns error (3) on I.GTLD-SERVERS.NET? Mar 1 21:40:32 - named[170]: sysquery: findns error (3) on B.GTLD-SERVERS.NET? Mar 1 21:40:32 - named[170]: sysquery: findns error (3) on D.GTLD-SERVERS.NET? Mar 1 21:40:32 - named[170]: sysquery: findns error (3) on L.GTLD-SERVERS.NET? Mar 1 21:40:32 - named[170]: sysquery: findns error (3) on F.GTLD-SERVERS.NET? Mar 1 21:40:32 - named[170]: sysquery: findns error (3) on J.GTLD-SERVERS.NET? Mar 1 21:40:32 - named[170]: sysquery: findns error (3) on K.GTLD-SERVERS.NET? Mar 1 21:40:32 - named[170]: sysquery: findns error (3) on E.GTLD-SERVERS.NET? Mar 1 21:40:32 - named[170]: sysquery: findns error (3) on M.GTLD-SERVERS.NET? Mar 1 21:45:32 - named[170]: sysquery: findns error (2) on muwaya.ucs.unimelb.edu.au? Mar 1 21:45:32 - named[170]: sysquery: findns error (2) on munnari.oz.au? Mar 1 21:45:43 - named[170]: sysquery: findns error (3) on A.GTLD-SERVERS.NET? Mar 1 21:45:43 - named[170]: sysquery: findns error (3) on G.GTLD-SERVERS.NET? Mar 1 21:45:43 - named[170]: sysquery: findns error (3) on H.GTLD-SERVERS.NET? Mar 1 21:45:43 - named[170]: sysquery: findns error (3) on C.GTLD-SERVERS.NET? Mar 1 21:45:43 - named[170]: sysquery: findns error (3) on I.GTLD-SERVERS.NET? Mar 1 21:45:43 - named[170]: sysquery: findns error (3) on B.GTLD-SERVERS.NET? Mar 1 21:45:43 - named[170]: sysquery: findns error (3) on D.GTLD-SERVERS.NET? Mar 1 21:45:43 - named[170]: sysquery: findns error (3) on L.GTLD-SERVERS.NET? Mar 1 21:45:43 - named[170]: sysquery: findns error (3) on F.GTLD-SERVERS.NET? Mar 1 21:45:43 - named[170]: sysquery: findns error (3) on J.GTLD-SERVERS.NET? Mar 1 21:45:43 - named[170]: sysquery: findns error (3) on K.GTLD-SERVERS.NET? Mar 1 21:45:43 - named[170]: sysquery: findns error (3) on E.GTLD-SERVERS.NET? Mar 1 21:45:43 - named[170]: sysquery: findns error (3) on M.GTLD-SERVERS.NET? Mar 1 21:45:52 - named[170]: sysquery: findns error (3) on A.GTLD-SERVERS.NET? Mar 1 21:45:52 - named[170]: sysquery: findns error (3) on G.GTLD-SERVERS.NET? Mar 1 21:45:52 - named[170]: sysquery: findns error (3) on H.GTLD-SERVERS.NET? Mar 1 21:45:52 - named[170]: sysquery: findns error (3) on C.GTLD-SERVERS.NET? Mar 1 21:45:52 - named[170]: sysquery: findns error (3) on I.GTLD-SERVERS.NET? Mar 1 21:45:52 - named[170]: sysquery: findns error (3) on B.GTLD-SERVERS.NET? Mar 1 21:45:52 - named[170]: sysquery: findns error (3) on D.GTLD-SERVERS.NET? Mar 1 21:45:52 - named[170]: sysquery: findns error (3) on L.GTLD-SERVERS.NET? Mar 1 21:45:52 - named[170]: sysquery: findns error (3) on F.GTLD-SERVERS.NET? Mar 1 21:45:52 - named[170]: sysquery: findns error (3) on J.GTLD-SERVERS.NET? Mar 1 21:45:52 - named[170]: sysquery: findns error (3) on K.GTLD-SERVERS.NET? Mar 1 21:45:52 - named[170]: sysquery: findns error (3) on E.GTLD-SERVERS.NET? Mar 1 21:45:52 - named[170]: sysquery: findns error (3) on M.GTLD-SERVERS.NET? Mar 1 21:54:52 - named[170]: sysquery: findns error (3) on A.GTLD-SERVERS.NET? Mar 1 21:54:52 - named[170]: sysquery: findns error (3) on G.GTLD-SERVERS.NET? Mar 1 21:54:52 - named[170]: sysquery: findns error (3) on H.GTLD-SERVERS.NET? Mar 1 21:54:52 - named[170]: sysquery: findns error (3) on C.GTLD-SERVERS.NET? Mar 1 21:54:52 - named[170]: sysquery: findns error (3) on I.GTLD-SERVERS.NET? Mar 1 21:54:52 - named[170]: sysquery: findns error (3) on B.GTLD-SERVERS.NET? Mar 1 21:54:52 - named[170]: sysquery: findns error (3) on D.GTLD-SERVERS.NET? Mar 1 21:54:52 - named[170]: sysquery: findns error (3) on L.GTLD-SERVERS.NET? Mar 1 21:54:52 - named[170]: sysquery: findns error (3) on F.GTLD-SERVERS.NET? Mar 1 21:54:52 - named[170]: sysquery: findns error (3) on J.GTLD-SERVERS.NET? Mar 1 21:54:52 - named[170]: sysquery: findns error (3) on K.GTLD-SERVERS.NET? Mar 1 21:54:52 - named[170]: sysquery: findns error (3) on E.GTLD-SERVERS.NET? Mar 1 21:54:52 - named[170]: sysquery: findns error (3) on M.GTLD-SERVERS.NET? Mar 1 21:55:52 - named[170]: sysquery: findns error (3) on A.GTLD-SERVERS.NET? Mar 1 21:55:52 - named[170]: sysquery: findns error (3) on G.GTLD-SERVERS.NET? Mar 1 21:55:52 - named[170]: sysquery: findns error (3) on H.GTLD-SERVERS.NET? Mar 1 21:55:52 - named[170]: sysquery: findns error (3) on C.GTLD-SERVERS.NET? Mar 1 21:55:52 - named[170]: sysquery: findns error (3) on I.GTLD-SERVERS.NET? Mar 1 21:55:52 - named[170]: sysquery: findns error (3) on B.GTLD-SERVERS.NET? Mar 1 21:55:52 - named[170]: sysquery: findns error (3) on D.GTLD-SERVERS.NET? Mar 1 21:55:52 - named[170]: sysquery: findns error (3) on L.GTLD-SERVERS.NET? Mar 1 21:55:52 - named[170]: sysquery: findns error (3) on F.GTLD-SERVERS.NET? Mar 1 21:55:52 - named[170]: sysquery: findns error (3) on J.GTLD-SERVERS.NET? Mar 1 21:55:52 - named[170]: sysquery: findns error (3) on K.GTLD-SERVERS.NET? Mar 1 21:55:52 - named[170]: sysquery: findns error (3) on E.GTLD-SERVERS.NET? Mar 1 21:55:52 - named[170]: sysquery: findns error (3) on M.GTLD-SERVERS.NET? Mar 1 21:56:49 - kernel: 323 init Mar 1 21:57:01 - kernel: 323 done Mar 1 22:00:02 - named[170]: sysquery: findns error (3) on A.GTLD-SERVERS.NET? Mar 1 22:00:02 - named[170]: sysquery: findns error (3) on G.GTLD-SERVERS.NET? Mar 1 22:00:02 - named[170]: sysquery: findns error (3) on H.GTLD-SERVERS.NET? Mar 1 22:00:02 - named[170]: sysquery: findns error (3) on C.GTLD-SERVERS.NET? Mar 1 22:00:02 - named[170]: sysquery: findns error (3) on I.GTLD-SERVERS.NET? Mar 1 22:00:02 - named[170]: sysquery: findns error (3) on B.GTLD-SERVERS.NET? Mar 1 22:00:02 - named[170]: sysquery: findns error (3) on D.GTLD-SERVERS.NET? Mar 1 22:00:02 - named[170]: sysquery: findns error (3) on L.GTLD-SERVERS.NET? Mar 1 22:00:02 - named[170]: sysquery: findns error (3) on F.GTLD-SERVERS.NET? Mar 1 22:00:02 - named[170]: sysquery: findns error (3) on J.GTLD-SERVERS.NET? Mar 1 22:00:02 - named[170]: sysquery: findns error (3) on K.GTLD-SERVERS.NET? Mar 1 22:00:02 - named[170]: sysquery: findns error (3) on E.GTLD-SERVERS.NET? Mar 1 22:00:02 - named[170]: sysquery: findns error (3) on M.GTLD-SERVERS.NET? Mar 1 22:03:46 - named[170]: sysquery: findns error (3) on dns.astercity.net? Mar 1 22:03:47 - named[170]: sysquery: findns error (3) on dns.astercity.net? Mar 1 22:03:47 - named[170]: sysquery: findns error (2) on ns1.ikp.pl? Mar 1 22:03:48 - named[170]: sysquery: findns error (3) on dns.astercity.net? Mar 1 22:03:48 - named[170]: sysquery: findns error (2) on ns1.ikp.pl? Mar 1 22:05:00 - named[170]: sysquery: findns error (3) on dns.astercity.net? Mar 1 22:05:12 - named[170]: sysquery: findns error (3) on A.GTLD-SERVERS.NET? Mar 1 22:05:12 - named[170]: sysquery: findns error (3) on G.GTLD-SERVERS.NET? Mar 1 22:05:12 - named[170]: sysquery: findns error (3) on H.GTLD-SERVERS.NET? Mar 1 22:05:12 - named[170]: sysquery: findns error (3) on C.GTLD-SERVERS.NET? Mar 1 22:05:12 - named[170]: sysquery: findns error (3) on I.GTLD-SERVERS.NET? Mar 1 22:05:12 - named[170]: sysquery: findns error (3) on B.GTLD-SERVERS.NET? Mar 1 22:05:12 - named[170]: sysquery: findns error (3) on D.GTLD-SERVERS.NET? Mar 1 22:05:12 - named[170]: sysquery: findns error (3) on L.GTLD-SERVERS.NET? Mar 1 22:05:12 - named[170]: sysquery: findns error (3) on F.GTLD-SERVERS.NET? Mar 1 22:05:12 - named[170]: sysquery: findns error (3) on J.GTLD-SERVERS.NET? Mar 1 22:05:12 - named[170]: sysquery: findns error (3) on K.GTLD-SERVERS.NET? Mar 1 22:05:12 - named[170]: sysquery: findns error (3) on E.GTLD-SERVERS.NET? Mar 1 22:05:12 - named[170]: sysquery: findns error (3) on M.GTLD-SERVERS.NET? Mar 1 22:05:33 - named[170]: sysquery: findns error (3) on A.GTLD-SERVERS.NET? Mar 1 22:05:33 - named[170]: sysquery: findns error (3) on G.GTLD-SERVERS.NET? Mar 1 22:05:33 - named[170]: sysquery: findns error (3) on H.GTLD-SERVERS.NET? Mar 1 22:05:33 - named[170]: sysquery: findns error (3) on C.GTLD-SERVERS.NET? Mar 1 22:05:33 - named[170]: sysquery: findns error (3) on I.GTLD-SERVERS.NET? Mar 1 22:05:33 - named[170]: sysquery: findns error (3) on B.GTLD-SERVERS.NET? Mar 1 22:05:33 - named[170]: sysquery: findns error (3) on D.GTLD-SERVERS.NET? Mar 1 22:05:33 - named[170]: sysquery: findns error (3) on L.GTLD-SERVERS.NET? Mar 1 22:05:33 - named[170]: sysquery: findns error (3) on F.GTLD-SERVERS.NET? Mar 1 22:05:33 - named[170]: sysquery: findns error (3) on J.GTLD-SERVERS.NET? Mar 1 22:05:33 - named[170]: sysquery: findns error (3) on K.GTLD-SERVERS.NET? Mar 1 22:05:33 - named[170]: sysquery: findns error (3) on E.GTLD-SERVERS.NET? Mar 1 22:05:33 - named[170]: sysquery: findns error (3) on M.GTLD-SERVERS.NET? Mar 1 22:10:23 - named[170]: sysquery: findns error (3) on A.GTLD-SERVERS.NET? Mar 1 22:10:23 - named[170]: sysquery: findns error (3) on G.GTLD-SERVERS.NET? Mar 1 22:10:23 - named[170]: sysquery: findns error (3) on H.GTLD-SERVERS.NET? Mar 1 22:10:23 - named[170]: sysquery: findns error (3) on C.GTLD-SERVERS.NET? Mar 1 22:10:23 - named[170]: sysquery: findns error (3) on I.GTLD-SERVERS.NET? Mar 1 22:10:23 - named[170]: sysquery: findns error (3) on B.GTLD-SERVERS.NET? Mar 1 22:10:23 - named[170]: sysquery: findns error (3) on D.GTLD-SERVERS.NET? Mar 1 22:10:23 - named[170]: sysquery: findns error (3) on L.GTLD-SERVERS.NET? Mar 1 22:10:23 - named[170]: sysquery: findns error (3) on F.GTLD-SERVERS.NET? Mar 1 22:10:23 - named[170]: sysquery: findns error (3) on J.GTLD-SERVERS.NET? Mar 1 22:10:23 - named[170]: sysquery: findns error (3) on K.GTLD-SERVERS.NET? Mar 1 22:10:23 - named[170]: sysquery: findns error (3) on E.GTLD-SERVERS.NET? Mar 1 22:10:23 - named[170]: sysquery: findns error (3) on M.GTLD-SERVERS.NET? Mar 1 22:13:01 - named[170]: sysquery: findns error (2) on dns.bellona.pl? Mar 1 22:15:31 - named[170]: sysquery: findns error (3) on A.GTLD-SERVERS.NET? Mar 1 22:15:31 - named[170]: sysquery: findns error (3) on G.GTLD-SERVERS.NET? Mar 1 22:15:31 - named[170]: sysquery: findns error (3) on H.GTLD-SERVERS.NET? Mar 1 22:15:31 - named[170]: sysquery: findns error (3) on C.GTLD-SERVERS.NET? Mar 1 22:15:31 - named[170]: sysquery: findns error (3) on I.GTLD-SERVERS.NET? Mar 1 22:15:31 - named[170]: sysquery: findns error (3) on B.GTLD-SERVERS.NET? Mar 1 22:15:31 - named[170]: sysquery: findns error (3) on D.GTLD-SERVERS.NET? Mar 1 22:15:31 - named[170]: sysquery: findns error (3) on L.GTLD-SERVERS.NET? Mar 1 22:15:31 - named[170]: sysquery: findns error (3) on F.GTLD-SERVERS.NET? Mar 1 22:15:31 - named[170]: sysquery: findns error (3) on J.GTLD-SERVERS.NET? Mar 1 22:15:31 - named[170]: sysquery: findns error (3) on K.GTLD-SERVERS.NET? Mar 1 22:15:31 - named[170]: sysquery: findns error (3) on E.GTLD-SERVERS.NET? Mar 1 22:15:31 - named[170]: sysquery: findns error (3) on M.GTLD-SERVERS.NET? Mar 1 22:15:33 - named[170]: sysquery: findns error (3) on A.GTLD-SERVERS.NET? Mar 1 22:15:33 - named[170]: sysquery: findns error (3) on G.GTLD-SERVERS.NET? Mar 1 22:15:33 - named[170]: sysquery: findns error (3) on H.GTLD-SERVERS.NET? Mar 1 22:15:33 - named[170]: sysquery: findns error (3) on C.GTLD-SERVERS.NET? Mar 1 22:15:33 - named[170]: sysquery: findns error (3) on I.GTLD-SERVERS.NET? Mar 1 22:15:33 - named[170]: sysquery: findns error (3) on B.GTLD-SERVERS.NET? Mar 1 22:15:33 - named[170]: sysquery: findns error (3) on D.GTLD-SERVERS.NET? Mar 1 22:15:33 - named[170]: sysquery: findns error (3) on L.GTLD-SERVERS.NET? Mar 1 22:15:33 - named[170]: sysquery: findns error (3) on F.GTLD-SERVERS.NET? Mar 1 22:15:33 - named[170]: sysquery: findns error (3) on J.GTLD-SERVERS.NET? Mar 1 22:15:33 - named[170]: sysquery: findns error (3) on K.GTLD-SERVERS.NET? Mar 1 22:15:33 - named[170]: sysquery: findns error (3) on E.GTLD-SERVERS.NET? Mar 1 22:15:33 - named[170]: sysquery: findns error (3) on M.GTLD-SERVERS.NET? Mar 1 22:15:33 - named[170]: sysquery: findns error (3) on DNS1.DC.MSFT.NET? Mar 1 22:15:33 - named[170]: sysquery: findns error (3) on DNS1.SJ.MSFT.NET? Mar 1 22:15:33 - named[170]: sysquery: findns error (3) on DNS1.TK.MSFT.NET? Mar 1 22:15:33 - named[170]: sysquery: findns error (3) on DNS3.JP.MSFT.NET? Mar 1 22:15:33 - named[170]: sysquery: findns error (3) on DNS3.UK.MSFT.NET? Mar 1 22:15:33 - named[170]: sysquery: findns error (3) on DNS1.CP.MSFT.NET? Mar 1 22:20:43 - named[170]: sysquery: findns error (3) on A.GTLD-SERVERS.NET? Mar 1 22:20:43 - named[170]: sysquery: findns error (3) on G.GTLD-SERVERS.NET? Mar 1 22:20:43 - named[170]: sysquery: findns error (3) on H.GTLD-SERVERS.NET? Mar 1 22:20:43 - named[170]: sysquery: findns error (3) on C.GTLD-SERVERS.NET? Mar 1 22:20:43 - named[170]: sysquery: findns error (3) on I.GTLD-SERVERS.NET? Mar 1 22:20:43 - named[170]: sysquery: findns error (3) on B.GTLD-SERVERS.NET? Mar 1 22:20:43 - named[170]: sysquery: findns error (3) on D.GTLD-SERVERS.NET? Mar 1 22:20:43 - named[170]: sysquery: findns error (3) on L.GTLD-SERVERS.NET? Mar 1 22:20:43 - named[170]: sysquery: findns error (3) on F.GTLD-SERVERS.NET? Mar 1 22:20:43 - named[170]: sysquery: findns error (3) on J.GTLD-SERVERS.NET? Mar 1 22:20:43 - named[170]: sysquery: findns error (3) on K.GTLD-SERVERS.NET? Mar 1 22:20:43 - named[170]: sysquery: findns error (3) on E.GTLD-SERVERS.NET? Mar 1 22:20:43 - named[170]: sysquery: findns error (3) on M.GTLD-SERVERS.NET? Mar 1 22:23:44 - named[170]: sysquery: findns error (3) on A.GTLD-SERVERS.NET? Mar 1 22:23:44 - named[170]: sysquery: findns error (3) on G.GTLD-SERVERS.NET? Mar 1 22:23:44 - named[170]: sysquery: findns error (3) on H.GTLD-SERVERS.NET? Mar 1 22:23:44 - named[170]: sysquery: findns error (3) on C.GTLD-SERVERS.NET? Mar 1 22:23:44 - named[170]: sysquery: findns error (3) on I.GTLD-SERVERS.NET? Mar 1 22:23:44 - named[170]: sysquery: findns error (3) on B.GTLD-SERVERS.NET? Mar 1 22:23:44 - named[170]: sysquery: findns error (3) on D.GTLD-SERVERS.NET? Mar 1 22:23:44 - named[170]: sysquery: findns error (3) on L.GTLD-SERVERS.NET? Mar 1 22:23:44 - named[170]: sysquery: findns error (3) on F.GTLD-SERVERS.NET? Mar 1 22:23:44 - named[170]: sysquery: findns error (3) on J.GTLD-SERVERS.NET? Mar 1 22:23:44 - named[170]: sysquery: findns error (3) on K.GTLD-SERVERS.NET? Mar 1 22:23:44 - named[170]: sysquery: findns error (3) on E.GTLD-SERVERS.NET? Mar 1 22:23:44 - named[170]: sysquery: findns error (3) on M.GTLD-SERVERS.NET? Mar 1 22:25:33 - named[170]: sysquery: findns error (3) on A.GTLD-SERVERS.NET? Mar 1 22:25:33 - named[170]: sysquery: findns error (3) on G.GTLD-SERVERS.NET? Mar 1 22:25:33 - named[170]: sysquery: findns error (3) on H.GTLD-SERVERS.NET? Mar 1 22:25:33 - named[170]: sysquery: findns error (3) on C.GTLD-SERVERS.NET? Mar 1 22:25:33 - named[170]: sysquery: findns error (3) on I.GTLD-SERVERS.NET? Mar 1 22:25:33 - named[170]: sysquery: findns error (3) on B.GTLD-SERVERS.NET? Mar 1 22:25:33 - named[170]: sysquery: findns error (3) on D.GTLD-SERVERS.NET? Mar 1 22:25:33 - named[170]: sysquery: findns error (3) on L.GTLD-SERVERS.NET? Mar 1 22:25:33 - named[170]: sysquery: findns error (3) on F.GTLD-SERVERS.NET? Mar 1 22:25:33 - named[170]: sysquery: findns error (3) on J.GTLD-SERVERS.NET? Mar 1 22:25:33 - named[170]: sysquery: findns error (3) on K.GTLD-SERVERS.NET? Mar 1 22:25:33 - named[170]: sysquery: findns error (3) on E.GTLD-SERVERS.NET? Mar 1 22:25:33 - named[170]: sysquery: findns error (3) on M.GTLD-SERVERS.NET? Mar 1 22:26:17 - named[170]: sysquery: findns error (3) on A.GTLD-SERVERS.NET? Mar 1 22:26:17 - named[170]: sysquery: findns error (3) on G.GTLD-SERVERS.NET? Mar 1 22:26:17 - named[170]: sysquery: findns error (3) on H.GTLD-SERVERS.NET? Mar 1 22:26:17 - named[170]: sysquery: findns error (3) on C.GTLD-SERVERS.NET? Mar 1 22:26:17 - named[170]: sysquery: findns error (3) on I.GTLD-SERVERS.NET? Mar 1 22:26:17 - named[170]: sysquery: findns error (3) on B.GTLD-SERVERS.NET? Mar 1 22:26:17 - named[170]: sysquery: findns error (3) on D.GTLD-SERVERS.NET? Mar 1 22:26:17 - named[170]: sysquery: findns error (3) on L.GTLD-SERVERS.NET? Mar 1 22:26:17 - named[170]: sysquery: findns error (3) on F.GTLD-SERVERS.NET? Mar 1 22:26:17 - named[170]: sysquery: findns error (3) on J.GTLD-SERVERS.NET? Mar 1 22:26:17 - named[170]: sysquery: findns error (3) on K.GTLD-SERVERS.NET? Mar 1 22:26:17 - named[170]: sysquery: findns error (3) on E.GTLD-SERVERS.NET? Mar 1 22:26:17 - named[170]: sysquery: findns error (3) on M.GTLD-SERVERS.NET? Mar 1 22:32:19 - pppd[133]: Modem hangup Mar 1 22:32:19 - pppd[133]: Connection terminated. Mar 1 22:32:19 - pppd[133]: Connect time 139.3 minutes. Mar 1 22:32:19 - pppd[133]: Sent 60421305 bytes, received 343409690 bytes. Mar 1 22:32:19 - pppd[133]: Serial connection established. Mar 1 22:32:19 - pppd[133]: Using interface ppp0 Mar 1 22:32:19 - pppd[133]: Connect: ppp0 <--> /dev/ttyp1 Mar 1 22:32:24 - named[170]: sysquery: findns error (3) on A.GTLD-SERVERS.NET? Mar 1 22:32:24 - named[170]: sysquery: findns error (3) on G.GTLD-SERVERS.NET? Mar 1 22:32:24 - named[170]: sysquery: findns error (3) on H.GTLD-SERVERS.NET? Mar 1 22:32:24 - named[170]: sysquery: findns error (3) on C.GTLD-SERVERS.NET? Mar 1 22:32:24 - named[170]: sysquery: findns error (3) on I.GTLD-SERVERS.NET? Mar 1 22:32:24 - named[170]: sysquery: findns error (3) on B.GTLD-SERVERS.NET? Mar 1 22:32:24 - named[170]: sysquery: findns error (3) on D.GTLD-SERVERS.NET? Mar 1 22:32:24 - named[170]: sysquery: findns error (3) on L.GTLD-SERVERS.NET? Mar 1 22:32:24 - named[170]: sysquery: findns error (3) on F.GTLD-SERVERS.NET? Mar 1 22:32:24 - named[170]: sysquery: findns error (3) on J.GTLD-SERVERS.NET? Mar 1 22:32:24 - named[170]: sysquery: findns error (3) on K.GTLD-SERVERS.NET? Mar 1 22:32:24 - named[170]: sysquery: findns error (3) on E.GTLD-SERVERS.NET? Mar 1 22:32:24 - named[170]: sysquery: findns error (3) on M.GTLD-SERVERS.NET? Mar 1 22:32:24 - named[170]: ns_forw: sendto([194.204.159.1].53): Network is unreachable Mar 1 22:32:44 - named[170]: sysquery: findns error (3) on A.GTLD-SERVERS.NET? Mar 1 22:32:44 - named[170]: sysquery: findns error (3) on G.GTLD-SERVERS.NET? Mar 1 22:32:44 - named[170]: sysquery: findns error (3) on H.GTLD-SERVERS.NET? Mar 1 22:32:44 - named[170]: sysquery: findns error (3) on C.GTLD-SERVERS.NET? Mar 1 22:32:44 - named[170]: sysquery: findns error (3) on I.GTLD-SERVERS.NET? Mar 1 22:32:44 - named[170]: sysquery: findns error (3) on B.GTLD-SERVERS.NET? Mar 1 22:32:44 - named[170]: sysquery: findns error (3) on D.GTLD-SERVERS.NET? Mar 1 22:32:44 - named[170]: sysquery: findns error (3) on L.GTLD-SERVERS.NET? Mar 1 22:32:44 - named[170]: sysquery: findns error (3) on F.GTLD-SERVERS.NET? Mar 1 22:32:44 - named[170]: sysquery: findns error (3) on J.GTLD-SERVERS.NET? Mar 1 22:32:44 - named[170]: sysquery: findns error (3) on K.GTLD-SERVERS.NET? Mar 1 22:32:44 - named[170]: sysquery: findns error (3) on E.GTLD-SERVERS.NET? Mar 1 22:32:44 - named[170]: sysquery: findns error (3) on M.GTLD-SERVERS.NET? Mar 1 22:32:49 - pppd[133]: LCP: timeout sending Config-Requests Mar 1 22:32:49 - pppd[133]: Connection terminated. Mar 1 22:32:54 - pppoe[4930]: Timeout waiting for PADO packets Mar 1 22:33:19 - pppd[133]: Serial connection established. Mar 1 22:33:19 - pppd[133]: Using interface ppp0 Mar 1 22:33:19 - pppd[133]: Connect: ppp0 <--> /dev/ttyp0 Mar 1 22:33:21 - named[170]: sysquery: findns error (3) on A.GTLD-SERVERS.NET? Mar 1 22:33:21 - named[170]: sysquery: findns error (3) on G.GTLD-SERVERS.NET? Mar 1 22:33:21 - named[170]: sysquery: findns error (3) on H.GTLD-SERVERS.NET? Mar 1 22:33:21 - named[170]: sysquery: findns error (3) on C.GTLD-SERVERS.NET? Mar 1 22:33:21 - named[170]: sysquery: findns error (3) on I.GTLD-SERVERS.NET? Mar 1 22:33:21 - named[170]: sysquery: findns error (3) on B.GTLD-SERVERS.NET? Mar 1 22:33:21 - named[170]: sysquery: findns error (3) on D.GTLD-SERVERS.NET? Mar 1 22:33:21 - named[170]: sysquery: findns error (3) on L.GTLD-SERVERS.NET? Mar 1 22:33:21 - named[170]: sysquery: findns error (3) on F.GTLD-SERVERS.NET? Mar 1 22:33:21 - named[170]: sysquery: findns error (3) on J.GTLD-SERVERS.NET? Mar 1 22:33:21 - named[170]: sysquery: findns error (3) on K.GTLD-SERVERS.NET? Mar 1 22:33:21 - named[170]: sysquery: findns error (3) on E.GTLD-SERVERS.NET? Mar 1 22:33:21 - named[170]: sysquery: findns error (3) on M.GTLD-SERVERS.NET? Mar 1 22:33:49 - pppd[133]: LCP: timeout sending Config-Requests Mar 1 22:33:49 - pppd[133]: Connection terminated. Mar 1 22:33:54 - pppoe[4958]: Timeout waiting for PADO packets Mar 1 22:34:01 - named[170]: sysquery: findns error (3) on A.GTLD-SERVERS.NET? Mar 1 22:34:01 - named[170]: sysquery: findns error (3) on G.GTLD-SERVERS.NET? Mar 1 22:34:01 - named[170]: sysquery: findns error (3) on H.GTLD-SERVERS.NET? Mar 1 22:34:01 - named[170]: sysquery: findns error (3) on C.GTLD-SERVERS.NET? Mar 1 22:34:01 - named[170]: sysquery: findns error (3) on I.GTLD-SERVERS.NET? Mar 1 22:34:01 - named[170]: sysquery: findns error (3) on B.GTLD-SERVERS.NET? Mar 1 22:34:01 - named[170]: sysquery: findns error (3) on D.GTLD-SERVERS.NET? Mar 1 22:34:01 - named[170]: sysquery: findns error (3) on L.GTLD-SERVERS.NET? Mar 1 22:34:01 - named[170]: sysquery: findns error (3) on F.GTLD-SERVERS.NET? Mar 1 22:34:01 - named[170]: sysquery: findns error (3) on J.GTLD-SERVERS.NET? Mar 1 22:34:01 - named[170]: sysquery: findns error (3) on K.GTLD-SERVERS.NET? Mar 1 22:34:01 - named[170]: sysquery: findns error (3) on E.GTLD-SERVERS.NET? Mar 1 22:34:01 - named[170]: sysquery: findns error (3) on M.GTLD-SERVERS.NET? Mar 1 22:34:19 - pppd[133]: Serial connection established. Mar 1 22:34:19 - pppd[133]: Using interface ppp0 Mar 1 22:34:19 - pppd[133]: Connect: ppp0 <--> /dev/ttyp0 Mar 1 22:34:41 - named[170]: sysquery: findns error (3) on A.GTLD-SERVERS.NET? Mar 1 22:34:41 - named[170]: sysquery: findns error (3) on G.GTLD-SERVERS.NET? Mar 1 22:34:41 - named[170]: sysquery: findns error (3) on H.GTLD-SERVERS.NET? Mar 1 22:34:41 - named[170]: sysquery: findns error (3) on C.GTLD-SERVERS.NET? Mar 1 22:34:41 - named[170]: sysquery: findns error (3) on I.GTLD-SERVERS.NET? Mar 1 22:34:41 - named[170]: sysquery: findns error (3) on B.GTLD-SERVERS.NET? Mar 1 22:34:41 - named[170]: sysquery: findns error (3) on D.GTLD-SERVERS.NET? Mar 1 22:34:41 - named[170]: sysquery: findns error (3) on L.GTLD-SERVERS.NET? Mar 1 22:34:41 - named[170]: sysquery: findns error (3) on F.GTLD-SERVERS.NET? Mar 1 22:34:41 - named[170]: sysquery: findns error (3) on J.GTLD-SERVERS.NET? Mar 1 22:34:41 - named[170]: sysquery: findns error (3) on K.GTLD-SERVERS.NET? Mar 1 22:34:41 - named[170]: sysquery: findns error (3) on E.GTLD-SERVERS.NET? Mar 1 22:34:41 - named[170]: sysquery: findns error (3) on M.GTLD-SERVERS.NET? Mar 1 22:34:42 - pppoe[4986]: PADS: Service-Name: '' Mar 1 22:34:42 - pppoe[4986]: PPP session is 5792 Mar 1 22:34:46 - pppd[133]: local IP address 80.50.36.222 Mar 1 22:34:46 - pppd[133]: remote IP address 213.25.2.41 Mar 1 22:35:05 - named[170]: sysquery: findns error (3) on A.GTLD-SERVERS.NET? Mar 1 22:35:05 - named[170]: sysquery: findns error (3) on G.GTLD-SERVERS.NET? Mar 1 22:35:05 - named[170]: sysquery: findns error (3) on H.GTLD-SERVERS.NET? Mar 1 22:35:05 - named[170]: sysquery: findns error (3) on C.GTLD-SERVERS.NET? Mar 1 22:35:05 - named[170]: sysquery: findns error (3) on I.GTLD-SERVERS.NET? Mar 1 22:35:05 - named[170]: sysquery: findns error (3) on B.GTLD-SERVERS.NET? Mar 1 22:35:05 - named[170]: sysquery: findns error (3) on D.GTLD-SERVERS.NET? Mar 1 22:35:05 - named[170]: sysquery: findns error (3) on L.GTLD-SERVERS.NET? Mar 1 22:35:05 - named[170]: sysquery: findns error (3) on F.GTLD-SERVERS.NET? Mar 1 22:35:05 - named[170]: sysquery: findns error (3) on J.GTLD-SERVERS.NET? Mar 1 22:35:05 - named[170]: sysquery: findns error (3) on K.GTLD-SERVERS.NET? Mar 1 22:35:05 - named[170]: sysquery: findns error (3) on E.GTLD-SERVERS.NET? Mar 1 22:35:05 - named[170]: sysquery: findns error (3) on M.GTLD-SERVERS.NET? Mar 1 22:35:08 - named[170]: sysquery: findns error (3) on A.GTLD-SERVERS.NET? Mar 1 22:35:08 - named[170]: sysquery: findns error (3) on G.GTLD-SERVERS.NET? Mar 1 22:35:08 - named[170]: sysquery: findns error (3) on H.GTLD-SERVERS.NET? Mar 1 22:35:08 - named[170]: sysquery: findns error (3) on C.GTLD-SERVERS.NET? Mar 1 22:35:08 - named[170]: sysquery: findns error (3) on I.GTLD-SERVERS.NET? Mar 1 22:35:08 - named[170]: sysquery: findns error (3) on B.GTLD-SERVERS.NET? Mar 1 22:35:08 - named[170]: sysquery: findns error (3) on D.GTLD-SERVERS.NET? Mar 1 22:35:08 - named[170]: sysquery: findns error (3) on L.GTLD-SERVERS.NET? Mar 1 22:35:08 - named[170]: sysquery: findns error (3) on F.GTLD-SERVERS.NET? Mar 1 22:35:08 - named[170]: sysquery: findns error (3) on J.GTLD-SERVERS.NET? Mar 1 22:35:08 - named[170]: sysquery: findns error (3) on K.GTLD-SERVERS.NET? Mar 1 22:35:08 - named[170]: sysquery: findns error (3) on E.GTLD-SERVERS.NET? Mar 1 22:35:08 - named[170]: sysquery: findns error (3) on M.GTLD-SERVERS.NET? Mar 1 22:35:11 - kernel: 323 init Mar 1 22:35:13 - named[170]: sysquery: findns error (3) on A.GTLD-SERVERS.NET? Mar 1 22:35:13 - named[170]: sysquery: findns error (3) on G.GTLD-SERVERS.NET? Mar 1 22:35:13 - named[170]: sysquery: findns error (3) on H.GTLD-SERVERS.NET? Mar 1 22:35:13 - named[170]: sysquery: findns error (3) on C.GTLD-SERVERS.NET? Mar 1 22:35:13 - named[170]: sysquery: findns error (3) on I.GTLD-SERVERS.NET? Mar 1 22:35:13 - named[170]: sysquery: findns error (3) on B.GTLD-SERVERS.NET? Mar 1 22:35:13 - named[170]: sysquery: findns error (3) on D.GTLD-SERVERS.NET? Mar 1 22:35:13 - named[170]: sysquery: findns error (3) on L.GTLD-SERVERS.NET? Mar 1 22:35:13 - named[170]: sysquery: findns error (3) on F.GTLD-SERVERS.NET? Mar 1 22:35:13 - named[170]: sysquery: findns error (3) on J.GTLD-SERVERS.NET? Mar 1 22:35:13 - named[170]: sysquery: findns error (3) on K.GTLD-SERVERS.NET? Mar 1 22:35:13 - named[170]: sysquery: findns error (3) on E.GTLD-SERVERS.NET? Mar 1 22:35:13 - named[170]: sysquery: findns error (3) on M.GTLD-SERVERS.NET? Mar 1 22:35:21 - kernel: 323 done Mar 1 22:35:33 - named[170]: sysquery: findns error (3) on A.GTLD-SERVERS.NET? Mar 1 22:35:33 - named[170]: sysquery: findns error (3) on G.GTLD-SERVERS.NET? Mar 1 22:35:33 - named[170]: sysquery: findns error (3) on H.GTLD-SERVERS.NET? Mar 1 22:35:33 - named[170]: sysquery: findns error (3) on C.GTLD-SERVERS.NET? Mar 1 22:35:33 - named[170]: sysquery: findns error (3) on I.GTLD-SERVERS.NET? Mar 1 22:35:33 - named[170]: sysquery: findns error (3) on B.GTLD-SERVERS.NET? Mar 1 22:35:33 - named[170]: sysquery: findns error (3) on D.GTLD-SERVERS.NET? Mar 1 22:35:33 - named[170]: sysquery: findns error (3) on L.GTLD-SERVERS.NET? Mar 1 22:35:33 - named[170]: sysquery: findns error (3) on F.GTLD-SERVERS.NET? Mar 1 22:35:33 - named[170]: sysquery: findns error (3) on J.GTLD-SERVERS.NET? Mar 1 22:35:33 - named[170]: sysquery: findns error (3) on K.GTLD-SERVERS.NET? Mar 1 22:35:33 - named[170]: sysquery: findns error (3) on E.GTLD-SERVERS.NET? Mar 1 22:35:33 - named[170]: sysquery: findns error (3) on M.GTLD-SERVERS.NET? Mar 1 22:40:07 - named[170]: NSTATS 1046558407 1046547607 A=398 PTR=1 Mar 1 22:40:07 - named[170]: XSTATS 1046558407 1046547607 RQ=399 RR=150 RIQ=0 RNXD=0 RFwdQ=168 RFwdR=148 RDupQ=103 RDupR=0 RFail=0 RFErr=0 RErr=0 RTCP=0 RAXFR=0 RLame=0 ROpts=0 SSysQ=2 SAns=128 SFwdQ=168 SFwdR=148 SDupQ=33 SFail=20 SFErr=0 SErr=21 RNotNsQ=399 SNaAns=104 SNXD=22 Mar 1 22:42:23 - named[170]: sysquery: findns error (3) on A.GTLD-SERVERS.NET? Mar 1 22:42:23 - named[170]: sysquery: findns error (3) on G.GTLD-SERVERS.NET? Mar 1 22:42:23 - named[170]: sysquery: findns error (3) on H.GTLD-SERVERS.NET? Mar 1 22:42:23 - named[170]: sysquery: findns error (3) on C.GTLD-SERVERS.NET? Mar 1 22:42:23 - named[170]: sysquery: findns error (3) on I.GTLD-SERVERS.NET? Mar 1 22:42:23 - named[170]: sysquery: findns error (3) on B.GTLD-SERVERS.NET? Mar 1 22:42:23 - named[170]: sysquery: findns error (3) on D.GTLD-SERVERS.NET? Mar 1 22:42:23 - named[170]: sysquery: findns error (3) on L.GTLD-SERVERS.NET? Mar 1 22:42:23 - named[170]: sysquery: findns error (3) on F.GTLD-SERVERS.NET? Mar 1 22:42:23 - named[170]: sysquery: findns error (3) on J.GTLD-SERVERS.NET? Mar 1 22:42:23 - named[170]: sysquery: findns error (3) on K.GTLD-SERVERS.NET? Mar 1 22:42:23 - named[170]: sysquery: findns error (3) on E.GTLD-SERVERS.NET? Mar 1 22:42:23 - named[170]: sysquery: findns error (3) on M.GTLD-SERVERS.NET? Mar 1 22:45:33 - named[170]: sysquery: findns error (3) on A.GTLD-SERVERS.NET? Mar 1 22:45:33 - named[170]: sysquery: findns error (3) on G.GTLD-SERVERS.NET? Mar 1 22:45:33 - named[170]: sysquery: findns error (3) on H.GTLD-SERVERS.NET? Mar 1 22:45:33 - named[170]: sysquery: findns error (3) on C.GTLD-SERVERS.NET? Mar 1 22:45:33 - named[170]: sysquery: findns error (3) on I.GTLD-SERVERS.NET? Mar 1 22:45:33 - named[170]: sysquery: findns error (3) on B.GTLD-SERVERS.NET? Mar 1 22:45:33 - named[170]: sysquery: findns error (3) on D.GTLD-SERVERS.NET? Mar 1 22:45:33 - named[170]: sysquery: findns error (3) on L.GTLD-SERVERS.NET? Mar 1 22:45:33 - named[170]: sysquery: findns error (3) on F.GTLD-SERVERS.NET? Mar 1 22:45:33 - named[170]: sysquery: findns error (3) on J.GTLD-SERVERS.NET? Mar 1 22:45:33 - named[170]: sysquery: findns error (3) on K.GTLD-SERVERS.NET? Mar 1 22:45:33 - named[170]: sysquery: findns error (3) on E.GTLD-SERVERS.NET? Mar 1 22:45:33 - named[170]: sysquery: findns error (3) on M.GTLD-SERVERS.NET? Mar 1 22:47:33 - named[170]: sysquery: findns error (3) on A.GTLD-SERVERS.NET? Mar 1 22:47:33 - named[170]: sysquery: findns error (3) on G.GTLD-SERVERS.NET? Mar 1 22:47:33 - named[170]: sysquery: findns error (3) on H.GTLD-SERVERS.NET? Mar 1 22:47:33 - named[170]: sysquery: findns error (3) on C.GTLD-SERVERS.NET? Mar 1 22:47:33 - named[170]: sysquery: findns error (3) on I.GTLD-SERVERS.NET? Mar 1 22:47:33 - named[170]: sysquery: findns error (3) on B.GTLD-SERVERS.NET? Mar 1 22:47:33 - named[170]: sysquery: findns error (3) on D.GTLD-SERVERS.NET? Mar 1 22:47:33 - named[170]: sysquery: findns error (3) on L.GTLD-SERVERS.NET? Mar 1 22:47:33 - named[170]: sysquery: findns error (3) on F.GTLD-SERVERS.NET? Mar 1 22:47:33 - named[170]: sysquery: findns error (3) on J.GTLD-SERVERS.NET? Mar 1 22:47:33 - named[170]: sysquery: findns error (3) on K.GTLD-SERVERS.NET? Mar 1 22:47:33 - named[170]: sysquery: findns error (3) on E.GTLD-SERVERS.NET? Mar 1 22:47:33 - named[170]: sysquery: findns error (3) on M.GTLD-SERVERS.NET? Mar 1 22:54:43 - pppd[133]: Modem hangup Mar 1 22:54:43 - pppd[133]: Connection terminated. Mar 1 22:54:43 - pppd[133]: Connect time 20.4 minutes. Mar 1 22:54:43 - pppd[133]: Sent 6972969 bytes, received 67188956 bytes. Mar 1 22:54:43 - pppd[133]: Serial connection established. Mar 1 22:54:43 - pppd[133]: Using interface ppp0 Mar 1 22:54:43 - pppd[133]: Connect: ppp0 <--> /dev/ttyp1 Mar 1 22:54:46 - named[170]: sysquery: findns error (3) on A.GTLD-SERVERS.NET? Mar 1 22:54:46 - named[170]: sysquery: findns error (3) on G.GTLD-SERVERS.NET? Mar 1 22:54:46 - named[170]: sysquery: findns error (3) on H.GTLD-SERVERS.NET? Mar 1 22:54:46 - named[170]: sysquery: findns error (3) on C.GTLD-SERVERS.NET? Mar 1 22:54:46 - named[170]: sysquery: findns error (3) on I.GTLD-SERVERS.NET? Mar 1 22:54:46 - named[170]: sysquery: findns error (3) on B.GTLD-SERVERS.NET? Mar 1 22:54:46 - named[170]: sysquery: findns error (3) on D.GTLD-SERVERS.NET? Mar 1 22:54:46 - named[170]: sysquery: findns error (3) on L.GTLD-SERVERS.NET? Mar 1 22:54:46 - named[170]: sysquery: findns error (3) on F.GTLD-SERVERS.NET? Mar 1 22:54:46 - named[170]: sysquery: findns error (3) on J.GTLD-SERVERS.NET? Mar 1 22:54:46 - named[170]: sysquery: findns error (3) on K.GTLD-SERVERS.NET? Mar 1 22:54:46 - named[170]: sysquery: findns error (3) on E.GTLD-SERVERS.NET? Mar 1 22:54:46 - named[170]: sysquery: findns error (3) on M.GTLD-SERVERS.NET? Mar 1 22:54:46 - named[170]: ns_forw: sendto([194.204.159.1].53): Network is unreachable Mar 1 22:55:04 - named[170]: sysquery: findns error (3) on A.GTLD-SERVERS.NET? Mar 1 22:55:04 - named[170]: sysquery: findns error (3) on G.GTLD-SERVERS.NET? Mar 1 22:55:04 - named[170]: sysquery: findns error (3) on H.GTLD-SERVERS.NET? Mar 1 22:55:04 - named[170]: sysquery: findns error (3) on C.GTLD-SERVERS.NET? Mar 1 22:55:04 - named[170]: sysquery: findns error (3) on I.GTLD-SERVERS.NET? Mar 1 22:55:04 - named[170]: sysquery: findns error (3) on B.GTLD-SERVERS.NET? Mar 1 22:55:04 - named[170]: sysquery: findns error (3) on D.GTLD-SERVERS.NET? Mar 1 22:55:04 - named[170]: sysquery: findns error (3) on L.GTLD-SERVERS.NET? Mar 1 22:55:04 - named[170]: sysquery: findns error (3) on F.GTLD-SERVERS.NET? Mar 1 22:55:04 - named[170]: sysquery: findns error (3) on J.GTLD-SERVERS.NET? Mar 1 22:55:04 - named[170]: sysquery: findns error (3) on K.GTLD-SERVERS.NET? Mar 1 22:55:04 - named[170]: sysquery: findns error (3) on E.GTLD-SERVERS.NET? Mar 1 22:55:04 - named[170]: sysquery: findns error (3) on M.GTLD-SERVERS.NET? Mar 1 22:55:13 - pppd[133]: LCP: timeout sending Config-Requests Mar 1 22:55:13 - pppd[133]: Connection terminated. Mar 1 22:55:18 - pppoe[5567]: Timeout waiting for PADO packets Mar 1 22:55:24 - named[170]: sysquery: findns error (3) on A.GTLD-SERVERS.NET? Mar 1 22:55:24 - named[170]: sysquery: findns error (3) on G.GTLD-SERVERS.NET? Mar 1 22:55:24 - named[170]: sysquery: findns error (3) on H.GTLD-SERVERS.NET? Mar 1 22:55:24 - named[170]: sysquery: findns error (3) on C.GTLD-SERVERS.NET? Mar 1 22:55:24 - named[170]: sysquery: findns error (3) on I.GTLD-SERVERS.NET? Mar 1 22:55:24 - named[170]: sysquery: findns error (3) on B.GTLD-SERVERS.NET? Mar 1 22:55:24 - named[170]: sysquery: findns error (3) on D.GTLD-SERVERS.NET? Mar 1 22:55:24 - named[170]: sysquery: findns error (3) on L.GTLD-SERVERS.NET? Mar 1 22:55:24 - named[170]: sysquery: findns error (3) on F.GTLD-SERVERS.NET? Mar 1 22:55:24 - named[170]: sysquery: findns error (3) on J.GTLD-SERVERS.NET? Mar 1 22:55:24 - named[170]: sysquery: findns error (3) on K.GTLD-SERVERS.NET? Mar 1 22:55:24 - named[170]: sysquery: findns error (3) on E.GTLD-SERVERS.NET? Mar 1 22:55:24 - named[170]: sysquery: findns error (3) on M.GTLD-SERVERS.NET? Mar 1 22:55:43 - pppd[133]: Serial connection established. Mar 1 22:55:43 - pppd[133]: Using interface ppp0 Mar 1 22:55:43 - pppd[133]: Connect: ppp0 <--> /dev/ttyp0 Mar 1 22:55:44 - named[170]: sysquery: findns error (3) on A.GTLD-SERVERS.NET? Mar 1 22:55:44 - named[170]: sysquery: findns error (3) on G.GTLD-SERVERS.NET? Mar 1 22:55:44 - named[170]: sysquery: findns error (3) on H.GTLD-SERVERS.NET? Mar 1 22:55:44 - named[170]: sysquery: findns error (3) on C.GTLD-SERVERS.NET? Mar 1 22:55:44 - named[170]: sysquery: findns error (3) on I.GTLD-SERVERS.NET? Mar 1 22:55:44 - named[170]: sysquery: findns error (3) on B.GTLD-SERVERS.NET? Mar 1 22:55:44 - named[170]: sysquery: findns error (3) on D.GTLD-SERVERS.NET? Mar 1 22:55:44 - named[170]: sysquery: findns error (3) on L.GTLD-SERVERS.NET? Mar 1 22:55:44 - named[170]: sysquery: findns error (3) on F.GTLD-SERVERS.NET? Mar 1 22:55:44 - named[170]: sysquery: findns error (3) on J.GTLD-SERVERS.NET? Mar 1 22:55:44 - named[170]: sysquery: findns error (3) on K.GTLD-SERVERS.NET? Mar 1 22:55:44 - named[170]: sysquery: findns error (3) on E.GTLD-SERVERS.NET? Mar 1 22:55:44 - named[170]: sysquery: findns error (3) on M.GTLD-SERVERS.NET? Mar 1 22:56:04 - named[170]: sysquery: findns error (3) on A.GTLD-SERVERS.NET? Mar 1 22:56:04 - named[170]: sysquery: findns error (3) on G.GTLD-SERVERS.NET? Mar 1 22:56:04 - named[170]: sysquery: findns error (3) on H.GTLD-SERVERS.NET? Mar 1 22:56:04 - named[170]: sysquery: findns error (3) on C.GTLD-SERVERS.NET? Mar 1 22:56:04 - named[170]: sysquery: findns error (3) on I.GTLD-SERVERS.NET? Mar 1 22:56:04 - named[170]: sysquery: findns error (3) on B.GTLD-SERVERS.NET? Mar 1 22:56:04 - named[170]: sysquery: findns error (3) on D.GTLD-SERVERS.NET? Mar 1 22:56:04 - named[170]: sysquery: findns error (3) on L.GTLD-SERVERS.NET? Mar 1 22:56:04 - named[170]: sysquery: findns error (3) on F.GTLD-SERVERS.NET? Mar 1 22:56:04 - named[170]: sysquery: findns error (3) on J.GTLD-SERVERS.NET? Mar 1 22:56:04 - named[170]: sysquery: findns error (3) on K.GTLD-SERVERS.NET? Mar 1 22:56:04 - named[170]: sysquery: findns error (3) on E.GTLD-SERVERS.NET? Mar 1 22:56:04 - named[170]: sysquery: findns error (3) on M.GTLD-SERVERS.NET? Mar 1 22:56:13 - pppd[133]: LCP: timeout sending Config-Requests Mar 1 22:56:13 - pppd[133]: Connection terminated. Mar 1 22:56:18 - pppoe[5611]: Timeout waiting for PADO packets Mar 1 22:56:24 - named[170]: sysquery: findns error (3) on A.GTLD-SERVERS.NET? Mar 1 22:56:24 - named[170]: sysquery: findns error (3) on G.GTLD-SERVERS.NET? Mar 1 22:56:24 - named[170]: sysquery: findns error (3) on H.GTLD-SERVERS.NET? Mar 1 22:56:24 - named[170]: sysquery: findns error (3) on C.GTLD-SERVERS.NET? Mar 1 22:56:24 - named[170]: sysquery: findns error (3) on I.GTLD-SERVERS.NET? Mar 1 22:56:24 - named[170]: sysquery: findns error (3) on B.GTLD-SERVERS.NET? Mar 1 22:56:24 - named[170]: sysquery: findns error (3) on D.GTLD-SERVERS.NET? Mar 1 22:56:24 - named[170]: sysquery: findns error (3) on L.GTLD-SERVERS.NET? Mar 1 22:56:24 - named[170]: sysquery: findns error (3) on F.GTLD-SERVERS.NET? Mar 1 22:56:24 - named[170]: sysquery: findns error (3) on J.GTLD-SERVERS.NET? Mar 1 22:56:24 - named[170]: sysquery: findns error (3) on K.GTLD-SERVERS.NET? Mar 1 22:56:24 - named[170]: sysquery: findns error (3) on E.GTLD-SERVERS.NET? Mar 1 22:56:24 - named[170]: sysquery: findns error (3) on M.GTLD-SERVERS.NET? Mar 1 22:56:25 - named[170]: sysquery: findns error (3) on A.GTLD-SERVERS.NET? Mar 1 22:56:25 - named[170]: sysquery: findns error (3) on G.GTLD-SERVERS.NET? Mar 1 22:56:25 - named[170]: sysquery: findns error (3) on H.GTLD-SERVERS.NET? Mar 1 22:56:25 - named[170]: sysquery: findns error (3) on C.GTLD-SERVERS.NET? Mar 1 22:56:25 - named[170]: sysquery: findns error (3) on I.GTLD-SERVERS.NET? Mar 1 22:56:25 - named[170]: sysquery: findns error (3) on B.GTLD-SERVERS.NET? Mar 1 22:56:25 - named[170]: sysquery: findns error (3) on D.GTLD-SERVERS.NET? Mar 1 22:56:25 - named[170]: sysquery: findns error (3) on L.GTLD-SERVERS.NET? Mar 1 22:56:25 - named[170]: sysquery: findns error (3) on F.GTLD-SERVERS.NET? Mar 1 22:56:25 - named[170]: sysquery: findns error (3) on J.GTLD-SERVERS.NET? Mar 1 22:56:25 - named[170]: sysquery: findns error (3) on K.GTLD-SERVERS.NET? Mar 1 22:56:25 - named[170]: sysquery: findns error (3) on E.GTLD-SERVERS.NET? Mar 1 22:56:25 - named[170]: sysquery: findns error (3) on M.GTLD-SERVERS.NET? Mar 1 22:56:43 - pppd[133]: Serial connection established. Mar 1 22:56:43 - pppd[133]: Using interface ppp0 Mar 1 22:56:43 - pppd[133]: Connect: ppp0 <--> /dev/ttyp0 Mar 1 22:57:01 - pppoe[5658]: PADS: Service-Name: '' Mar 1 22:57:01 - pppoe[5658]: PPP session is 6144 Mar 1 22:57:01 - named[170]: sysquery: findns error (3) on A.GTLD-SERVERS.NET? Mar 1 22:57:01 - named[170]: sysquery: findns error (3) on G.GTLD-SERVERS.NET? Mar 1 22:57:01 - named[170]: sysquery: findns error (3) on H.GTLD-SERVERS.NET? Mar 1 22:57:01 - named[170]: sysquery: findns error (3) on C.GTLD-SERVERS.NET? Mar 1 22:57:01 - named[170]: sysquery: findns error (3) on I.GTLD-SERVERS.NET? Mar 1 22:57:01 - named[170]: sysquery: findns error (3) on B.GTLD-SERVERS.NET? Mar 1 22:57:01 - named[170]: sysquery: findns error (3) on D.GTLD-SERVERS.NET? Mar 1 22:57:01 - named[170]: sysquery: findns error (3) on L.GTLD-SERVERS.NET? Mar 1 22:57:01 - named[170]: sysquery: findns error (3) on F.GTLD-SERVERS.NET? Mar 1 22:57:01 - named[170]: sysquery: findns error (3) on J.GTLD-SERVERS.NET? Mar 1 22:57:01 - named[170]: sysquery: findns error (3) on K.GTLD-SERVERS.NET? Mar 1 22:57:01 - named[170]: sysquery: findns error (3) on E.GTLD-SERVERS.NET? Mar 1 22:57:01 - named[170]: sysquery: findns error (3) on M.GTLD-SERVERS.NET? Mar 1 22:57:04 - pppd[133]: local IP address 80.50.36.222 Mar 1 22:57:04 - pppd[133]: remote IP address 213.25.2.41 Mak. mak@radiopkh.org gg 1218735
Technical Details
Message-ID:
<b3r01a$g3p$1@korweta.task.gda.pl>Path:
mbox-mo1.pugleaf.net!news-archive.icm.edu.pl!news.rmf.pl!news.ipartners.pl!newsfeed.gazeta.pl!news.atman.pl!news.task.gda.pl!not-for-mailReferences:
<b3q42k$pk0$1@korweta.task.gda.pl> <b3qsg2$3vd$1@atlantis.news.tpi.pl> <b3quoo$9do$1@korweta.task.gda.pl>Show Full Headers
Complete Article Headers
Path: mbox-mo1.pugleaf.net!news-archive.icm.edu.pl!news.rmf.pl!news.ipartners.pl!newsfeed.gazeta.pl!news.atman.pl!news.task.gda.pl!not-for-mail From: "Mak" <mak777@wp.pl> Newsgroups: alt.pl.freesco Subject: Re: Podtrzymywanie połączenia NEO+ Date: Sat, 1 Mar 2003 20:00:57 +0100 Organization: CI TASK http://www.task.gda.pl Lines: 1860 Message-ID: <b3r01a$g3p$1@korweta.task.gda.pl> References: <b3q42k$pk0$1@korweta.task.gda.pl> <b3qsg2$3vd$1@atlantis.news.tpi.pl> <b3quoo$9do$1@korweta.task.gda.pl> NNTP-Posting-Host: pe222.neoplus.adsl.tpnet.pl X-Trace: korweta.task.gda.pl 1046545270 16505 80.50.36.222 (1 Mar 2003 19:01:10 GMT) X-Complaints-To: abuse@news.task.gda.pl NNTP-Posting-Date: Sat, 1 Mar 2003 19:01:10 +0000 (UTC) X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 6.00.2800.1106 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit