Why does plusnet give more info than other dns servers

[#1]

Example of a few servers, plusnet seem to give out more info... why ?
Tracing to yahoo.com via 212.159.6.9, maximum of 3 retries
212.159.6.9 (212.159.6.9) Got answer
|\___ ns5.yahoo.com [yah...





























via 208.67.222.220, maximum of 3 retries
208.67.222.220 (208.67.222.220) Got answer
208.67.222.220 (...


via 8.8.8.8, maximum of 3 retries
8.8.8.8 (8.8.8.8.) Got answer
8.8.8.8 (8.8.8.8.)                  ...



via 208.67.222.123, maximum of 3 retries
208.67.222.123 (208.67.222.123) Got answer
208.67.222.123 (...
via 212.159.6.9, maximum of 3 retries
212.159.6.9 (212.159.6.9)
|\___ dns.iad.llns.net [llnw.net] (...

[#2]

Don't know about PN's DNS software but with your Pi /  "unbound" try this .conf setting.

Quote

minimal-responses: <yes or no>               If  yes,  Unbound  doesn't  insert authority/additional sections               into response messages when those  sections  are  not  required.               This  reduces  response  size  significantly,  and may avoid TCP               fallback for some responses.  This may cause a  slight  speedup.               The  default  is no, because the DNS protocol RFCs mandate these               sections, and the additional content could be of  use  and  save               roundtrips for clients.

[#3]

Cheers npr, every little helps.
The little pi is working pretty well these days, it's a case of finding a good Kernel I guess. Out of interest though I'm still curious why more info seems to be given out via plusnet v/s other popular servers.
[tt] thread0.num.queries=119013
thread0.num.cachehits=87748
thread0.num.cachemiss=31265
thread0.num.prefetch=2083
thread0.num.recursivereplies=31265
thread0.requestlist.avg=0.933909
thread0.requestlist.max=12
thread0.requestlist.overwritten=0
thread0.requestlist.exceeded=0
thread0.requestlist.current.all=0
thread0.requestlist.current.user=0
thread0.recursion.time.avg=0.077400
thread0.recursion.time.median=0.0321775
total.num.queries=119013
total.num.cachehits=87748
total.num.cachemiss=31265
total.num.prefetch=2083
total.num.recursivereplies=31265
total.requestlist.avg=0.933909
total.requestlist.max=12
total.requestlist.overwritten=0
total.requestlist.exceeded=0
total.requestlist.current.all=0
total.requestlist.current.user=0
total.recursion.time.avg=0.077400
total.recursion.time.median=0.0321775
time.now=1401381325.066039
time.up=1839023.362245
time.elapsed=1824615.456262[/tt].

[#4]

  I misread your question.
What tool are you using?
Is it something like dig +trace

Quote

; <<>> DiG 9.8.6-P1 <<>> +trace yahoo.com @212.159.6.9 ;; global options: +cmd .                      484570  IN      NS      b.root-servers.net. .                      484570  IN      NS      f.root-servers.net. .                      484570  IN      NS      d.root-servers.net. .                      484570  IN      NS      a.root-servers.net. .                      484570  IN      NS      j.root-servers.net. .                      484570  IN      NS      l.root-servers.net. .                      484570  IN      NS      k.root-servers.net. .                      484570  IN      NS      h.root-servers.net. .                      484570  IN      NS      e.root-servers.net. .                      484570  IN      NS      m.root-servers.net. .                      484570  IN      NS      c.root-servers.net. .                      484570  IN      NS      g.root-servers.net. .                      484570  IN      NS      i.root-servers.net. ;; Received 228 bytes from 212.159.6.9#53(212.159.6.9) in 390 ms com.                    172800  IN      NS      a.gtld-servers.net. com.                    172800  IN      NS      b.gtld-servers.net. com.                    172800  IN      NS      c.gtld-servers.net. com.                    172800  IN      NS      d.gtld-servers.net. com.                    172800  IN      NS      e.gtld-servers.net. com.                    172800  IN      NS      f.gtld-servers.net. com.                    172800  IN      NS      g.gtld-servers.net. com.                    172800  IN      NS      h.gtld-servers.net. com.                    172800  IN      NS      i.gtld-servers.net. com.                    172800  IN      NS      j.gtld-servers.net. com.                    172800  IN      NS      k.gtld-servers.net. com.                    172800  IN      NS      l.gtld-servers.net. com.                    172800  IN      NS      m.gtld-servers.net. ;; Received 487 bytes from 199.7.83.42#53(l.root-servers.net) in 375 ms yahoo.com.              172800  IN      NS      ns1.yahoo.com. yahoo.com.              172800  IN      NS      ns5.yahoo.com. yahoo.com.              172800  IN      NS      ns2.yahoo.com. yahoo.com.              172800  IN      NS      ns3.yahoo.com. yahoo.com.              172800  IN      NS      ns4.yahoo.com. ;; Received 197 bytes from 192.42.93.30#53(g.gtld-servers.net) in 296 ms yahoo.com.              1800    IN      A      98.138.253.109 yahoo.com.              1800    IN      A      206.190.36.45 yahoo.com.              1800    IN      A      98.139.183.24 yahoo.com.              172800  IN      NS      ns5.yahoo.com. yahoo.com.              172800  IN      NS      ns6.yahoo.com. yahoo.com.              172800  IN      NS      ns4.yahoo.com. yahoo.com.              172800  IN      NS      ns3.yahoo.com. yahoo.com.              172800  IN      NS      ns1.yahoo.com. yahoo.com.              172800  IN      NS      ns2.yahoo.com. ;; Received 279 bytes from 203.84.221.53#53(ns3.yahoo.com) in 218 ms

[#5]

dnstracer
sudo dnstracer -s 8.8.8.8 -o -4 yahoo.com

[#6]

I quickly got bored reading the following -- but it doesn't look good.
http://homepage.ntlworld.com/jonathan.deboynepollard/FGA/dnstracer-incorrect-algorithm.html
Don't you have dig in linux

[#7]

Quite!  
Quickly runs away while typing: sudo apt-get purge dnstracer............

[#8]

That tweak seems to work better npr, I'll update the post with stats again when I get  hits up around the 100,000 mark in a few days.
I have never seen anything less than 0.03 Previously
[tt]
thread0.num.queries=333
thread0.num.cachehits=287
thread0.num.cachemiss=46
thread0.num.prefetch=0
thread0.num.recursivereplies=46
thread0.requestlist.avg=0.0434783
thread0.requestlist.max=1
thread0.requestlist.overwritten=0
thread0.requestlist.exceeded=0
thread0.requestlist.current.all=0
thread0.requestlist.current.user=0
thread0.recursion.time.avg=0.026126
thread0.recursion.time.median=0.0268516
total.num.queries=333
total.num.cachehits=287
total.num.cachemiss=46
total.num.prefetch=0
total.num.recursivereplies=46
total.requestlist.avg=0.0434783
total.requestlist.max=1
total.requestlist.overwritten=0
total.requestlist.exceeded=0
total.requestlist.current.all=0
total.requestlist.current.user=0
total.recursion.time.avg=0.026126
total.recursion.time.median=0.0268516
time.now=1401401139.785368
time.up=1858838.081574
time.elapsed=1844430.175591[/tt]

[#9]

That's better than I ever got from the Pi. 
You've tempted me to have another go.
Which version of linux are you running -- download link if you have it please. 

[#10]

I used bleeding edge updates till i found what worked best for me npr, via "sudo rpi-update" https://github.com/Hexxeh/rpi-update or http://asliceofraspberrypi.blogspot.co.uk/2013/02/updating-your-raspberry-pis-kernel-and.html I'm also still over-clocking as well, it's worth trying the stock version, things have moved on quite a bit, well worth a try though! But i'm sure it won't take you long to rumble the process of finding how to get to the following versions that I'm running.
512MB Version Rpi
Linux  3.10.37+ #669 PREEMPT Tue Apr 15 14:44:32 BST 2014 armv6l GNU/Linux
Apr 23 2014 00:09:02
Copyright (c) 2012 Broadcom
version 8c6eeb8ba935907264625ed86287962173a60e55
Memory split GPU=16
./cpustatus
Temperature: 43.9 C
Voltage: 1.25 V (+0.5)
Min speed: 900 MHz
Max speed: 900 MHz
Current speed: 900 MHzersion
Governor: ondemand

#!/bin/bash
# cpustatus
#
# Prints the current state of the CPU like temperature, voltage and speed.
# The temperature is reported in degrees Celsius (C) while
# the CPU speed is calculated in megahertz (MHz).
 
function convert_to_MHz {
let value=$1/1000
echo "$value"
}
 
function calculate_overvolts {
# We can safely ignore the integer
# part of the decimal argument
# since it's not realistic to run the Pi
# at voltages higher than 1.99 V
let overvolts=${1#*.}-20
echo "$overvolts"
}
 
temp=$(vcgencmd measure_temp)
temp=${temp:5:4}
 
volts=$(vcgencmd measure_volts)
volts=${volts:5:4}
 
if [ $volts != "1.20" ]; then
overvolts=$(calculate_overvolts $volts)
fi
 
minFreq=$(cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq)
minFreq=$(convert_to_MHz $minFreq)
 
maxFreq=$(cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq)
maxFreq=$(convert_to_MHz $maxFreq)
 
freq=$(cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_cur_freq)
freq=$(convert_to_MHz $freq)
 
governor=$(cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor)
 
echo "Temperature: $temp C"
echo -n "Voltage: $volts V"
[ $overvolts ] && echo " (+0.$overvolts overvolt)" || echo -e "\r"
echo "Min speed: $minFreq MHz"
echo "Max speed: $maxFreq MHz"
echo "Current speed: $freq MHz"
echo "Governor: $governor"
 
exit 0

Great little script, i need to find the source and paste the link.
Just shout if you want a copy of my unbound.conf