You are using WINS Forward Lookup integration in your mixed UNIX/Windows environment to allow your DNS-only UNIX clients to use only their configured Windows Server DNS server to query and resolve resolution requests for downlevel Windows NT 4.0 machines’ NetBIOS names. This has been working well for your company for several months. You are informed that over the next several weeks, the Windows NT 4.0 servers are being moved to a different subnet in order to create a separate broadcast domain. They will still continue to register with the same WINS server, but their IP addresses will be changing, and they will no longer be able to be accessed via broadcasts. As these servers start their migration to the new subnet you begin to receive calls only from your UNIX community, complaining that they can no longer access servers that have moved until a day or so later.
What can you do to fix the problem for all future migrated servers?
- Type nbtstat -RR on the migrated NT servers.
- Increase the TTL for WINS forward lookup records.
- Type ipconfig /registerdns on the migrated NT servers.
- Decrease the TTL for WINS forward lookups records.
Reveal Solution Next Question