nslookup fails due to IPv6 lookup returning SERVFAIL

Bug #1874329 reported by Joshua Genet
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Neutron Gateway Charm
Invalid
Undecided
Unassigned

Bug Description

We're doing an nslookup from an instance in our Openstack. Using -type=a (IPv4) works as expected, but using -type=aaaa (IPv6), we get SERVFAIL. It seems as though we should get NOERROR, NXDOMAIN, etc.

This could be an issue in our Openstack configuration as we don't get a SERVFAIL on Serverstack, but we are unsure. (attached is our openstack bundle)

-----
From our Openstack
-----

ubuntu@juju-8e317a-kubernetes-11:~$ nslookup -server=172.16.0.10 -type=a juju-8e317a-kubernetes-11.openstack.customername.lan
1:47 PM Server: 127.0.0.53
1:47 PM Address: 127.0.0.53#53
1:47 PM Non-authoritative answer:
1:47 PM Name: juju-8e317a-kubernetes-11.openstack.customername.lan
1:47 PM Address: 172.16.0.113
1:47 PM ubuntu@juju-8e317a-kubernetes-11:~$ nslookup -server=172.16.0.10 -type=aaaa juju-8e317a-kubernetes-11.openstack.customername.lan
1:47 PM Server: 127.0.0.53
1:47 PM Address: 127.0.0.53#53
1:47 PM ** server can't find juju-8e317a-kubernetes-11.openstack.customername.lan: SERVFAIL

-----
From Serverstack
-----

Server: 127.0.0.53
2:01 PM Address: 127.0.0.53#53
2:01 PM Non-authoritative answer:
2:01 PM Name: solutions-qa-bastion.project.serverstack
2:01 PM Address: 10.5.0.10
2:01 PM ubuntu@solutions-qa-bastion:~$ nslookup -type=aaaa solutions-qa-bastion.project.serverstack
2:01 PM Server: 127.0.0.53
2:01 PM Address: 127.0.0.53#53
2:01 PM Non-authoritative answer:
2:01 PM *** Can't find solutions-qa-bastion.project.serverstack: No answer

Revision history for this message
Joshua Genet (genet022) wrote :
Changed in charm-neutron-gateway:
status: New → Incomplete
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Bug attachments

Remote bug watches

Bug watches keep track of this bug in other bug trackers.