You should not have to add any <DEV>_<PARAMETER>. These are added automatically when you chose to use network contextualization. You can add DNS_SEARCH in the VM template and it will be used.
On Thu, Sep 25, 2014 at 9:19 AM, Christoph Pleger <christoph.ple...@cs.tu-dortmund.de> wrote: > Hello, > >> Looking at the context.ps1 script here >> (https://github.com/OpenNebula/addon-context-windows/blob/master/context.ps1) >> it appears that: >> >> The format of <DEV>_DNS is a space separated list of DNS server IPs - e.g. >> "192.168.0.1 192.168.0.2" >> I can't see where <DEV>_DNS_SEARCH is being set, so I guess it is ignored. >> I would expect this to be a list of search domains - the equivalent to the >> 'search <domain>' entry inside nsswitch.conf on Linux/Unix systems. > > Thank you for the answer, that at least helps a little further. But still > I hope that someone can tell me what to insert for "<DEV> ... (I had > guessed that the people who wrote that documentation are reading here and > know the answer) > > Regards > Christoph > > _______________________________________________ > Users mailing list > Users@lists.opennebula.org > http://lists.opennebula.org/listinfo.cgi/users-opennebula.org -- Javier Fontán Muiños Developer OpenNebula - Flexible Enterprise Cloud Made Simple www.OpenNebula.org | @OpenNebula | github.com/jfontan _______________________________________________ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
