Reverse DNS host-lookup failure

Eric Albee

unread,

Oct 7, 2015, 5:13:46 PM10/7/15

to gce-discussion

Has anyone experienced issues with reverse dns lookup failure against your nodes. For example when I run `host {ip-2-query}`, i get the following result: `not found: 3(NXDOMAIN)`

The odd thing though is that this is only on certain nodes, others have no problem with the reverse DNS lookup

Thanks,

~albmin

Faizan (Google Cloud Support)

unread,

Oct 8, 2015, 3:14:31 PM10/8/15

to gce-discussion

Hello Eric,

We confirmed there appears to be an issue here, and we're investigating.

I'll update the post once I have more information to share.

Thanks

Faizan

Eric Albee

unread,

Oct 12, 2015, 12:35:04 AM10/12/15

to gce-discussion

Faizan, any updates yet? I can provide more info if needed

Eric Albee

unread,

Oct 19, 2015, 10:37:44 PM10/19/15

to gce-discussion

in terms of resolution, the issue appears to be resolved

Paul Nash

unread,

Oct 20, 2015, 12:52:30 AM10/20/15

to gce-discussion

Hi Eric, yes, engineering has made some corrections for specific blocks of IPs that were not resolving reverse DNS correctly.