[150880] in North American Network Operators' Group
Re: facebook lost their A-record for www.facebook.com?
daemon@ATHENA.MIT.EDU (Anurag Bhatia)
Wed Mar 7 03:52:54 2012
In-Reply-To: <op.wasioen94oyyg1@localhost.localdomain>
Date: Wed, 7 Mar 2012 14:21:54 +0530
From: Anurag Bhatia <me@anuragbhatia.com>
To: Octavio Alvarez <alvarezp@alvarezp.ods.org>
Cc: NANOG Mailing List <nanog@nanog.org>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
Good point Octavio . +trace with dig is always useful when getting weird
results.
(Sent from my mobile device)
Anurag Bhatia
http://anuragbhatia.com
On Mar 7, 2012 1:19 PM, "Octavio Alvarez" <alvarezp@alvarezp.ods.org> wrote:
> On Tue, 06 Mar 2012 23:43:07 -0800, Igor Ybema <igor@ergens.org> wrote:
>
> [igor@vds ~]$ host -t A www.facebook.com ns1.facebook.com
>> Using domain server:
>> Name: ns1.facebook.com
>> Address: 204.74.66.132#53
>> Aliases:
>>
>> www.facebook.com has no A record
>>
>
> No, it's a subdomain with its A records in another server.
>
> $ host -t A www.facebook.com glb1.facebook.com.
> Using domain server:
> Name: glb1.facebook.com.
> Address: 69.171.239.10#53
> Aliases:
>
> www.facebook.com has address 69.171.224.12
>
>
> Try dig +trace www.facebook.com to see why.
>
>
>
> --
> Octavio.
>
> Twitter: @alvarezp2000 -- Identi.ca: @alvarezp
>
>
