My users need to have these 3 DNS entries in their Win2k client setup, exactly in this order. For example:
A
B
C
A and B are identical to each other.
C is in a different region.
These DNS servers are maintained by 2 different data centers.
I don't have any authority over them.
The problem is:
1 - "A&B" are able to resolve internet/intranet requests properly but cannot resolve "*.session.rservices.com"
2 - "C" can resolve "*.session.rservices.com" but internet/intranet stuff is resolving to the wrong location(NAT Address) and thus won't work.
My users need "C" to resolve "*.session.rservices.com" requests because of an app they need. So when all 3 DNS entries are in the client setup, everything works 85% of the time.
The other 15% of time Intranet/Internet access is intermittent. Seems that those requests sometimes use the DNS "C" to resolve and it fails. Likewise requests for "*.session.rservices.com" work mostly but there is a chance it won't work as it might use A&B to resolve.
Is there a way I can somehow prioritize the DNS search usage in Win2kPro? For example to force requests for "*.session.rservices.com" to only use DNS "C" and never A/B?
Thanks for any insight into this
-Phil
A
B
C
A and B are identical to each other.
C is in a different region.
These DNS servers are maintained by 2 different data centers.
I don't have any authority over them.
The problem is:
1 - "A&B" are able to resolve internet/intranet requests properly but cannot resolve "*.session.rservices.com"
2 - "C" can resolve "*.session.rservices.com" but internet/intranet stuff is resolving to the wrong location(NAT Address) and thus won't work.
My users need "C" to resolve "*.session.rservices.com" requests because of an app they need. So when all 3 DNS entries are in the client setup, everything works 85% of the time.
The other 15% of time Intranet/Internet access is intermittent. Seems that those requests sometimes use the DNS "C" to resolve and it fails. Likewise requests for "*.session.rservices.com" work mostly but there is a chance it won't work as it might use A&B to resolve.
Is there a way I can somehow prioritize the DNS search usage in Win2kPro? For example to force requests for "*.session.rservices.com" to only use DNS "C" and never A/B?
Thanks for any insight into this
-Phil