Lame delegations on DNS lookups

[jpm121]

Hi all,

Perused some server log files today (I know, it was a slow Monday) and ran across something I'd seen before but never bothered to research.

In a nutshell -- this machine is one of those "all-in-one" internet appliance deals: gateway, DNS, mail server, web server, file server, firewall, etc. It does all of the jobs reasonably well, but not fantastic. Basically, though, once you configure the sucker, it just sits and chugs away.

The IP address of this box (192.168.60.254) is designated as the default gateway and DNS server for all (20 or so) Win98 PCs on the TCP/IP LAN. Out the other end is an SDSL line over a router -- all standard fare.

I'm not actually maintaining any DNS servers on my LAN -- my ISP provided 8 or 9 servers with an ABOVE.NET suffix and those are used by the server to provide DNS resolution to the client PCs -- it does the lookups and caches some stuff but doesn't really maintain DNS info.

I'm seeing error messages along the lines of "Lame delegation of '

http://www.symantec.com'

to 198.x.x.x". Users are still getting through, and I can get to symantec's site just fine. However, Symantec's web site actually resolves to 63.241.29.142. I did some research but am still having trouble understanding how this part of DNS is working and what (if anything) I should be concerned about from this error message. I sure appreciate any insight on this...

Thanks!

 

[adam108]

I'm not the "authority" on dns but a quick search on altavista did turn up the following link. Go to this site and search for lame and it should give you what you are seeking. From my interpretation, it certainly seems like an authority problem at symantec. A quick note to their site admin could resolve the problem if I am correct in this interpretation. Godd luck and keep us posted.

 

[adam108]

Oops, so busy hedging my answer that I forgot to put in the link...

http://www.intac.com/~cdp/cptd-faq/section4.html#lame