systemd-resolved not forwarding dns requests to dns server when ElasticIP assigned

0

We have instances running ubuntu 20.04 which use systemd-resolved with a local address of 127.0.0.53

This appears to affect instances that have an ElasticIP assigned to them but not others. I cannot see any other difference. resolvectl status show that 10.0.0.2 is the dns server in use for both affected and non-affected instances. On affected instances, using tcpdump I can see that 127.0.0.53 is responding with SERVFAIL and not forwarding anythin to the Amazon DNS service, which is at 10.0.0.2

However if I manually send a request directly to 10.0.0.2 on affected instance: nslookup x.y.com 10.0.02 it successfully perfroms dns request.

Any ideas?

已提問 2 年前檢視次數 70 次
沒有答案

您尚未登入。 登入 去張貼答案。

一個好的回答可以清楚地回答問題並提供建設性的意見回饋,同時有助於提問者的專業成長。

回答問題指南