9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Lucio De Re <lucio.dere@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Flakey DNS server
Date: Wed, 7 Oct 2020 06:08:09 +0200	[thread overview]
Message-ID: <CAJQ9t7iEfHbinBjU7+xXiHgpYNFfj_dO+nrnCk+cs6imjv2tTA@mail.gmail.com> (raw)

It would take me a long time to get to grips with the Plan 9 DNS
server (believe me, I've tried) and somehow my situation is getting
more difficult as norms on the Internet are being bent by service
provider that care for their profitability much more than for
interoperation: I get regular failures that bring my connection to the
Internet to a halt in unpredictable ways.

That may be due to a complicated network database, possibly with
errors in it, but fixing that is also a mission I don't wish to get
stuck into.

Short-cut: 9front's dns server has undergone many changes from the
Bell Labs sources I have on my production system , while 9legacy, at a
glance, does not report any "dns" patches; my faith in Cinap is that
he's likely to have applied sensible fixes (assuming it's his work,
feel free to correct me).

Chances are 9front ndb/dns binary will work OK on my system, but I
have in fact compiled the 9front sources in the Bell Labs context and
only a minor warning was reported.

So the big question, before I commit to something I may not be
competent to fix: what is recommended by those in the know?

Lucio.

             reply	other threads:[~2020-10-07  4:08 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-07  4:08 Lucio De Re [this message]
2020-10-07 13:15 ` [9fans] " Wes Kussmaul
2020-10-07 16:14   ` Kurt H Maier
2020-10-08  0:45     ` Wes Kussmaul
2020-10-08  0:59       ` ori
2020-10-08  3:48         ` Lucio De Re
2020-10-08 10:54           ` Ethan Gardener
2020-10-08 12:48         ` Wes Kussmaul
2020-10-24 22:14   ` cigar562hfsp952fans
2020-10-24 22:48     ` [9fans] " Charles Forsyth
2020-10-24 23:01       ` Calvin Morrison
2020-10-25  2:09       ` Wes Kussmaul
2020-10-25 13:33         ` hiro
2020-10-25 16:43           ` Wes Kussmaul
2020-10-25 18:32             ` hiro
2020-10-25 18:38               ` Wes Kussmaul
2020-10-25 18:54                 ` hiro
2020-10-25 19:00                   ` Wes Kussmaul
2020-10-25 19:28                     ` hiro
2020-10-25 20:19                       ` Wes Kussmaul
2020-10-27  0:39         ` Thaddeus Woskowiak
2020-10-27  7:06           ` Lucio De Re
2020-10-28  3:18             ` ori
2020-10-27 14:51           ` Wes Kussmaul
2020-10-29  0:24         ` cigar562hfsp952fans
2020-10-08  0:58 ` [9fans] " ori
2020-10-08  3:29   ` Lucio De Re
2020-10-08 12:06     ` kvik

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=CAJQ9t7iEfHbinBjU7+xXiHgpYNFfj_dO+nrnCk+cs6imjv2tTA@mail.gmail.com \
    --to=lucio.dere@gmail.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).