ecursion setting in named is immaterial when doing dig +trace.
> Once dig gets the addresses of the root server, it stops asking your local
> copy of named and starts asking the root servers for itself and does not rely
> any further on named.
>
> Lyle
>
> On 05/02/12
s to the real issue you have.
>
> Lyle Giese
> LCR Computer Services, Inc.
>
> On 05/02/12 16:36, Paul Marais wrote:
>>
>> Thanks Lyle,
>> You're right - I started using the host command because it was giving me the
>> error I found in the postfix logs..
use a longer timeout perhaps.
On May 2, 2012, at 1:42 PM, Lyle Giese wrote:
> On 05/02/12 12:12, Paul Marais wrote:
>> Hi,
>> I'm having an issue where my postfix server is having trouble with some
>> lookups.
>> When I type 'host', 80% of the time I get decen
;<>> DiG 9.7.3 <<>> mx gmail.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 32902
;; flags: qr rd; QUERY: 1, ANSWER: 0, AUTHORITY: 13, ADDITIONAL: 5
;; WARNING: recursion requested but not available
On May 2, 2012, at 1
Hi,
I'm having an issue where my postfix server is having trouble with some lookups.
When I type 'host ', 80% of the time I get decent reply speed, but
for 20% I get a 5 second delay, or even a timeout.
My nameserver is configured to only allow recursion for hosts on my local
network, and I have
5 matches
Mail list logo
