This website uses Cookies. Click Accept to agree to our website's cookie use as described in our Privacy Policy. Click Preferences to customize your cookie settings.
Accept
Reject
Preferences
Log in to ask a question
Announcements
This site is in read only until July 22 as we migrate to a new platform; refer to this community post for more details.
Get hands-on experience with 20+ free Google Cloud products and $300 in free credit for new customers.
Log in to ask a question

Cloud DNS server only resolves on loopback and not on primary internal ip address

Posted on 06-08-2025 05:36 AM
andres_fastweb
Bronze 3
Bronze 3
Reply posted on --/--/---- --:-- AM

Hi,

Having some issues getting my GCP DNS server vm up and running (debian).

Local queries work but it uses the loopback address of 127.0.0.53 so when I query it from another vm in same subnet I get a "communications error to 10.128.0.2#53: connection refused" error message.

I found that in the /etc/resolv.conf file it only has this loopback address and not its internal which is 10.128.0.2 and have tried adding it there but linux erases it after a restart.

How do I get my vm to resolve on its primary internal address?

Thanks,

AA

0 5 310
Topic Labels
0 Likes
Reply
5 REPLIES 5
Top Labels in this Space
Top Solution Authors
View all