This is a part of an log message that you will see a ton if you ever run your own DNS server.
Feb 28 23:33:56 wilbur named[14270]: lame server resolving 'online.wsj.com' (in 'wsj.com'?): 63.240.101.1#53
Mar 1 00:03:59 wilbur named[14270]: lame server resolving 'online.wsj.com' (in 'wsj.com'?): 63.240.101.1#53
Mar 1 00:34:01 wilbur named[14270]: lame server resolving 'online.wsj.com' (in 'wsj.com'?): 63.240.101.1#53
Mar 1 00:49:02 wilbur named[14270]: lame server resolving 'online.wsj.com' (in 'wsj.com'?): 63.240.101.1#53
Mar 1 01:04:03 wilbur named[14270]: lame server resolving 'online.wsj.com' (in 'wsj.com'?): 63.240.101.1#53
I must have left a browser open before going to bed.
Anyway, these messages can really fill up the log files and make things really difficult to sort through. As this is really the fault of the remote DNS server admin, the best thing I can do on my end is to drop these messages into the bit bucket.
In /etc/named.conf, add the bolded text:
logging {
category lame-servers { null; };