Does the upstream DNS server actually know about bip.lcy02.canonistack?
If it doesn't, what sort of a response are you expecting?
Why /etc/hosts does not have bip & bip.lcy02.canonistack set?
Is this a fresh instance, or an upgrade?
in bionic, cloud-init should have configured your instance using netplan, not eni.
Does the upstream DNS server actually know about bip.lcy02. canonistack?
If it doesn't, what sort of a response are you expecting?
Why /etc/hosts does not have bip & bip.lcy02. canonistack set?
Is this a fresh instance, or an upgrade?
in bionic, cloud-init should have configured your instance using netplan, not eni.