On Thu, 27 Oct 2011 07:04:42 +0200, Emanuele Balla (aka Skull) wrote:
TCP is needed only when replies do not fit 512 bytes (let's ignore
EDNS0
and such). For any DNSBL, this limit is not a problem at all.
its was edns0 defaults that maked most problems, from my logs it seem
more stable now, h
On 10/23/11 5:42 AM, Benny Pedersen wrote:
> On Sat, 22 Oct 2011 22:34:48 -0500, Larry Brower wrote:
>>> can i control this pr zone when bind is dns client ?
>> Why would you want to? Just fix the problem.
>
> ask dnsbl owners to stop using rbldnsd ?
No point and no need for that.
TCP is needed o
Kevin wrote on 10/22/2011 11:42:08 PM:
> > remote server is rbldnsd with is not supporting tcp, how to solve this
?
>
> You have a badly broken DNS if it does not support TCP. You need to
> fix this. Anything else is a band-aid that will just keep breaking
> things.
If it is a general purpose D
On Sun, Oct 23, 2011 at 6:43 AM, Benny Pedersen wrote:
> On Sun, 23 Oct 2011 13:56:21 +1000, Noel Butler wrote:
>>
>> I think you have something broken, bind uses UDP by default, if
>> it can not connect to a dns server on UDP it then retries on TCP.
>>
>> It also uses TCP for AXFR's
>
> correct,
On Sun, 23 Oct 2011 13:56:21 +1000, Noel Butler wrote:
I think you have something broken, bind uses UDP by default, if
it can not connect to a dns server on UDP it then retries on TCP.
It also uses TCP for AXFR's
correct, its not my problem how axfr works, as i have sleeped on it
now, got th
I think you have something broken, bind uses UDP by default, if it can
not connect to a dns server on UDP it then retries on TCP.
It also uses TCP for AXFR's
On Sun, 2011-10-23 at 05:50 +0200, Benny Pedersen wrote:
> On Sat, 22 Oct 2011 20:42:08 -0700, Kevin Oberman wrote:
> > On Sat, Oct 22, 20
On Sat, 22 Oct 2011 20:42:08 -0700, Kevin Oberman wrote:
On Sat, Oct 22, 2011 at 8:24 PM, Benny Pedersen wrote:
can i control this pr zone when bind is dns client ?
remote server is rbldnsd with is not supporting tcp, how to solve
this ?
You have a badly broken DNS if it does not support TCP
On Sat, Oct 22, 2011 at 8:24 PM, Benny Pedersen wrote:
> can i control this pr zone when bind is dns client ?
>
> remote server is rbldnsd with is not supporting tcp, how to solve this ?
You have a badly broken DNS if it does not support TCP. You need to
fix this. Anything else is a band-aid that
On Sat, 22 Oct 2011 22:34:48 -0500, Larry Brower wrote:
can i control this pr zone when bind is dns client ?
Why would you want to? Just fix the problem.
ask dnsbl owners to stop using rbldnsd ?
remote server is rbldnsd with is not supporting tcp, how to solve
this ?
Use a server that is sa
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 10/22/2011 10:24 PM, Benny Pedersen wrote:
> can i control this pr zone when bind is dns client ?
>
Why would you want to? Just fix the problem.
> remote server is rbldnsd with is not supporting tcp, how to solve this ?
Use a server that is san
can i control this pr zone when bind is dns client ?
remote server is rbldnsd with is not supporting tcp, how to solve this
?
___
Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe
from this list
bind-users mailing list
bi
11 matches
Mail list logo