|
|
|
|
 请教dns内部解析不正常 - dnysea [ 2004-04-23 11:40 | 544 byte(s)]
 Re: 请教dns内部解析不正常 - riser [ 2004-04-23 16:44 | 50 byte(s)]
 Re: 请教dns内部解析不正常 - dnysea [ 2004-04-25 01:07 | 224 byte(s)]
 Re: 请教dns内部解析不正常 - dnysea [ 2004-04-25 01:26 | 1,474 byte(s)]
 Re: 请教dns内部解析不正常 - dnysea [ 2004-04-26 09:43 | 240 byte(s)]
 Re: 请教dns内部解析不正常 - riser [ 2004-04-26 09:56 | 66 byte(s)]
 Re: 请教dns内部解析不正常 - dnysea [ 2004-04-26 11:38 | 292 byte(s)]
 Re: 请教dns内部解析不正常 - dnysea [ 2004-04-23 17:47 | 60 byte(s)]
|
|
|
|
[Original]
[Print]
[Top]
|
我在公司内部的一台机器上面安装了bind-9.2.3,用来解析内部使用的一个广域网上不存在的域名,比如说就叫做internal.site,其下有www,www-1等若干子域名。然后DHCP,让所有的内部client端的第一个dns都指向这台dns。
现在的问题是client开机之后有时候无法解析该域名,dos下面ping域名时报告错误是:Ping request cound not find host xxxx.xxx.xxx. Please check the name and try again. 但是过一段时间,什么也不用做,又正常了,很奇怪。
请问可能是怎么回事?
环境:Redhat Advance Server 3.0, Bind-9.2.3,客户端是XP Profiessional.
谢谢!
|
|
|
[Original]
[Print]
[Top]
|
|
[Original]
[Print]
[Top]
|
XP下面我用nslookup之后,nslookup显示以下内容:Can't find server name for address 192.168.1.100: Non-existent domain,然后就将default server设置为另外一个dns服务器。
请问这个问题是怎么回事?
谢谢!
|
|
|
[Original]
[Print]
[Top]
|
|
[Original]
[Print]
[Top]
|
查过文档,nslookup不正常原来是内部dns服务器没有设置反向解析的原因,具体内容参见以下地址内的内容:http://www.ezine.com/QandA/ServerName.html
If you go into the NSLOOKUP program and it immediately gives you an error message something along the lines of:
*** Can't find Server name for address...
Non-existent domain
*** Default servers are not available
Default Server: Unknown
You are experiencing a common problem caused by an improperly configured reverse arpa (in-addr.arpa) zone.
When the NSLOOKUP program starts it goes to the TCP/IP configuration for the system on which it is running. From the configuration it determines the IP address of the DNS server that the system is configured to use. The NSLOOKUP does a reverse lookup using the IP address of the DNS server and tries to determine the name of the server.
If the reverse arpa zone for that IP address is not set up correctly, then NSLOOKUP cannot determine the name associated with that IP address, and it displays the error message given above.
To fix this problem you need to properly configure the reverse arpa zone for the IP address of the DNS server, and make sure that the reverse arpa is properly delegated to the server.
现在nslookup问题已经解决,内部域名解析目前看起来已经正常,再观察一段时间看看还有没有什么问题。
|
|
|
[Original]
[Print]
[Top]
|
|
[Original]
[Print]
[Top]
|
最新情况,现在nslookup正常了,而且nslookup能解析那些内部域名。但是ping的时候又不能解析,晕阿,说是以下错误:Ping request could not find host xx.xxxx.xxx. Please check the name and try again.
请问有可能是怎么回事呢?
谢谢!
|
|
|
[Original]
[Print]
[Top]
|
|
[Original]
[Print]
[Top]
|
是这样的,ping不能解析到结果时,我用了ipconfig/flushdns之后,几次还是不能正确解析。
但是过了一段时间,期间没有什么操作,一切就正常了,很是奇怪。
因为我要用于公司内部,不能指望每个人去手工进行一些诸如ipconfig/flushdns之类的操作啊。
哪位能帮解决吗?
多谢了。
|
|
|
[Original]
[Print]
[Top]
|
|
|