1

If I have contradictory NS records for my domain:

dig +trace example.com

example.com.        172800  IN  NS  ns1.webfaction.com.
example.com.        172800  IN  NS  ns2.webfaction.com.
example.com.        172800  IN  NS  ns2.mydyndns.org.

Which one[s] will be queried by my DNS client? Does the ordering matter? How can I tell the ordering?

2
  • I would remove the ns dns record if possible, tertiary ns is unlikely to be fired off in my experience; how big is your network?
    – scape
    Commented Nov 7, 2012 at 18:13
  • There is no such thing as "tertiary ns"
    – bortzmeyer
    Commented Nov 7, 2012 at 20:59

3 Answers 3

2

The ordering in which the lists are presented to you is randomly ordered in most cases. But you (as the dns-admin) can also configure sequential output (round-robin) or static output. Depends on the administrators mood.

Which entry a client chooses is also up to the developer of the client.

dig +trace picks a random entry.

In any case, the only reason for this is load balancing. If all servers are running fine it doesn't matter which entry you actually use.

1

I don't see the same output when running the same command.

But to answer your question, a random one will be chosen and the order you list them in does not matter. You can see this with successive runs:

$ dig +trace inburke.com

...
inburke.com.        3600    IN  A   108.59.11.111
;; Received 45 bytes from 173.230.141.144#53(ns4.webfaction.com) in 96 ms

$ dig +trace inburke.com
...
inburke.com.        3600    IN  A   108.59.11.111
;; Received 45 bytes from 178.79.142.142#53(ns2.webfaction.com) in 8 ms
1
  • Sorry, just providing an example. I changed it to example.com Commented Nov 7, 2012 at 19:00
1

I believe that the resolver uses round robin methodology to query DNS hosts.

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .