DNS request timed out

512 views
Skip to first unread message

jeanetienne...@gmail.com

unread,
Aug 15, 2016, 3:31:57 PM8/15/16
to public-dns-discuss
I have switched IP and server from some domains. Yesterday I turned off the old server.

After more than 24h some domains still don't resolve using the Google public DNS servers. Using any other servers they resolve fine.
I followed the diagnosing resolution problems steps successfully. Everything seems fine. I also tried to flush the cache from Google page.
I made sure the firewall was not blocking Google IP, etc.

Any clue?

The domain is blaeckskateboardwheels.us

nslookup -debug blaeckskateboardwheels.us. 8.8.8.8
------------
Got answer:
    HEADER:
        opcode = QUERY, id = 1, rcode = NOERROR
        header flags:  response, want recursion, recursion avail.
        questions = 1,  answers = 1,  authority records = 0,  additional = 0

    QUESTIONS:
        8.8.8.8.in-addr.arpa, type = PTR, class = IN
    ANSWERS:
    ->  8.8.8.8.in-addr.arpa
        name = google-public-dns-a.google.com
        ttl = 21098 (5 hours 51 mins 38 secs)

------------
Server:  google-public-dns-a.google.com
Address:  8.8.8.8

DNS request timed out.
    timeout was 2 seconds.
timeout (2 secs)
DNS request timed out.
    timeout was 2 seconds.
timeout (2 secs)
*** Request to google-public-dns-a.google.com timed-out

Alex Dupuy

unread,
Aug 15, 2016, 3:42:52 PM8/15/16
to public-dns-discuss
Because your name servers are named within the domain itself, you need to update the glue records for ns1.blaeckskateboardwheels.us and ns2.blaeckskateboardwheels.us—it would also be a very good idea to have more than one nameserver (ideally in multiple locations). Giving the same IP address for both name servers will "satisfy" the .US registry and your registrar, but you will likely not be satisfied with the (lack of) reliability.

If 64.140.156.46 is the correct name server IP address, then you need to fix the name server as it is not responding either to our resolvers, or queries from other locations:


; <<>> DiG 9.10.2 <<>> ns blaeckskateboardwheels.us @a.cctld.us.
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 36414
;; flags: qr rd; QUERY: 1, ANSWER: 0, AUTHORITY: 2, ADDITIONAL: 3
;; WARNING: recursion requested but not available

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:

;; AUTHORITY SECTION:
BLAECKSKATEBOARDWHEELS.us. 7200 IN NS NS2.BLAECKSKATEBOARDWHEELS.us.
BLAECKSKATEBOARDWHEELS.us. 7200 IN NS NS1.BLAECKSKATEBOARDWHEELS.us.

;; ADDITIONAL SECTION:
NS1.BLAECKSKATEBOARDWHEELS.us. 7200 IN A 64.140.156.46
NS2.BLAECKSKATEBOARDWHEELS.us. 7200 IN A 64.140.156.46

;; Query time: 1 msec
;; SERVER: 156.154.124.70#53(156.154.124.70)
;; WHEN: Mon Aug 15 15:37:06 EDT 2016
;; MSG SIZE  rcvd: 145


; <<>> DiG 9.10.2 <<>> ns blaeckskateboardwheels.us @64.140.156.46
;; global options: +cmd
;; connection timed out; no servers could be reached

Reply all
Reply to author
Forward
0 new messages