[Buildroot] Buildroot 2012.02-rc3 released

[Steve Calfee <stevecalfee@gmail.com>]

On 02/29/2012 05:47 PM, Steve Calfee wrote:
> On Wed, Feb 29, 2012 at 5:00 PM, Arnout Vandecappelle<arnout@mind.be>  wrote:
>> On Thursday 01 March 2012 00:52:20 Steve Calfee wrote:
>>> On Wed, Feb 29, 2012 at 4:17 PM, Arnout Vandecappelle<arnout@mind.be>  wrote:
>>>> 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.
>>>>
>>> I did what you suggested, But I don't know if the differences are important:
>>> me:~$ host -v -t SOA uclibc.org
>>> Trying "uclibc.org"
>>> ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 64103
>>> ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1
>>>
>>> ;; QUESTION SECTION:
>>> ;uclibc.org.                  IN      SOA
>>>
>>> ;; ANSWER SECTION:
>>> uclibc.org.           86400   IN      SOA     ns1.auth.osuosl.org. hostmaster.osuosl.org.
>>> 1330554603 300 900 604800 86400
>>>
>>> ;; ADDITIONAL SECTION:
>>> ns1.auth.osuosl.org.  67451   IN      A       140.211.166.140
>>>
>>> Received 107 bytes from 192.168.3.31#53 in 305 ms
>>   That looks OK though...  So my explanation has some flaws :-)
>>
>>   What does host -v -t SOA git.buildroot.net tell you?
>>
>> Trying "git.buildroot.net"
>> ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 44693
>> ;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 1, ADDITIONAL: 0
>>
>> ;; QUESTION SECTION:
>> ;git.buildroot.net.             IN      SOA
>>
>> ;; ANSWER SECTION:
>> git.buildroot.net.      36219   IN      CNAME   buildroot.uclibc.org.
>> buildroot.uclibc.org.   79420   IN      CNAME   www.uclibc.org.
>>
>> ;; AUTHORITY SECTION:
>> uclibc.org.             10664   IN      SOA     ns1.auth.osuosl.org. hostmaster.osuosl.org. 1330554603 300 900 604800 86400
>>
>> Received 150 bytes from 192.168.22.22#53 in 70 ms
>>
>> --
> Hi Arnout, thanks for trying to help. Here is my screen:
>
> me:~$ host -v -t SOA git.buildroot.net
> Trying "git.buildroot.net"
> ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 36106
> ;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 1
>
> ;; QUESTION SECTION:
> ;git.buildroot.net.		IN	SOA
>
> ;; ANSWER SECTION:
> git.buildroot.net.	21181	IN	CNAME	buildroot.uclibc.org.
> buildroot.uclibc.org.	86400	IN	SOA	ns1.auth.osuosl.org.
> hostmaster.osuosl.org. 1330554603 300 900 604800 86400
>
> ;; ADDITIONAL SECTION:
> ns1.auth.osuosl.org.	64383	IN	A	140.211.166.140
>
> Received 148 bytes from 192.168.3.31#53 in 93 ms
>
> I don't see anything obviously weird, but the link
> (http://git.buildroot.net/buildroot/plain/CHANGES?id=2012.02_rc3)
> still does not work.
>
> Wait, I just tried git and it now will fetch, and now I tried that
> link again and it works now. So either magic happened or someone,
> somewhere in DNS land fixed it.
>
> So for me, for now, from work this is fixed!
>
> Thanks, Steve
Hi all from DNS land.

I took the laptop home to the att uverse network, and I still cannot get 
through. I even went though the host query commands with similar 
results. Just git fetch and the git.buildroot.net link still fail.

Regards, Steve