Red Hat Summit 红帽全球峰会支持控制台（Console）开发人员开始试用联系人

此内容没有您所选择的语言版本。

7.3.3. Verifying the BIND Configuration

Before continuing with further configuration, ensure BIND is configured correctly so that the broker's host name resolves. 
# dig @127.0.0.1 broker.example.com dig @127.0.0.1 broker.example.com
Copy to Clipboard Toggle word wrap
Inspect the ANSWER SECTION of the output, and ensure it contains the correct IP address.
Ensure the local BIND instance is being used by the broker: 
# dig broker.example.com dig broker.example.com
	
(An example AUTHORITY section:)
;; AUTHORITY SECTION:
example.com.    1    IN    NS    ns1.example.com.
Copy to Clipboard Toggle word wrap
Inspect the AUTHORITY SECTION of the output to verify that it contains the broker host name. If you have BIND configured on a separate host, verify that it returns that host name.
The BIND instance as configured will not answer questions about domains it does not own, but if you add one or more secondary nameservers in the /etc/resolv.conf file, they can be queried for other domains. Because the dig command will only query the BIND instance by default, use the host command to test requests for other host names. 
# host icann.org

icann.org has address 192.0.43.7
icann.org has IPv6 address 2001:500:88:200::7
icann.org mail is handled by 10 pechora1.icann.org.
Copy to Clipboard Toggle word wrap
返回顶部
Red Hat logoGithubredditYoutubeTwitter

学习

尝试、购买和销售

社区

关于红帽文档

通过我们的产品和服务，以及可以信赖的内容，帮助红帽用户创新并实现他们的目标。 了解我们当前的更新.

让开源更具包容性

红帽致力于替换我们的代码、文档和 Web 属性中存在问题的语言。欲了解更多详情，请参阅红帽博客.

關於紅帽

我们提供强化的解决方案，使企业能够更轻松地跨平台和环境（从核心数据中心到网络边缘）工作。

Theme

© 2025 Red Hat