win2k dns problems --watch newbie

[Danny Mayer]

         You can't do that.  You can only have one application listening at the
ip address/port at the same time. You CAN have one server listening on both
IP addresses at the same time.

         In any case this is the wrong mailing list.  You're running Microsoft's code,
  this is the BIND mailing list.  You need to contact Microsoft support for more
  information and answers.

                 Danny
At 08:39 PM 3/29/01, Scott.Wiseman wrote:




>I am trying for 2 dns servers on the same machine...
>
>dns.avidware.com
>and
>dns1.avidware.com
>
>what went wrong?
>
>
>
>Event Type:     Warning
>Event Source:   DNS
>Event Category: None
>Event ID:       9999
>Date:           3/29/2001
>Time:           5:20:12 PM
>User:           N/A
>Computer:       DNS
>Description:
>The DNS server has encountered numerous run-time events.  These are usually
>caused by the reception of bad or unexpected packets, or from problems with
>or excessive replication traffic.  The data is the number of suppressed
>events encountered in the last 15 minute interval. 
>Data:
>0000: 14 00 00 00               ....    
>
>
>
>
>Event Type:     Warning
>Event Source:   DNS
>Event Category: None
>Event ID:       7062
>Date:           3/29/2001
>Time:           5:20:12 PM
>User:           N/A
>Computer:       DNS
>Description:
>The DNS server encountered a packet addressed to itself -- IP address
>216.184.208.169. 
>  
>The DNS server should never be sending a packet to itself.  This situation
>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. 
>  
>Example of self-delegation: 
>   -> This DNS server dns1.foo.com is the primary for the zone foo.com. 
>   -> The foo.com zone contains a delegation of bar.foo.com to dns1.foo.com, 
>   (bar.foo.com NS dns1.foo.com) 
>   -> BUT the bar.foo.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. 
>Data:
>0000: 50 25 00 00               P%..