On 18-Aug-2008, at 15:22 , Prabhat Rana wrote: > Matt, > Thanks for the quick response. The querying client is this case is > not a server it is infact a handheld device. And we can not put any > search order in this device. We can only tell it to which DNS server > to query and what URL which is http://mms
Ah, I see. And you can't put the fully qualified domain name of nms.ora.com in for the URL? That seems broken to me. However, if that's the case... Assuming that it's only the one hostname that you need to reach (nms.ora.com) then you should configure a new TLD called 'nms' on your authoritative servers, along side ora.com. The 'nms.' zone would just have the A record for nms.ora.com in it. On the recursive server(s), set up a forwarder statement sending requests for 'nms.' to your authoritative servers. If 'nms.ora.com' is just an example, and you have several predictable host names that will need to be reached in this way, then you need to set up a new TLD for each host. If you can't predict what host names will be used this way, then there's no way (that I'm aware of) to do what you want with BIND.
