使用 AWS re:Post 即表示您同意 AWS re:Post 使用條款

nslookup failed - Got SERVFAIL reply from 172.26.0.2

0

Hello,

I've created a lightsail instance and deployed a test site, it's working fine via a browser, however when the server instance can't seem to resolve the hostname, if I query using a google DNS server it resolved fine, any ideas?

Enter image description here

Thanks

已提問 7 天前檢視次數 60 次
3 個答案
1
已接受的答案

Hello.

I checked the DNS propagation status on the following site, but name resolution was only successful in some countries.
It is possible that it is taking a long time to propagate to AWS DNS.
Therefore, I think I succeeded by changing the DNS server used for name resolution.
https://www.nslookuptool.com/#A&test.bpa.org.ki
a

profile picture
專家
已回答 7 天前
profile picture
專家
已審閱 6 天前
1

Based on the information provided, it appears that your Lightsail instance is having trouble resolving the hostname using its default DNS server (172.26.0.2), while external DNS servers like Google's (8.8.8.8) can resolve it correctly. This suggests a potential issue with the DNS configuration on your Lightsail instance or within your VPC.

Here are a few steps you can take to troubleshoot and potentially resolve this issue:

  1. Check the /etc/resolv.conf file on your Lightsail instance to verify the configured DNS servers. If the file is pointing to an incorrect or unresponsive DNS server, you may need to update it.

  2. Ensure that your Lightsail instance's security group or firewall settings allow outbound DNS traffic (usually on port 53).

  3. Verify that the DNS records for your domain are correctly set up in your DNS management system (e.g., Route 53 or Lightsail's DNS zone).

  4. If you're using a custom domain, make sure the nameservers are correctly configured with your domain registrar.

  5. Try updating the instance's DNS configuration to use public DNS servers temporarily (like 8.8.8.8) to see if that resolves the issue.

  6. If the problem persists, you may want to create a snapshot of your instance and launch a new instance from that snapshot to see if the issue is related to the specific instance configuration.

If none of these steps resolve the issue, it may be worth contacting AWS support for further assistance, as there could be an underlying network or configuration problem within your Lightsail environment.

Sources
DNS Doesn't resolve | AWS re:Post
AWS Lightsail help | AWS re:Post
Troubleshoot website access errors on Lightsail | AWS re:Post

profile picture
已回答 7 天前
profile picture
專家
已審閱 6 天前
0

Thank you, I'll look further into the DNS side of things. Cheers

已回答 7 天前

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

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

回答問題指南