Gordon Messmer wrote: ----------------->>>> The name server responsible for resolving the reverse queries for the 65.106.254.x network isn't configured properly. Your server was referred to is as the authority for that zone, but it thinks that another server is the authority. ----------------->>>>
Jonathan Bartlett wrote: ----------------->>>> If you run a nameserver, you may see an error about a "lame server". New administrators of DNS servers often ask what this is, what it means, and whether it's a problem. There is no cause for concern. The lame server is one that is advertised to have authoritative information about a domain, but doesn't. This can happen in a few different ways, but it's usually not worth the trouble to track down the administrator of the other domain. ----------------->>>> Well that is interesting... So the lame server is configured incorrectly and has my server listed as the authority... which its not! But the thing that concerns me is I get a bunch of these not always the same address either. This morning it was 142.166.236.211.in-addr.arpa 150.117.234.211.in-addr.arpa 165.`66.91.211.in-addr.arpa 188.255.132.202.in-addr.arpa 202.132.255.189.in-addr.arpa dns1.kr.iasiaworks.net.in-addr.arpa Which doesn't even include yesterdays: 181.254.106.65-in-addr.arpa This kinda matches what Jonathan says. I was just concerned that this was some kind of an attempt to circumvent my nameserver. So I will ignore them...no? _______________________________________________ Redhat-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/redhat-list
