From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] Buildroot 2012.02-rc3 released
Date: Thu, 1 Mar 2012 00:17:12 +0000 [thread overview]
Message-ID: <201203010017.12296.arnout@mind.be> (raw)
In-Reply-To: <CAJJ6jxv1JvMsK7pMgQJ85DHDiz=on8zO3Mux0KigJHpq-a3_ZQ@mail.gmail.com>
On Wednesday 29 February 2012 23:48:36 Steve Calfee wrote:
> Both systems sit on a NAT LAN with 192.168* ip addresses. I don't know
> if that affects things, shouldn't.
It will. The DNS on the NAT will cache the authoritive server for
uclibc.org. If the original uclibc.org DNS server still replies to DNS
requests, but doesn't give answers for uclibc.org addresses, then the NAT
will not look further. You can verify this by issuing
host -v -t SOA uclibc.org
which should reply
uclibc.org. 86125 IN SOA ns1.auth.osuosl.org. hostmaster.osuosl.org. 1330554603 300 900 604800 86400
but will probably reply with the old DNS server.
There is unfortunately no way to force your NAT to forget the cached
record. You can try to NOT access any uclibc.org site for 48 hours,
which may expire the cache.
To fix it, something must be done at the old DNS server. I don't know
what needs to be done exactly.
Regards,
Arnout
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286540
Essensium/Mind http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint: 7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F
next prev parent reply other threads:[~2012-03-01 0:17 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <RT-Ticket-20368@osuosl.org>
2012-02-27 16:10 ` [Buildroot] Buildroot 2012.02-rc3 released Peter Korsgaard
2012-02-28 19:27 ` Steve Calfee
2012-02-29 7:22 ` Peter Korsgaard
2012-02-29 7:43 ` Thomas De Schampheleire
2012-02-29 15:54 ` Steve Calfee
2012-02-29 16:01 ` Peter Korsgaard
2012-02-29 16:04 ` Michael S. Zick
2012-02-29 16:22 ` Steve Calfee
2012-02-29 22:24 ` Chris Kerios
2012-02-29 23:37 ` Yann E. MORIN
2012-02-29 23:48 ` Steve Calfee
2012-02-29 23:57 ` Chris Kerios
2012-03-01 0:17 ` Arnout Vandecappelle [this message]
2012-03-01 0:40 ` Chris Kerios
2012-03-01 0:52 ` Steve Calfee
2012-03-01 1:00 ` Arnout Vandecappelle
2012-03-01 1:47 ` Steve Calfee
2012-03-01 3:44 ` Steve Calfee
2012-03-04 16:01 ` Steve Calfee
2012-03-04 16:50 ` Michael S. Zick
2012-03-04 17:06 ` Steve Calfee
[not found] ` <87mx7wwb4u.fsf@macbook.be.48ers.dk>
[not found] ` <rt-3.6.3-2614-1330988102-1965.20368-6-0@osuosl.org>
2012-03-06 17:16 ` [Buildroot] [support.osuosl.org #20368] " Steve Calfee
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=201203010017.12296.arnout@mind.be \
--to=arnout@mind.be \
--cc=buildroot@busybox.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