Cache Corruption

Re: Cache Corruption

From:

Date:

Time:

Here's what I get when I query your server:

- A cached negative response for the address in question.
- A cached authority response for in-addr.arpa:

in-addr.arpa. 81762 NS ipdns1.hinet.net.
in-addr.arpa. 81762 NS ipdns2.hinet.net.
ipdns1.hinet.net. 49227 A 168.95.192.14
ipdns2.hinet.net. 49227 A 168.95.1.14

So the question is, why does your server think this? Why does it
believe what the hinet.net servers told it?

It would be useful if you could figure out what reverse zone is
delegated to these servers. I know, this is not an easy task. After
all, the reverse zones that contain the PTR records for these servers
themselves are handled by some other servers in the hinet.net
organization.

I will see if our engineers can figure this out. Please don't reset
this machine if you can help it.
____________________________________________________________________
Chris Buxton Men & Mice
cbuxton@menandmice.com We Make DNS Easy!

At 12:56 PM -0500 8/13/01, Jerry Pasker wrote:
>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

Sales:
888/4-DPOINT

Support:
858/452-3696