To me it looks like the software that is validating your setup is testing to ensure all 3 name servers you have set return the same records... and they don't.
It looks like this is on purpose also to do with balancing the DNS load.
when doing the following tests:
dig @NS1.DREAMHOST.COM ns gabrielfair.com
I get an answer like:
;; ANSWER SECTION:
gabrielfair.com. 14400 IN NS ns3.dreamhost.com.
gabrielfair.com. 14400 IN NS ns2.dreamhost.com.
gabrielfair.com. 14400 IN NS ns1.dreamhost.com.
Testing NS2:
dig @NS2.DREAMHOST.COM ns gabrielfair.com
I get an answer like:
;; ANSWER SECTION:
gabrielfair.com. 14400 IN NS ns2.dreamhost.com.
gabrielfair.com. 14400 IN NS ns1.dreamhost.com.
gabrielfair.com. 14400 IN NS ns3.dreamhost.com.
And testing NS3:
`dig @NS3.DREAMHOST.COM ns gabrielfair.com``
I get an answer like:
;; ANSWER SECTION:
gabrielfair.com. 14400 IN NS ns2.dreamhost.com.
gabrielfair.com. 14400 IN NS ns1.dreamhost.com.
gabrielfair.com. 14400 IN NS ns3.dreamhost.com.
Although the hosts are the same the order is different when NS1 is queried.
I dont think this is something to worry about unless the validator will not let you skip it.