Harry, Do you have an onap_dns server in your setup? In the heat-based ONAP, it looks like there’s an onap_dns server that provides name resolution for the various components, and then it may use some openstack DNS service called designate to get out to the real world (e.g. 8.8.8.8). Two things that might come out of that - if you just jump out to 8.8.8.8, you may not get local name resolution. Secondly, perhaps the 10.43.0.10 is supposed to be the local onap_dns server? That doesn’t sound like the address defaulted in the heat template for ONAP on O.S., however.
Joe > On Feb 24, 2018, at 1:43 AM, huangxiangyu <[email protected]> wrote: > > Hi Michael > > I’m using OOM Amsterdam branch and found that the nameserver in each > container is configured to 10.43.0.10. This address is unreachable and > therefore cause package installation failure in pod like heat-bootstrap-xxxx > under onap-dcaegen2. I can manually change nameserver to 8.8.8.8 to install > package but is there a way to configure nameserver to 8.8.8.8 ? > > Thanks > Harry > _______________________________________________ > onap-discuss mailing list > [email protected] <mailto:[email protected]> > https://lists.onap.org/mailman/listinfo/onap-discuss > <https://lists.onap.org/mailman/listinfo/onap-discuss>
_______________________________________________ onap-discuss mailing list [email protected] https://lists.onap.org/mailman/listinfo/onap-discuss
