From: orc <orc@sibserver.ru>
To: musl@lists.openwall.com
Subject: Re: dn_expand() confuses postfix
Date: Sun, 25 Aug 2013 16:42:20 +0800 [thread overview]
Message-ID: <20130825164220.2801654a@sibserver.ru> (raw)
In-Reply-To: <20130825064321.GT20515@brightrain.aerifal.cx>
On Sun, 25 Aug 2013 02:43:21 -0400
Rich Felker <dalias@aerifal.cx> wrote:
> On Thu, Aug 15, 2013 at 02:14:22PM +0800, orc wrote:
> > Other issue now:
> >
> > ../test_dns_lookup: lookup yandex.ru type MX flags 2
> > ../test_dns_lookup: dns_query: yandex.ru (MX): OK
> > ../test_dns_lookup: warning: valid_hostname: invalid character
> > 6(decimal): ?yande.?r ../test_dns_lookup: warning: malformed domain
> > name in resource name of MX record
> > for ?yande.?r: ?yande.?r ../test_dns_lookup: fatal: Name service
> > error for name=yandex.ru type=MX: Malformed or unexpected name
> > server reply
> >
> > ../test_dns_lookup: lookup ya.ru type MX flags 2
> > ../test_dns_lookup: dns_query: ya.ru (MX): OK
> > ../test_dns_lookup: warning: valid_hostname: invalid character
> > 2(decimal): ?y.?r ../test_dns_lookup: warning: malformed domain
> > name in resource name of MX record
> > for ?y.?r: ?y.?r ../test_dns_lookup: fatal: Name service error for
> > name=ya.ru type=MX: Malformed or unexpected name server reply
> >
> > temp buffer at src/dns/dns_lookup.c:287 is messed up with these.
>
> I believe this was actually a nasty regression in the dn_expand "fix"
> -- somehow I thought my tests were checking reverse dns, but they
> weren't, and the new code actually had a bad off-by-one error. It
> should be fixed now. Let me know if you're still experiencing
> problems.
>
> Rich
Yes, it works now. Thanks!
% ./test_dns_lookup mx google.com
./test_dns_lookup: lookup google.com type MX flags 2
./test_dns_lookup: dns_query: google.com (MX): OK
./test_dns_lookup: dns_get_answer: type MX for google.com
./test_dns_lookup: dns_get_answer: type MX for google.com
./test_dns_lookup: dns_get_answer: type MX for google.com
./test_dns_lookup: dns_get_answer: type MX for google.com
./test_dns_lookup: dns_get_answer: type MX for google.com
google.com: fqdn: google.com
google.com: ttl: 600 pref: 50 MX: alt4.aspmx.l.google.com
google.com: ttl: 600 pref: 40 MX: alt3.aspmx.l.google.com
google.com: ttl: 600 pref: 20 MX: alt1.aspmx.l.google.com
google.com: ttl: 600 pref: 10 MX: aspmx.l.google.com
google.com: ttl: 600 pref: 30 MX: alt2.aspmx.l.google.com
% ./test_dns_lookup mx ya.ru
./test_dns_lookup: lookup ya.ru type MX flags 2
./test_dns_lookup: dns_query: ya.ru (MX): OK
./test_dns_lookup: dns_get_answer: type MX for ya.ru
ya.ru: fqdn: ya.ru
ya.ru: ttl: 6580 pref: 10 MX: mx.yandex.ru
prev parent reply other threads:[~2013-08-25 8:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-13 18:19 orc
2013-08-13 18:38 ` Rich Felker
2013-08-13 19:09 ` orc
2013-08-13 20:36 ` Rich Felker
2013-08-14 22:06 ` Rich Felker
2013-08-15 6:14 ` orc
2013-08-15 6:36 ` Rich Felker
2013-08-25 6:43 ` Rich Felker
2013-08-25 8:42 ` orc [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20130825164220.2801654a@sibserver.ru \
--to=orc@sibserver.ru \
--cc=musl@lists.openwall.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/musl/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).