search

cloudfoundry / bosh-azure-cpi-release

BOSH Azure CPI
Apache License 2.0
63 stars 88 forks source link

VM is being created with MS DNS even when local_dns is specified. #686

Closed vijaymck closed 1 year ago

vijaymck commented 1 year ago

Versions (please add them if you have more releases for this issue)

CPI Version: 42 BOSH Version: bosh-277.3.0 CF Version: Diego Version:

Stemcell

Version: ubuntu-jammy-1.93 Distro:

Environment

Issue Details

We create BOSH env/director using files from commit: https://github.com/cloudfoundry/bosh-deployment/blob/2eefadfd56be3d7be91a25f7fc0910f203d8ea84/

Specified internal_dns var list to create-env:

image

Also include interoplate file for dns replacement:

image

However, when checked in BOSH director or any VM it creates, we are seeing "168.63.129.16" as first name server entry in resolv.conf. It shows that, our specified internal dns entries are included but first one is MS's public DNS server. We are obviously having issues resolving local look ups.

bosh/0:~# cat /etc/resolv.conf nameserver 168.63.129.16 nameserver 10.15.x.x nameserver 10.7.x.x search u5m03w2x1dxu5c40t4t0m315eg.dx.internal.cloudapp.net

Logs (Please redact all sensitive information in your logs)

Repro steps (if necessary, delete otherwise)

vijaymck commented 1 year ago

BTW, bosh interpolate is generating as expected: dns:

vijaymck commented 1 year ago

Also Bosh task CPI log shows expected DNS entries: I, [2023-07-11T11:26:57.272298 #27111 #2240] INFO -- [req_id cpi-730480]: create_vm(0f3bf655-10ae-4eca-a216-6af1901a2935, bosh-stemcell-f26be7ca-9c17-45fb-8a20-9bd1869fccad, {"instance_type"=>"Standard_D2_v2"}, {"Infrastructure"=>{"type"=>"manual", "ip"=>"10.15.4.96", "netmask"=>"255.255.255.192", "cloud_properties"=>{"resource_group_name"=>"rg-west-ETS_NETWORK", "subnet_name"=>"sb-concourse-uw", "virtual_network_name"=>"vnet-west-ETSTRANSIT"}, "default"=>["dns", "gateway"], "dns"=>["10.15.x.x", "10.7.x.x", "10.55.x.x"], "gateway"=>"10.15.4.65"}}, [], ...)

ramonskie commented 1 year ago

did you configure these nameservers in your network? as it seems that dhcp entries are retrieved first. so it seems there are configured are 2 sources. dhcp +boshdns if only boshdns is configured it should put it in the correct order. bosh dns can be configured with the correct recursors that you need

vijaymck commented 1 year ago

Thanks @ramonskie That puts in the right path. My VNET does have MS default DNS configured. Seems like it was recent change from our local DNS servers. Will verify after update those and confirm here.

rkoster commented 1 year ago

@vijaymck where you able to resolve the issue?

rkoster commented 1 year ago

Closing due to inactivity, feel free to reopen when needed.