Score:0

Dns for internal network setup

in flag

Primary network IP addresses ppp.ppp.ppp.0-255. Primary has its own name resolution. Manufacturing network IP addresses xxx.xxx.xxx.0-255. I have a block of IP addresses with which to work with on my Manufacturing network xxx.xxx.xxx.0 - 255. I am not the primary network admin here. For some reason unknown to me the standard network cannot handle (or won't be set up) DNS for local name lookup for clients on this network xxx.xxx.xxx.0-255. I do however have a Microsoft Server 2016 running. I will be connecting many IP connected sensors, IOT and other manufacturing type devices in this Manufacturing network.

My thought is to set up the Microsoft Server to do DNS for the Manufacturing network xxx.xxx.xxx.0-255.

That service IP address could be added to any machine name resolution IP's that needs to do additional name resolution in the xxx.xxx.xxx.0-255 range.

Is this reasonable or a really stupid workaround?

mangohost

Post an answer

Most people don’t grasp that asking a lot of questions unlocks learning and improves interpersonal bonding. In Alison’s studies, for example, though people could accurately recall how many questions had been asked in their conversations, they didn’t intuit the link between questions and liking. Across four studies, in which participants were engaged in conversations themselves or read transcripts of others’ conversations, people tended not to realize that question asking would influence—or had influenced—the level of amity between the conversationalists.