Leonard Ong wrote:
Hi,
I got some lines in /var/log/messages that i dont' understand : Mar 1 09:04:43 ns1 named[1683]: Lame server on 'banaspati.civl.telkom.net.id' (in 'telkom.net.id'?): [139.130.4.5].53 'ns1.telstra.net' Mar 1 09:05:47 ns1 kernel: eth0: Transmit error, Tx status register 82.
If your eth0 is up and running, ignore this as a transient error. Although, it would be better if someone could give a more meaningful explanation. Anyone?
Mar 1 09:12:20 ns1 named[1683]: "usa.net IN NS" points to a CNAME (dns02.ops.usa.net)
I think bind requires that the NS entries point to "A" records. It logs this warning whenever it finds an NS record pointing to a "CNAME" record. I have seen this a lot in my logs. Again, harmless.
Mar 1 09:18:00 ns1 named[1683]: Lame server on 'kommax.com.hk' (in 'kommax.com.hk'?): [202.87.253.7].53 'ns.artogram.com' Mar 1 09:18:01 ns1 named[1683]: Lame server on 'kommax.com.hk' (in 'kommax.com.hk'?): [202.87.252.5].53 'ns.eastworld.net'
A "lame server" is one that should be authoritative for a zone, according to the NS records that delegate authority for that zone, but really isn't, perhaps because it hasn't been configured to load the zone or because it is a secondary master that has expired the zone. Again, harmless. The last two errors are not your problems at all. I don't know about the first one. Nadeem -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/