Lyle Giese wrote:
>
> Don't use host. It's not telling us what is going wrong and it's only doing
> an A record lookup of host name.
I agree dig is better for serious debugging, but for a quick check host
isn't as bad as you suggest.
$ host dotat.at
dotat.at has address 212.13.197.229
dotat.at
I think its fixed... just not sure why...
I removed the 'recursion no' line and its much faster now and not timing out...
I used to have :
recursion no;
allow-query { any; };
allow-recursion { 192.168.2.0/24; 127.0.0.1; };
allow-query-cache { 192.168.2.0/24;
If you have recursion turned off, then no it won't forward. It tells
your named that if it doesn't already know the answer, tell the client I
don't know and won't ask anyone else.
But what about the second scenerio below? You check on scenerio 1, but
you have not addressed #2.
Besides, the
On May 02, 2012, at 18.41, Paul Marais wrote:
> So it looks like I just need to make postfix use a longer timeout perhaps.
or, you could just not use your isp's nameservers, and let bind do what it
does. it's unlikely that your isp's nameservers are doing you great favors, if
any at all. eit
I checked the firewall and I have rules to allow tcp & udp on port 53.
Is there anything I can do to get more information on why no connection is made
to the root servers.
I'm a bit confused.. if I have recursion off shouldn't my local named be
forwarding the request to the name server in my "f
In article ,
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 decent reply speed, but
> > for 20% I get a 5 second delay, or even a timeout.
>
Using dig +trace, dig is trying to accomplish the recursion that named
would do for you. This tells us your local copy of named is answering
requests as that is where you received the list of root servers from.
But when dig tries to ask the root name servers how to find gmail.com,
dig is unab
So I discovered that if I just do: dig gmail.com I get no answers... but thats
most likely because my NS is set to not allow recursion... what I didn't
realize is that dig was not forwarding the request to my isp's NS.
When force the lookup on my isp's NS ie: dig @206.168.216.6 mx gmail.com, I g
Thanks Lyle,
You're right - I started using the host command because it was giving me the
error I found in the postfix logs...
but as I just discovered dig +trace also give me the error...
I am seeing lots of mailed messages to gmail accounts... and when I do a trace
I get the following:
; <<>
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 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
On Wed, 2 May 2012, Paul Marais wrote:
> 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 rec
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
12 matches
Mail list logo
