Si you just use AD to do all this for you? You said you setup your DNS using next->next->next, which smells of Windows:)

On 8 March 2016 at 13:48, geoffrey gitagia via skunkworks <skunkworks@lists.my.co.ke> wrote:
Thanks Wilson 

My problem seems to be way bigger than DNS .

But yes WINS would be the ideal solution.

On Tue, Mar 8, 2016 at 1:11 PM, Thuo Wilson <lixton@gmail.com> wrote:

On 8 March 2016 at 09:40, geoffrey gitagia via skunkworks <skunkworks@lists.my.co.ke> wrote:
I'mm not particularly interested with internet , but my MPLS IP's .

So it should serve requests for network A to network B and vice versa



The DNS in your context i think is ambiguous, you mean netbios names [local] that may have some challenges passing via routed networks since the names are obtained in a broadcast domain. Maybe WINs can break that [not windows fan anyway] or map name to an IP on remote networks using hosts file OR as you prefer local domain with zone entry for each host on the extended network. Remember to set/force PC on network to use this DNS server.

​​MPLS will pass all traffic unless filtered.​

Kind Regards,
Wilson./



--
GG


_______________________________________________
skunkworks mailing list
skunkworks@lists.my.co.ke
------------
List info, subscribe/unsubscribe
http://lists.my.co.ke/cgi-bin/mailman/listinfo/skunkworks
------------

Skunkworks Rules
http://my.co.ke/phpbb/viewtopic.php?f=24&t=94
------------
Other services @ http://my.co.ke



--
Best regards,
Odhiambo WASHINGTON,
Nairobi,KE
+254 7 3200 0004/+254 7 2274 3223
"Oh, the cruft."