From: Jeff Sickel <jas@corpus-callosum.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] dns vs. textrr
Date: Thu, 19 Jan 2012 11:00:51 -0600 [thread overview]
Message-ID: <87B8E7AD-7956-4F2F-8F59-566651922EED@corpus-callosum.com> (raw)
In-Reply-To: <3456bc974ba7b432c1e61cb5a5492314@ladd.quanstro.net>
Haven't seen it. But it does seem that a lot of us
are having fun with dns this week (and every week).
Mine's more the problem of
ndb/dns -sx /net.alt -f /lib/ndb/external
configuration and properly getting it a resolver
from a subsequent dns= tuple. One day I'll remember
to keep it simple and just have everything in /net
and learn to manage the bridging between networks.
-jas
On Jan 19, 2012, at 10:01 AM, erik quanstrom wrote:
> a long text record seems to be causing lookup
> failures for other records. with the record
> below in /lib/ndb/external, lookups for mx.coraid.com
> fail. with just that line deleted, lookups work again.
> older versions of dns don't seem to have that problem.
>
> i was wondering if anyone had seen this?
>
> - erik
>
> ----
>
> dom=m1._domainkey.coraid.com txtrr="k=rsa; p=MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQDFUlNZvtGDlIGDRtzyRQydM9yRInD5YMx86QpgZ3v7pT+Mx4tGbjUxY41TXbsp7UH9hTREaKKGQKNM/B3FzcFVv4zafZ09lUaXcbSdtD70iXyH0OXEGXLZI5gG0ZwjK5ptgQ18d+pUP9s8xMkJnZlubTk9MLvQnv3ZBzoL9FHFDQIDAQAB"
>
>
>
next prev parent reply other threads:[~2012-01-19 17:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-19 16:01 erik quanstrom
2012-01-19 17:00 ` Jeff Sickel [this message]
2012-01-19 17:17 ` erik quanstrom
2012-01-19 22:12 ` erik quanstrom
2012-01-19 23:32 ` Lyndon Nerenberg
2012-01-19 23:56 ` erik quanstrom
2012-01-20 0:11 ` Lyndon Nerenberg
2012-01-20 0:14 ` erik quanstrom
2012-01-20 0:39 ` Lyndon Nerenberg
2012-01-20 6:31 ` Jeff Sickel
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=87B8E7AD-7956-4F2F-8F59-566651922EED@corpus-callosum.com \
--to=jas@corpus-callosum.com \
--cc=9fans@9fans.net \
/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.
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).