On 12/30/10 3:04 PM, Lightner, Jeff wrote:
If qmail is open source then YOU can patch it to your heart's content
and might even want to fork the project so you're maintaining it for
others.
Expecting BIND to hold itself back or patch itself for 1998 standards is
a bit like expecting people that
On Thu, 2010-12-30 at 22:42 +0100, Lazy wrote:
> 2010/12/30 Tony Finch :
> > On 30 Dec 2010, at 19:56, Lazy wrote:
> >>
> >> qmail uses ANY so m$ is not getting any mail from us
> >
> > This is several bugs in qmail. It is making the query in order to
> > canonicalize the domain in outgoing emai
lf
Of Lazy
Sent: Thursday, December 30, 2010 4:42 PM
To: bind-users@lists.isc.org
Subject: Re: bind 9.7.2-P3 does not resolve www.microsoft.com
2010/12/30 Tony Finch :
> On 30 Dec 2010, at 19:56, Lazy wrote:
>>
>> qmail uses ANY so m$ is not getting any mail from us
>
> This is
2010/12/30 Tony Finch :
> On 30 Dec 2010, at 19:56, Lazy wrote:
>>
>> qmail uses ANY so m$ is not getting any mail from us
>
> This is several bugs in qmail. It is making the query in order to
> canonicalize the domain in outgoing email, which it does not need to do
> according to the current SM
On 30 Dec 2010, at 19:56, Lazy wrote:
>
> qmail uses ANY so m$ is not getting any mail from us
This is several bugs in qmail. It is making the query in order to canonicalize
the domain in outgoing email, which it does not need to do according to the
current SMTP specs. It should be making an M
2010/12/30 :
> Zitat von Lazy :
>
>> 2010/12/30 Lazy :
>>>
>>> 2010/12/28 Dennis Clarke :
>> trying to resolve www.microsoft.com or microsoft.com results in a
>> "connection timed out; no servers could be reached"
>
> Well, for what it's worth - it's not just you having that i
Le jeudi 30 décembre 2010 à 20:29 +0100, lst_ho...@kwsoft.de a écrit :
> Zitat von Lazy :
>
> > 2010/12/30 Lazy :
> >> 2010/12/28 Dennis Clarke :
> >>>
> > trying to resolve www.microsoft.com or microsoft.com results in a
> > "connection timed out; no servers could be reached"
>
> >>
Zitat von Lazy :
2010/12/30 Lazy :
2010/12/28 Dennis Clarke :
trying to resolve www.microsoft.com or microsoft.com results in a
"connection timed out; no servers could be reached"
Well, for what it's worth - it's not just you having that issue. When
testing from home and from work I get th
2010/12/30 Lazy :
> 2010/12/28 Dennis Clarke :
>>
trying to resolve www.microsoft.com or microsoft.com results in a
"connection timed out; no servers could be reached"
>>>
>>> Well, for what it's worth - it's not just you having that issue. When
>>> testing from home and from work I get t
2010/12/28 Dennis Clarke :
>
>>> trying to resolve www.microsoft.com or microsoft.com results in a
>>> "connection timed out; no servers could be reached"
>>
>> Well, for what it's worth - it's not just you having that issue. When
>> testing from home and from work I get the same.
>>
>
> works fine
Dnia 2010-12-29 13:55 T. Wunderlich napisał(a):
>Thanks a lot for all your suggestions. I haven't found a solution yet, but
found something
>which got my attention:
>
>Have a look at the TTL of the following CNAME entries.
>
>What happens when the lookup lasts longer than those 57 seconds? Mayb
Thanks a lot for all your suggestions. I haven't found a solution yet, but
found something
which got my attention:
Have a look at the TTL of the following CNAME entries.
What happens when the lookup lasts longer than those 57 seconds? Maybe named
will get
in trouble then?
AND what do the RFC
Ok, trying to send the same email third time, maybe it will get to the right
recipient and with the right subject at last.
Damn webmail, damn trying to resend from thunderbird.
Dnia 2010-12-28 09:26 Eivind Olsen napisał(a):
>> >> trying to resolve www.microsoft.com or microsoft.com results in
Michael Sinatra wrote:
> On 12/28/10 06:07, Lightner, Jeff wrote:
>> It's working fine for me from RHEL5 Linux DNS servers and from Windows
>> DNS servers.
>
> It's not clear from this thread whether 'dig any microsoft.com
> @ns[12345].msft.net' works for anyone. I cannot get it to work from
> any
On 12/28/10 06:07, Lightner, Jeff wrote:
It's working fine for me from RHEL5 Linux DNS servers and from Windows
DNS servers.
It's not clear from this thread whether 'dig any microsoft.com
@ns[12345].msft.net' works for anyone. I cannot get it to work from any
of the msft.net servers on clien
On 12/28/10 00:26, Eivind Olsen wrote:
So, to recap: at the risk of showing what a fool I am by doing something
completely wrong here, I'm betting Microsoft has messed up their DNS - I
would have expected queries over TCP to work, and I would not have
expected EDNS to give a FORMERR (but ok, if
010 4:16 AM
To: bind-users@lists.isc.org
Subject: Re: bind 9.7.2-P3 does not resolve www.microsoft.com
> works fine for me on linux and Solaris.
In my case it's using FreeBSD and Solaris.
The problem might be related to where you do queries from?
Anyway, I tried some other nameservers / &
> works fine for me on linux and Solaris.
In my case it's using FreeBSD and Solaris.
The problem might be related to where you do queries from?
Anyway, I tried some other nameservers / "looking glass" sites, like these
- I can't vouch for how good they normally are, but these were ones I
found w
>> trying to resolve www.microsoft.com or microsoft.com results in a
>> "connection timed out; no servers could be reached"
>
> Well, for what it's worth - it's not just you having that issue. When
> testing from home and from work I get the same.
>
works fine for me on linux and Solaris.
--
> trying to resolve www.microsoft.com or microsoft.com results in a
> "connection timed out; no servers could be reached"
Well, for what it's worth - it's not just you having that issue. When
testing from home and from work I get the same.
Of course, I could be doing something wrong, but whenever
20 matches
Mail list logo
