On 28 Mar 2015, at 03:44 , Nicolás <[email protected]> wrote: > Don't completely rely on dig, as you might be obtaining a cached DNS > response. DNS servers usually cache responses for a certain time. You can try > using dig along with the +trace option to see where the query is going > through, or even querying directly the authoritative server for some of the > domains and see the result for debugging purposes.
My DNS is the next machine over, but +trace does seem to be running very slowly, so that is probably the cause. Getting a reply from my main DNS server took over 18 seconds. ;; Received 496 bytes from 75.148.37.67#53(75.148.37.67) in 18166 ms And from the root servers, even longer. ;; Received 487 bytes from 193.0.14.129#53(193.0.14.129) in 60743 ms Thanks. I’ll look at why bind on my DNS server is so slow. -- 'But you ain't part of it, are you?' said Granny conversationally. 'You try, but you always find yourself watchin' yourself watchin' people, eh? Never quite believin' anything? Thinkin' the wrong thoughts?'
