From mboxrd@z Thu Jan  1 00:00:00 1970
Date: Thu, 17 Oct 1996 00:49:59 +0100
From: forsyth@plan9.cs.york.ac.uk forsyth@plan9.cs.york.ac.uk
Subject: unmatched replies
Topicbox-Message-UUID: 4f70b226-eac8-11e9-9e20-41e7f4b1d025
Message-ID: <19961016234959.kmyOZqrxbG6Ce2wx9e6bJnwyStdtbiK8p70rYxmjCIs@z>

the `unmatched reply' diagnostic is easy to generate by
interrupting a (user level) file server that queues requests and replies
to them out of issuing order but doesn't (quite) cope with Tflush/Rflush.
p9auth% mail 9fans
subject: unmatched replies

the `unmatched reply' diagnostic is easy to generate by
interrupting a (user level) file server that queues requests and replies
to them out of issuing order but doesn't (quite) cope with Tflush/Rflush.

rflush(void)	/* synchronous so easy */

is sometimes a clue.

dnsiplookup in ndb/cs might be a good place to start looking in your case,
but i'm just guessing.
it depends what you were trying to do when you noticed that the routing
tables had changed ...