直接查询Google Cloud DNS记录(nslookup) [英] Looking up Google Cloud DNS records (nslookup) directly

问题描述

我正在测试GC DNS，并已创建区域和记录.但是，直接查询分配的Google NS时，执行nslookup(Windows/命令行)会超时:

I'm in the process of testing GC DNS and have created zones and records. However, doing nslookup (windows/command line) times out when querying assigned Google NS directly:

> www.some_domain_A_record.com.
Server:  ns-cloud1.googledomains.com
Addresses:  2001:4860:4802:32::6e
          216.239.32.110

DNS request timed out.
    timeout was 2 seconds.
DNS request timed out.
    timeout was 2 seconds.
*** Request to ns-cloud-e1.googledomains.com timed-out

有人对此有任何建议/意见吗?

Does anyone have any advice/input on this?

注意:

• 我仅使用此项目的Cloud DNS(没有GCE/GAE/VM等)，实际上是仅DNS".我希望从一些现有的DNS(仅)提供程序迁移到Google云DNS

• I am only using Cloud DNS for this project (no GCE/GAE/VM, etc.), essentially "just DNS". I'm looking to migrate from some existing DNS (only) provider to Google cloud DNS

这意味着资源(A，CNAME，MX等)不一定与任何由GC托管的应用或服务(某些可能与-例如Google Apps/Work等)相关.换句话说，典型" DNS区域/记录.

This means resources (A, CNAME, MX, etc.) aren't necessarily related to any GC hosted app or service (some could be - e.g. Google Apps/Work, etc.). In other words "typical" DNS zone/records.

这是针对现有/活动域/区域

我尚未在注册商级别进行任何更改(我正在首先测试)，并且没有直接查询分配给该区域的google ns

I have not made any changes at the registrar level (I'm testing first) and querying the google ns assigned for the zone directly

致SO社区:
完全理解这不是编程问题.仅仅是这是Google的铜牌"级支持区域.

To SO community:
Completely understood that this isn't a programming question. Its just that this is the "Bronze" level support area for Google.

---

更新

实际上使用Mac终端成功

---

Update

Using Mac terminal actually succeeds

> server
Default server: ns-cloud1.googledomains.com
Address: 216.239.32.106#53
> gcloud-test.some_domain_I_have.com.
Server:     ns-cloud1.googledomains.com
Address:    216.239.32.106#53

gcloud-test.some_domain_I_have.com  canonical name = the_right_target.com.
Name:   the_right_target.com
Address: 1.2.3.4

将进一步挖掘，似乎与Windows nslookup有关..怪异...这不是防火墙，我可以使用任何特定的(或公共)名称服务器nslookup其他域.

Will dig some more, seems something to do with Windows nslookup..weird...it's not some firewall, I can nslookup some other domain using whatever specific (or public) name server.

变得奇怪-上面的同一Mac(vm/parallels)上的Windows(10个无关紧要的东西)也可以正常工作...

Getting weirder - Windows (10 not that it should matter) on same Mac (vm/parallels) above works fine as well...

从2015年9月24日开始，似乎可以直接查询分配给您的Google ns在Windows nslookup(交互模式)上的奇怪行为.

As of today 9-24-2015 it seems the odd behavior on Windows nslookup (interactive mode) when querying your assigned Google ns directly is resolved.

最重要的是:一切都很好，运行起来也很流畅！我要去Google Cloud了:)

Bottom line: All's good and running quite smoothly! To the Google Cloud I go :)

在(所有* ) Windows 上-似乎，如果您有/想要直接查询分配的Google NS ，如下所示在非交互模式(也称为一个班轮")中执行nslookup.如果要在DNS传播之前 检查/查询资源(此后，您实际上不需要直接查询分配的NS)就可以这样做.

On (all*) Windows - it just seems that if you have/want to query your assigned Google NS directly, you have to do nslookup in non-interactive mode (aka "one liner") as shown below. You'll do this if you want to check/query resources before DNS propagation (after which, you don't really need to query your assigned NS directly).

或者，如果您使用分配的Google NS的IP地址(也在下面的示例中)，则可以nslookup交互模式.

Alternatively, you could nslookup interactive mode if you use the IP address of your assigned Google NS (sample also below).

* 所有Windows" -表示主机/PC和操作系统.如上，Mac(VM/Parallels)上的Windows不受这种怪异的影响-您可以使用nslookup交互模式并直接查询您的ns ...

Mac/OSX终端正常/不受影响

*"all Windows" - meaning host/pc and OS. As above, Windows on Mac (VM/Parallels) is strangely unaffected by this weirdness - you can use nslookup interactive mode and query your ns directly just fine...

Mac/OSX terminal is fine/unaffacted

部分答案，仅限Windows:

Partial answer, scoped to Windows:

要使其正常运行，

• 在非交互式模式下使用nslookup: nslookup资源名称Google-ns
  例如nslookup foo.com ns-cloud1.googledomains.com
  
  或
  

• 以交互式模式使用google ns的IP地址:

• use nslookup in non-interative mode: nslookup name-of-resource the-google-ns
  e.g. nslookup foo.com ns-cloud1.googledomains.com
  
  or
  

• use the IP address of the google ns in interactive mode:

c:\nslookup
> server 216.239.32.106
Default Server:  ns-cloud-a1.googledomains.com
Address:  216.239.32.106

> the_resource_to_lookup

关于为什么"，我将转介给网络人士-多年来没有戴过这顶帽子-似乎与PTR/反向查找有关，但这只是一个猜测.

As to "why", I'll defer to network folk - haven't worn that hat in years -seems something to do with PTR/reverse lookup, but that's just a guess...

推荐答案

在Windows上，您正在使用ns-cloud-e1.googledomains.com作为名称服务器，而在Mac上，您正在使用ns-cloud1.googledomains.com ns-cloud-a1.googledomains.com.

Looking at your inquiries, on your Windows you're using ns-cloud-e1.googledomains.com as the name server, however on your Mac you're using ns-cloud1.googledomains.com which is ns-cloud-a1.googledomains.com.

如果两个查询都针对同一区域，则第一个nslookup查询中的time-out是有意义的.您的解决方法是使用正确的DNS服务器进行nslookup查询.

If both inquiries are for the same zone, then time-out on the first nslookup inquiry makes sense. Your workaround used a correct DNS server for the nslookup inquiry.

解决方案是将Windows DNS设置从ns-cloud-e1.googledomains.com修改为ns-cloud-a1.googledomains.com(与Mac相同).

The solution is modifing your Windows DNS settings from ns-cloud-e1.googledomains.com to ns-cloud-a1.googledomains.com (same DNS settings of your Mac).

使用开发人员控制台，在Cloud DNS下，您可以验证区域与哪些DNS服务器关联.

Using the Developers Console, under Cloud DNS you can verify what DNS servers your zone is associated to.

这篇关于直接查询Google Cloud DNS记录(nslookup)的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！