Google Public DNS blocks wikileaks.org (Update: No, they don’t)

It seems that Google is blocking wikileaks.org in its ‘Public DNS’ servers (8.8.8.8 and 8.8.4.4):

; <<>> DiG 9.7.1-P2 <<>> @8.8.8.8 wikileaks.org ; (1 server found) ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 50227 ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0 ;; QUESTION SECTION: ;wikileaks.org. IN A ;; Query time: 2457 msec ;; SERVER: 8.8.8.8#53(8.8.8.8) ;; WHEN: Fri Aug 27 18:10:43 2010 ;; MSG SIZE rcvd: 31

Update: Sorry Google, for me doubting you. As it turns out, you did no evil, you were just a bit slower than the others.

16 thoughts on “Google Public DNS blocks wikileaks.org (Update: No, they don’t)

  1. …or s1.dynadot.com and s2.dynadot.com which are responsible for resolving wikileaks.org are just down.
    Please make sure you know what you’re writing about.

      1. “everywhere else” seems to exclude at least two providers in Germany which served no answer five minutes ago either. One of them just gave me an answer, so most likely just some caching issue with the NS record (which seems to have switched recently).

  2. google’s dns servers are anycasted – so the instance you talk to could have had a temporary failure right after the ttl for wikileaks expired (it’s only about 15min). it’s working from whatever instance im talking to

  3. Not in peru, maybe in the US:

    buster$ dig wikileaks.org

    ; <> DiG 9.7.1-P2 <> wikileaks.org
    ;; global options: +cmd
    ;; Got answer:
    ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 65369
    ;; flags: qr rd ra; QUERY: 1, ANSWER: 4, AUTHORITY: 0, ADDITIONAL: 0

    ;; QUESTION SECTION:
    ;wikileaks.org. IN A

    ;; ANSWER SECTION:
    wikileaks.org. 545 IN A 88.80.17.18
    wikileaks.org. 545 IN A 88.80.17.21
    wikileaks.org. 545 IN A 88.80.17.21
    wikileaks.org. 545 IN A 88.80.17.18

    ;; Query time: 105 msec
    ;; SERVER: 8.8.8.8#53(8.8.8.8)
    ;; WHEN: Fri Aug 27 13:23:54 2010
    ;; MSG SIZE rcvd: 95

    buster$ cat /etc/resolv.conf
    # Generated by NetworkManager
    nameserver 8.8.8.8
    nameserver 8.8.4.4

  4. dig wikileaks.org

    ; <> DiG 9.7.0-P1 <> wikileaks.org
    ;; global options: +cmd
    ;; Got answer:
    ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 10950
    ;; flags: qr rd ra; QUERY: 1, ANSWER: 4, AUTHORITY: 0, ADDITIONAL: 0

    ;; QUESTION SECTION:
    ;wikileaks.org. IN A

    ;; ANSWER SECTION:
    wikileaks.org. 640 IN A 88.80.17.18
    wikileaks.org. 640 IN A 88.80.17.21
    wikileaks.org. 640 IN A 88.80.17.21
    wikileaks.org. 640 IN A 88.80.17.18

    ;; Query time: 98 msec
    ;; SERVER: 208.67.222.222#53(208.67.222.222)
    ;; WHEN: Fri Aug 27 13:34:02 2010
    ;; MSG SIZE rcvd: 95

  5. could plz someone explain this to a non-tech? in a part of central europe the site is available.

    what exactly does this refer to. if to the “maintenance”, could plz someone verify this?

    cooperation us military/companies in more direct and official ways were planned to start on oct 1st, wasn’t it?

    http://shortlinks.de/5p75

    1. update / correction – “maintenance” can’t be meant – (“WHEN: Fri Aug 27 18:10:43 2010”) – so, yesterday, aug 27th…

      what’s going on, plz. where exactly is the page blocked right now. any details, plz?

  6. both `dig @8.8.8.8 wikileaks.org` and `dig @8.8.4.4 wikileaks.org` are reporting accurate results back in the UK

  7. hm what – btw – could block the wl twitter account? (“atom bomb hits sweden. server down now for 5 days according to twitter” – tomorrow on CNN…)

  8. “could plz someone explain this to a non-tech?”

    Never attribute to malice that which can be adequately explained by incompetence.

Comments are closed.