win2k dns problems --watch newbie

[Gary Wardell]

Are you running NT BIND or Win2K's DNS service?

It's generally a bad idea to run two DNS services on the same machine and you didn't say what your trying to accomplish by this?

Some of the errors you show are probably due to both services listening on the same port.

If you really have to do this they must each listen on their own port which probably mans they need their own IP address so they can
both listen on the well-know DNS port.  You will also need to make sure that each copy is using it's own configuration file
otherwise there will be conflicts.  This means you will probably have to explicitly tell it which file to use when it starts.

It may be easier to spend $300 or so for a cheap machine and put the second DNS on it.

Gary


> -----Original Message-----
> From: bind-users-bounce at isc.org [mailto:bind-users-bounce at isc.org]On
> Behalf Of Scott.Wiseman
> Sent: Thu, March 29, 2001 8:40 PM
> To: 'bind-users at isc.org'
> Subject: win2k dns problems --watch newbie
>
>
>
>
>
>
> 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%..
>