The WINS and WINS-R Records
Zone transfers sometimes fail because of Microsoft’s proprietary WINS and WINS-R records. When a Microsoft DNS Server is configured to consult a WINS server for names it can’t find in a given zone, it inserts a special record into the zone datafile. The record looks like this:
@ IN WINS <IP address of WINS server>
When configured to use WINS-R for reverse-mapping queries, the Microsoft DNS Server adds a similar WINS-R record to reverse-mapping zones.
Unfortunately, neither WINS nor WINS-R is a standard record type in the IN class. Consequently, any BIND secondaries that transfer this zone will choke on these records and refuse to load the zone. Here’s the message the administrator of the BIND server might see in his syslog output:
May 23 15:58:43 terminator named-xfer[386]: "fx.movie.edu IN 65281" - unknown type (65281)
The workaround for this problem is to configure the Microsoft DNS Server to filter out the proprietary record before transferring the zone. You do this by selecting the zone in the left pane of the DNS console, right-clicking it, and selecting Properties. For a forward-mapping zone, click on the WINS tab in the resulting properties window, which is shown in Figure 15-5.
![]() |
Checking Do not replicate this record filters out the WINS record for that zone.
For a reverse-mapping zone, click on the
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access
