As far as I know, the only "special" thing that BIND does consistently on a
restart, that it doesn't do on a regular basis in normal operation, is a
"priming" query to whatever is configured as root nameservers. I suppose it's
_possible_ that there is something about priming queries, particularl
Even home routers sometimes try to police DNS traffic and I would
expect there is a bug in the code doing that.
As this is a ISP supplied router (if my Google Foo is accurate)
report the fault to the ISP. It is their job to fix it.
If it wasn't a ISP supplied router, update the router firmware
Chris,
First, what a strange problem to have.
You really need to spend some time capturing the traffic placed on the wire via
tcpdump and then slicing it up for clues with wireshark.
If you set a continuous ping to the router that would be a good timestamp that
you can use to correlate as a ma
3 matches
Mail list logo
