We have a situation that I am wondering about as far as the search order for DNS in the TCP/IP properties on Microsoft NT 4.0
I have read that on an NT server that the second DNS server(entered in TCP/IP properties) does not get queried unless the first server is completely unavailable.
For example: if you are looking for cisco.com and you have a local DNS server in the list first, which does not have the cisco entry, the search will NOT go onto the next DNS server and try to resolve the name.
The only way the second server resolves names is if the first is down completely.
This is the way I understand it works, but I have run into a situatuation that is working contrary to this.
Can someone help me out with this, I would appreciate it.
Thanks,
rkmorrow
I have read that on an NT server that the second DNS server(entered in TCP/IP properties) does not get queried unless the first server is completely unavailable.
For example: if you are looking for cisco.com and you have a local DNS server in the list first, which does not have the cisco entry, the search will NOT go onto the next DNS server and try to resolve the name.
The only way the second server resolves names is if the first is down completely.
This is the way I understand it works, but I have run into a situatuation that is working contrary to this.
Can someone help me out with this, I would appreciate it.
Thanks,
rkmorrow