nslookup - returned IP address priority


hello,

we have server has 2 ips. there issue can't head around.

when running nslookup against 1 dns server, ips correctly returned. server ip first , second ip used web app on same machine.

running nslookup against dns, returns ips in switched order, meaning web app ip first , server ip second.

i have run out of ideas :-(, server owner encounters issues when querying resources.

is there way set priority? dictates way ips returned when running nslookup?

regards,

dominique.

hi,

as far know, can’t set priority of records manually.

by default, dns server service uses local subnet prioritizing method giving preference ip addresses on same network when client query resolves host name mapped more 1 ip address. feature requires client application attempt connect host using closest (and typically fastest) ip address available connection.

the dns server service uses local subnet priority follows:

  1. the dns server service determines if local subnet prioritization is needed order query response.
         if more 1 resource record (rr) matches queried host name, the dns server service can reorder records subnet location. if the queried host name matches single resource record, or if the ip network address of client not match ip network address for any of mapped addresses in answer list of multiple rrs, no prioritizing necessary.
  2. for each rr in matched answer list, dns server service determines records (if any) match subnet location of the requesting client.
  3. the dns server service reorders answer list rrs which match local subnet of requesting client placed first in the answer list.
  4. prioritized subnet order, answer list returned the requesting client.

for detailed information, please view link below,

prioritizing local subnets

http://technet.microsoft.com/en-us/library/cc787373(v=ws.10).aspx

hope helps.



steven lee

technet community support





Windows Server  >  Network Infrastructure Servers



Comments

Popular posts from this blog

Motherboard replacement

Cannot create Full Text Search catalog after upgrading to V12 - Database is not fully started up or it is not in an ONLINE state

Remote Desktop App - Error 0x207 or 0x607