self-service network name resolution not working [closed]

asked 2017-10-14 11:09:31 -0500

tk8 gravatar image


I've installed OpenStack ocata release according to the install guide. Nearly everything works fine, but the name resolution in the self-service network does not work. I tried different name-servers, but I always get the output 'bad address'. Pinging the dns-servers works fine.

Does anyone has a hint?


edit retag flag offensive reopen merge delete

Closed for the following reason question is not relevant or outdated by tk8
close date 2017-10-18 11:25:12.226745


What action results in "bad address"? Are your nameservers built into OpenStack, are they in your cloud or outside the cloud? From where are you pinging them?

Bernd Bausch gravatar imageBernd Bausch ( 2017-10-14 19:38:36 -0500 )edit

I ping from a test-instance inside a self-service network. For exampleping results in ping: bad address '' First I used a nameserver inside my physical network then I tried I don't have a nameserver in my cloud. I can ping the ip-addresses of the nameservers.

tk8 gravatar imagetk8 ( 2017-10-15 04:26:24 -0500 )edit

"bad address" indicates that name resolution isn't even tried. When you google the error, many results point to problems related to busybox. I guess your instance is Cirros? Can you try a different Cirros version or a different image like Fedora or Ubuntu?

Bernd Bausch gravatar imageBernd Bausch ( 2017-10-15 14:45:34 -0500 )edit

I forgot to mention that the name resolution of an instance attached to the physical network (without router in a self-service network) works fine. I tested with ubuntu on the same self-service network and ping results in ping: unknown host.

tk8 gravatar imagetk8 ( 2017-10-16 07:25:56 -0500 )edit

Did you launch the two instances from the same image?

I would use DNS tools like dig or host to get more clarity. Compare /etc/nsswitch. In the worst case, trace for UDP packets, port 53.

Bernd Bausch gravatar imageBernd Bausch ( 2017-10-16 07:42:06 -0500 )edit