3 ms·
Well somebody has screwed it up on their end. Only the www record is not resolving, a lot of the others are, for eg: http://developers.facebook.com/ http://dev
by bl4k 16y ago
Well somebody has screwed it up on their end. Only the www record is not resolving, a lot of the others are, for eg:
http://developers.facebook.com/ http://developers.facebook.com/
$ nslookup facebook.com ns1.facebook.com
Server: ns1.facebook.com
Address: 204.74.66.132#53
Name: facebook.com
Address: 69.63.189.11
Name: facebook.com
Address: 69.63.181.12
Name: facebook.com
Address: 69.63.189.16
$ nslookup www.facebook.com ns1.facebook.com
Server: ns1.facebook.com
Address: 204.74.66.132#53
Non-authoritative answer:
*** Can't find www.facebook.com: No answer
(YMMV based on local cache etc.)
- deleted 16y ago[deleted]
- jamii 16y agoHilariously touch.facebook.com still seems to work.
- klochner 16y agoI imagine that would be a relatively easy fix, more likely they took the record down to debug internally without getting flooded with requests.
- bl4k 16y agoIt looks like you were right - they dropped that record to stop the requests coming in