How to trace a DNS lookup

We want to find an IP address for ws-mt1.pusher.com. We could use dig to ask a well-known DNS server like 8.8.8.8 for an A record:

$ dig @8.8.8.8 ws-mt1.pusher.com A

; <<>> DiG 9.8.3-P1 <<>> @8.8.8.8 ws-mt1.pusher.com A
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 34532
;; flags: qr rd ra; QUERY: 1, ANSWER: 3, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;ws-mt1.pusher.com.		IN	A

;; ANSWER SECTION:
ws-mt1.pusher.com.	43	IN	CNAME	edge106-mt1.pusher.com.
edge106-mt1.pusher.com.	7183	IN	CNAME	ec2-54-197-34-162.compute-1.amazonaws.com.
ec2-54-197-34-162.compute-1.amazonaws.com. 85534 IN A 54.197.34.162

;; Query time: 13 msec
;; SERVER: 8.8.8.8#53(8.8.8.8)
;; WHEN: Sun Aug 27 10:28:51 2017
;; MSG SIZE  rcvd: 129

Here, dig found that ws-mt1.pusher.com. is at address 54.197.34.162. dig found this with just one network round trip, because 8.8.8.8 has cached all the answers. This obscures how 8.8.8.8 knows the answer to the question. Instead of directly asking 8.8.8.8, we can follow the authority all the way from the root name servers. The dig tool has an option to do this, +trace:

+[no]trace:

Toggle tracing of the delegation path from the root name servers for the name being looked up. Tracing is disabled by default. When tracing is enabled, dig makes iterative queries to resolve the name being looked up. It will follow referrals from the root servers, showing the answer from each server that was used to resolve the lookup.

Let’s trace the delegation path for ws-mt1.pusher.com!

$ dig @8.8.8.8 +trace +question ws-mt1.pusher.com A

; <<>> DiG 9.8.3-P1 <<>> @8.8.8.8 +trace +question ws-mt1.pusher.com A
; (1 server found)
;; global options: +cmd
;.				IN	NS
.			170574	IN	NS	a.root-servers.net.
...
.			170574	IN	NS	f.root-servers.net.
...
;; Received 228 bytes from 8.8.8.8#53(8.8.8.8) in 31 ms

;ws-mt1.pusher.com.		IN	A
com.			172800	IN	NS	a.gtld-servers.net.
...
com.			172800	IN	NS	i.gtld-servers.net.
...
;; Received 495 bytes from 198.97.190.53#53(198.97.190.53) in 107 ms

;ws-mt1.pusher.com.		IN	A
pusher.com.		172800	IN	NS	ns-74.awsdns-09.com.
pusher.com.		172800	IN	NS	ns-703.awsdns-23.net.
...
;; Received 203 bytes from 192.43.172.30#53(192.43.172.30) in 21 ms

;ws-mt1.pusher.com.		IN	A
ws-mt1.pusher.com.	60	IN	CNAME	edge121-mt1.pusher.com.
edge121-mt1.pusher.com.	7200	IN	CNAME	ec2-54-236-213-148.compute-1.amazonaws.com.
...
;; Received 250 bytes from 205.251.194.191#53(205.251.194.191) in 309 ms

dig asks 8.8.8.8, “What are the name servers for the root zone, .”? 8.8.8.8 responds: “The name servers for . are a.root-servers.net., ...” dig arbitrarily picks f.root-servers.net., and resolves it to 198.97.190.53.
dig asks 198.97.190.53, “what are the addresss for ws-mt1.pusher.com.?” 198.97.190.53 responds: “I don’t know. Ask one of the name servers for com., which are: a.gtld-servers.net., ...” dig arbitrarily picks i.gtld-servers.net., and resolves it to 192.43.172.30.
dig asks 192.43.172.30, “what are the addresses for ws-mt1.pusher.com.?” 192.43.172.30 responds: “I don’t know. Ask one of the name servers for pusher.com., which are: ns-74.awsdns-09.com., ...” dig arbitrarily picks ns-703.awsdns-23.net., and resolves it to 205.251.194.191.
dig asks 205.251.194.191, “what are the addresses for ws-mt1.pusher.com.?” 205.251.194.191 responds: “I don’t know, but it’s the same as ec2-54-236-213-148.compute-1.amazonaws.com. - look that up instead.”

Notice that, even here, this is not the whole process! When a name server responds saying “the name server is i.gtld-servers.net.”, you then need to perform a recursive DNS subquery to find out an address for i.gtld-servers.net.. dig omits this detail here.

Also, our search for an address did not complete! The search finished with a CNAME, meaning we have to start all over again looking for the new name ec2-54-236-213-148.compute-1.amazonaws.com.! Let’s do that:

$ dig @8.8.8.8 +trace +question ec2-54-236-213-148.compute-1.amazonaws.com. A

