Re: compile airport, dual boot

[Michael Schmitz <schmitz@mail.biophys.uni-duesseldorf.de>]

> I wondered what had happened.  I'm seeing the same thing.  I've
> tried from several networks:
> 
> 
> bash-2.03$ nslookup www.linuxppc.org
> Server:  dns1.gallup.com
> Address:  198.175.140.220
> 
> Non-authoritative answer:
> Name:    www.linuxppc.org
> Address:  169.207.161.4
> 
> bash-2.03$ nslookup www.linuxppc.com
> Server:  dns1.gallup.com
> Address:  198.175.140.220
> 
> Name:    www.linuxppc.com
> Address:  169.207.161.4

Try the same with the authoritative name server for each domain
(ns2.socomm.net for penguinppc.org, E0.NS.VOYAGER.NET for linuxppc.com and
apparently linuxppc.org). They all know the right answers (except
voyager.net refusing to answer penguinppc.org queries). The DNS on
www.linuxppc.com seems a bit broken (replies SOA on NS queries), and the
whole setup to have linuxppc.com's DNS send authoritative data about
linuxppc.org is a bit strange, but there's been stranger things. 

%: nslookup
> lserver NS0.MEMEDYNE.COM
Default Server:  NS0.MEMEDYNE.COM
Address:  216.166.138.220

> www.linuxppc.org
Server:  NS0.MEMEDYNE.COM
Address:  216.166.138.220

Non-authoritative answer:
Name:    www.linuxppc.org
Address:  169.207.161.4

> www.linuxppc.com
Server:  NS0.MEMEDYNE.COM
Address:  216.166.138.220

Name:    www.linuxppc.com
Address:  169.207.161.4

> www.penguinppc.org
Server:  NS0.MEMEDYNE.COM
Address:  216.166.138.220

Non-authoritative answer:
Name:    www.penguinppc.org
Address:  206.160.138.11

It seems your own provider is to blame. 

	Michael