|
|
 |  |
Re: Cache CorruptionFrom: Jerry Pasker Date: Monday, August 13, 2001
Time: 11:43:50 am266 iMac, with 160MB RAM, OS 9.1 VM is off. QDNS Pro 3.0. I'm blocking
TCP Port 53 at my router, to prevent the TCP attack on the server, and
shield all my BIND running colo customers. Gave QDNS Pro about 100MB of RAM
to work with, QDNS currently has about 40MB of RAM free, so it's got
probably close to 60MB or so of DNS data cached.
It's been running since August 3rd, when I formatted the box and put a
clean install of OS 9.1 on it.
Do you have *ANY* idea how hard it is to find a bad DNS record when there's
that much cached data? <g>
And no, I've not 'automated' the process. Trial and error.
>what kind of box is it?
>----- Original Message -----
>From: "Jerry Pasker" <info@n-connect.net>
>To: "QuickDNS Talk" <quickdns-talk@lists.menandmice.com>
>Sent: Monday, August 13, 2001 1:56 PM
>Subject: Cache Corruption
>
>
>> I think I've finnaly figured out why QDNS Pro isn't as stable as my SIMS
>> box, MacRADIUS box, or WebSTAR box. My primary QDNS server's cache
>> corrupts. I'm assuming the corruption then leads to a crash.
>>
>> To see what I'm talking about:
>>
>> Using QDNS Expert, (set to "Any record")........
>>
>> First, do a DNS lookup on 209.207.1.10 using your own DNS server(s).
>>
>> Then, do the same lookup using my dns(208.245.212.3) server, and notice
>> that it gives incorrect data.
>> Using my seccondary DNS server (208.245.212.2) will give correct data.
>>
>> My primary dns server (208.245.212.3) will crash within a few hours of
>> giving bad data. I've only been lucky enough to catch this just before the
>> machine crashed, on one other occasion. Of course, restarting it right
>> now would fix this, but I want someone else to verify that my dns server's
>> cache is corrupted.
>>
>> -Jerry
>>
>>
>>
|

Return to Digital Point Solutions' Home Page |