BIND DNS estranho comportamento resolvendo dns

2

CentOS 6.3 Versão 9.8.2 do BIND

O servidor está agindo como o servidor DNS da minha rede local.

O que acontece é que eu posso resolver o jquery.com muito bem, mas acessar o code.jquery.com resulta em nada encontrado ao consultar do localhost.

dig jquery.com

; <<>> DiG 9.8.2rc1-RedHat-9.8.2-0.10.rc1.el6_3.5 <<>> jquery.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 38326
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 6, ADDITIONAL: 6

;; QUESTION SECTION:
;jquery.com.                    IN      A

;; ANSWER SECTION:
jquery.com.             3600    IN      A       70.32.120.34

;; AUTHORITY SECTION:
jquery.com.             168983  IN      NS      ns11.dnsmadeeasy.com.
jquery.com.             168983  IN      NS      ns14.dnsmadeeasy.com.
jquery.com.             168983  IN      NS      ns13.dnsmadeeasy.com.
jquery.com.             168983  IN      NS      ns15.dnsmadeeasy.com.
jquery.com.             168983  IN      NS      ns10.dnsmadeeasy.com.
jquery.com.             168983  IN      NS      ns12.dnsmadeeasy.com.

;; ADDITIONAL SECTION:
ns10.dnsmadeeasy.com.   84449   IN      A       208.94.148.4
ns11.dnsmadeeasy.com.   84449   IN      A       208.80.124.4
ns12.dnsmadeeasy.com.   84449   IN      A       208.80.126.4
ns13.dnsmadeeasy.com.   84449   IN      A       208.80.125.4
ns14.dnsmadeeasy.com.   84449   IN      A       208.80.127.4
ns15.dnsmadeeasy.com.   84449   IN      A       208.94.149.4

;; Query time: 75 msec
;; SERVER: 127.0.0.1#53(127.0.0.1)
;; WHEN: Tue Oct 30 11:09:55 2012
;; MSG SIZE  rcvd: 266

Então:

dig code.jquery.com

; <<>> DiG 9.8.2rc1-RedHat-9.8.2-0.10.rc1.el6_3.5 <<>> code.jquery.com
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 12717
;; flags: qr rd ra; QUERY: 1, ANSWER: 3, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;code.jquery.com.               IN      A

;; ANSWER SECTION:
code.jquery.com.        43118   IN      CNAME   wac.1257.edgecastcdn.net.
wac.1257.edgecastcdn.net. 3518  IN      CNAME   ne.wac.edgecastcdn.net.
ne.wac.edgecastcdn.net. 3518    IN      A       93.184.220.20

;; Query time: 80 msec
;; SERVER: 8.8.8.8#53(8.8.8.8)
;; WHEN: Tue Oct 30 11:10:45 2012
;; MSG SIZE  rcvd: 108

Então:

    dig jquery.com @localhost

    ; <<>> DiG 9.8.2rc1-RedHat-9.8.2-0.10.rc1.el6_3.5 <<>> jquery.com @localhost
    ;; global options: +cmd
    ;; Got answer:
    ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 10420
    ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 6, ADDITIONAL: 6

    ;; QUESTION SECTION:
    ;jquery.com.                    IN      A

    ;; ANSWER SECTION:
    jquery.com.             3501    IN      A       70.32.120.34

    ;; AUTHORITY SECTION:
    jquery.com.             168884  IN      NS      ns12.dnsmadeeasy.com.
    jquery.com.             168884  IN      NS      ns10.dnsmadeeasy.com.
    jquery.com.             168884  IN      NS      ns14.dnsmadeeasy.com.
    jquery.com.             168884  IN      NS      ns13.dnsmadeeasy.com.
    jquery.com.             168884  IN      NS      ns15.dnsmadeeasy.com.
    jquery.com.             168884  IN      NS      ns11.dnsmadeeasy.com.

    ;; ADDITIONAL SECTION:
    ns10.dnsmadeeasy.com.   84350   IN      A       208.94.148.4
    ns11.dnsmadeeasy.com.   84350   IN      A       208.80.124.4
    ns12.dnsmadeeasy.com.   84350   IN      A       208.80.126.4
    ns13.dnsmadeeasy.com.   84350   IN      A       208.80.125.4
    ns14.dnsmadeeasy.com.   84350   IN      A       208.80.127.4
    ns15.dnsmadeeasy.com.   84350   IN      A       208.94.149.4

    ;; Query time: 0 msec
    ;; SERVER: 127.0.0.1#53(127.0.0.1)
    ;; WHEN: Tue Oct 30 11:11:34 2012
    ;; MSG SIZE  rcvd: 266

E este é o pouco que estou perplexo:

    dig code.jquery.com @localhost

    ; <<>> DiG 9.8.2rc1-RedHat-9.8.2-0.10.rc1.el6_3.5 <<>> code.jquery.com @localhost
    ;; global options: +cmd
    ;; connection timed out; no servers could be reached
    
por pixel_paul 30.10.2012 / 12:18

1 resposta

0

Sua ligação local, por algum motivo, não pode acessar o edgecastcdn.net. Enquanto o google pode alcançá-los. tente dig @localhost edgecastcdn.net e dig @ns1.edgecastcdn.net edgecastcdn.net - você provavelmente obterá as mesmas mensagens de tempo limite.

Pode ser o problema de configuração incorreta ou o efeito colateral de algum ataque DDOS no edgecastcdn.net ou algo assim.

    
por 30.10.2012 / 15:06

Tags