; <<>> DiG 9.8.3-P1 <<>> @8.8.8.8 +trace +question ec2-54-236-213-148.compute-1.amazonaws.com. A
; (1 server found)
;; global options: +cmd
;.				IN	NS
.			229778	IN	NS	d.root-servers.net.
...
;; Received 228 bytes from 8.8.8.8#53(8.8.8.8) in 24 ms

;ec2-54-236-213-148.compute-1.amazonaws.com. IN A
com.			172800	IN	NS	h.gtld-servers.net.
...
;; Received 492 bytes from 199.7.91.13#53(199.7.91.13) in 106 ms

;ec2-54-236-213-148.compute-1.amazonaws.com. IN A
amazonaws.com.		172800	IN	NS	u1.amazonaws.com.
...
;; Received 192 bytes from 192.55.83.30#53(192.55.83.30) in 65 ms

;ec2-54-236-213-148.compute-1.amazonaws.com. IN A
compute-1.amazonaws.com. 900	IN	NS	u1.amazonaws.com.
...
;; Received 438 bytes from 205.251.195.199#53(205.251.195.199) in 708 ms

;ec2-54-236-213-148.compute-1.amazonaws.com. IN A
ec2-54-236-213-148.compute-1.amazonaws.com. 604800 IN A	54.236.213.148
...
;; Received 358 bytes from 156.154.64.10#53(156.154.64.10) in 15 ms

Finally, we get an address 54.236.213.148! Naive DNS queries would take dozens of round trips, taking seconds to complete. This is why we have caching/TTLs and DNS recursion!

Tagged .

More by Jim

What does the dot do in JavaScript?

foo.bar, foo.bar(), or foo.bar = baz - what do they mean? A deep dive into prototypical inheritance and getters/setters. 2020-11-01

Smear phishing: a new Android vulnerability

Trick Android to display an SMS as coming from any contact. Convincing phishing vuln, but still unpatched. 2020-08-06

A probabilistic pub quiz for nerds

A “true or false” quiz where you respond with your confidence level, and the optimal strategy is to report your true belief. 2020-04-26

Time is running out to catch COVID-19

Simulation shows it’s rational to deliberately infect yourself with COVID-19 early on to get treatment, but after healthcare capacity is exceeded, it’s better to avoid infection. Includes interactive parameters and visualizations. 2020-03-14

The inception bar: a new phishing method

A new phishing technique that displays a fake URL bar in Chrome for mobile. A key innovation is the “scroll jail” that traps the user in a fake browser. 2019-04-27

The hacker hype cycle

I got started with simple web development, but because enamored with increasingly esoteric programming concepts, leading to a “trough of hipster technologies” before returning to more productive work. 2019-03-23

Project C-43: the lost origins of asymmetric crypto

Bob invents asymmetric cryptography by playing loud white noise to obscure Alice’s message, which he can cancel out but an eavesdropper cannot. This idea, published in 1944 by Walter Koenig Jr., is the forgotten origin of asymmetric crypto. 2019-02-16

How Hacker News stays interesting

Hacker News buried my post on conspiracy theories in my family due to overheated discussion, not censorship. Moderation keeps the site focused on interesting technical content. 2019-01-26

My parents are Flat-Earthers

For decades, my parents have been working up to Flat-Earther beliefs. From Egyptology to Jehovah’s Witnesses to theories that human built the Moon billions of years in the future. Surprisingly, it doesn’t affect their successful lives very much. For me, it’s a fun family pastime. 2019-01-20

The dots do matter: how to scam a Gmail user

Gmail’s “dots don’t matter” feature lets scammers create an account on, say, Netflix, with your email address but different dots. Results in convincing phishing emails. 2018-04-07

The sorry state of OpenSSL usability

OpenSSL’s inadequate documentation, confusing key formats, and deprecated interfaces make it difficult to use, despite its importance. 2017-12-02

I hate telephones

I hate telephones. Some rational reasons: lack of authentication, no spam filtering, forced synchronous communication. But also just a visceral fear. 2017-11-08

The Three Ts of Time, Thought and Typing: measuring cost on the web

Businesses often tout “free” services, but the real costs come in terms of time, thought, and typing required from users. Reducing these “Three Ts” is key to improving sign-up flows and increasing conversions. 2017-10-26

Granddad died today

Granddad died. The unspoken practice of death-by-dehydration in the NHS. The Liverpool Care Pathway. Assisted dying in the UK. The importance of planning in end-of-life care. 2017-05-19

How do I call a program in C, setting up standard pipes?

A C function to create a new process, set up its standard input/output/error pipes, and return a struct containing the process ID and pipe file descriptors. 2017-02-17

Your syntax highlighter is wrong

Syntax highlighters make value judgments about code. Most highlighters judge that comments are cruft, and try to hide them. Most diff viewers judge that code deletions are bad. 2014-05-11

Want to build a fantastic product using LLMs? I work at Granola where we're building the future IDE for knowledge work. Come and work with us! Read more or get in touch!

This page copyright James Fisher 2017. Content is not associated with my employer. Found an error? Edit this page.

How to trace a DNS lookup

Similar posts

More by Jim