search

Azure / wordpress-linux-appservice

MIT License
111 stars 71 forks source link

Embedded dns resolver 127.0.0.11 issue #102

Closed lintaonz closed 1 year ago

lintaonz commented 1 year ago

Hi,

I have put both the App Service and the MySQL Flexible server behind my own VNet and Subnets. MySQL Flexible server use Private DNS Zone. When browse the App URL: mywebsite.azurewebsites.net, I got database connection error. Then I run nslookup command:

nslookup mywebiste.mysql.database.azure.com

Server:         127.0.0.11
Address:        127.0.0.11:53

Non-authoritative answer:
mywebiste.mysql.database.azure.com  canonical name = mywebiste.privatelink.mysql.database.azure.com

But if I do nslookup mywebiste.privatelink.mysql.database.azure.com

It return error:

nslookup mywebiste.privatelink.mysql.database.azure.com

Server:         127.0.0.11
Address:        127.0.0.11:53

** server can't find mywebiste.privatelink.mysql.database.azure.com: NXDOMAIN

Then I check the /etc/resolv.conf

# This container is using an embedded dns resolver
# The configured nameservers at startup are 168.63.129.16
# The configured options for the listener at startup are timeout:1 attempts:5
nameserver 127.0.0.11
options ndots:0 timeout:15 attempts:2

Then I update the the nameserver from 127.0.0.11 to 168.63.129.16 in the /etc/resolv.conf, everything is working.

Question: How do I let App Service don't use the embedded dns resolver 127.0.0.11 instead of the Microsoft default DNS 168.63.129.16 instead?

Thanks

Tao

lintaonz commented 1 year ago

It turns out it's our DNS server issue. Close the ticket here.