In article <ssm.3jlxmn@no-mx.forums.novell.com>, Ssm wrote:
> Any pointers would be appreciated
>
Every now and then I'd seen this in the past, but not recently. I did
find at one time that I had a lot better results by not mixing public
and private DNS entries, and best results pointing to internal only DNS
servers. I still don't know why, and that was only on some servers,
while others were fine.
I think it would be a good idea to use PKTSCAN on the server to grab a
packet trace, and then use Wireshark to look at the DNS packets to see
if you can find a pattern there.
I've also seen cases in the past where certain LAN drivers were very
bad with UDP packets, though I don't know why your problem would have
just started now. Don't overlook troubleshooting lan drivers, and NIC
issues in general though.
For now, start by checking your patches against tip #1 at the URL
below. And at least for a test, try pointing just to the internal DNS
server and see if that helps. But since this problem came up all of a
sudden on a previously-working system, I'm suspecting there is a
problem on the wire, and a packet trace will show some signs of it.
Craig Johnson
Novell Support Connection SysOp
*** For a current patch list, tips, handy files and books on
BorderManager, go to
http://www.craigjconsulting.com ***