domain-name-system – 我的AD DNS中没有互联网连接和转发查找区

当我查看DNS条目时,我看到以下内容：

我真的需要所有这些条目吗？

我目前有一个问题,我的AD无法访问互联网.从SF-Q我可以猜测它与我的dns条目有关,我认为修复将解决我的网络访问.

运行NetDiag / l会在DNS条目中显示错误,如下所示

DNS test . . . . . . . . . . . . . : Failed
      [WARNING] Cannot find a primary authoritative DNS server for the name
        'OptiTexDC.optitex.'. [ERROR_TIMEOUT]
        The name 'OptiTexDC.optitex.' may not be registered in DNS.
[WARNING] The DNS entries for this DC are not registered correctly on DNS server '192.168.0.2'. Please wait for 30 minutes for DNS server replication.
   [WARNING] The DNS entries for this DC cannot be verified right now on DNS server 80.179.52.100,ERROR_TIMEOUT. 
[FATAL] No DNS servers have the DNS records for this DC registered.

我想指出,我的所有用户/计算机等.可以访问互联网.

我真的不知道该怎么办？！

<<编辑>>
DNS管理转发器定义为我的ISP提供商给我的.这通常会传播给所有用户.

我应该将DC(192.168.0.2)添加为一个吗？

这是来自客户端的ipcnofig / all.我列出了我的ISP DNS以及我的域名.

添加更多信息：
查看服务器事件查看器,在DNS下,我看到以下内容：

Event Type: Warning
Event Source:   DNS
Event Category: None
Event ID:   7062
Date:       8/10/2011
Time:       16:03:03
User:       N/A
Computer:   OPTITEXDC
Description:
The DNS server encountered a packet addressed to itself on IP address 192.168.0.2. The     packet is for the DNS name "localhost.OPTITEX.OPTITEX.". The packet will be discarded. This condition usually indicates a configuration error. 

Check the following areas for possible self-send configuration errors: 
  1) Forwarders list. (DNS servers should not forward to themselves). 
  2) Master lists of secondary zones. 
  3) Notify lists of primary zones. 
  4) Delegations of subzones.  Must not contain NS record for this DNS server unless     subzone is also on this server. 
  5) Root hints. 

Example of self-delegation: 
  -> This DNS server dns1.example.microsoft.com is the primary for the zone     example.microsoft.com. 
  -> The example.microsoft.com zone contains a delegation of bar.example.microsoft.com to dns1.example.microsoft.com,(bar.example.microsoft.com NS dns1.example.microsoft.com) 
  -> BUT the bar.example.microsoft.com zone is NOT on this server. 

Note,you should make this delegation check (with nslookup or DNS manager) both on this DNS server and on the server(s) you delegated the subzone to. It is possible that the delegation was done correctly,but that the primary DNS for the subzone,has any incorrect NS record pointing back at this server. If this incorrect NS record is cached at this server,then the self-send could result.  If found,the subzone DNS server admin should remove the offending NS record. 

You can use the DNS server debug logging facility to track down the cause of this problem.

For more information,see Help and Support Center at     http://go.microsoft.com/fwlink/events.asp.
Data: 0000: 50 25 00 00               P%..

>我访问了提供的链接.没帮我.

<<编辑 – 添加服务器连接设置>>
我也在添加我的服务器网络设置.我不认为我可以动态地从DHCP进行这些设置,因为我是DHCP.我确实已经设置为DNS – 我自己的IP,以及我的1个ISP.我需要改变吗？

清单：
DNS客户端和DNS服务器都在服务器上运行.

谢谢