Search Again:

Re: Secondarying

From: Men & Mice Support
Date: Friday, September 10, 1999
Time: 8:56:00 pm

>I've just added the first couple of secondary addresses to Quick DNS Pro.
>This seems to be a no brainer (add domain, spec unique name for file,
>list primary server(s)) but it ain't workin' yet.
>
>As the weekend's cropping up, can someone just confirm that's all I need
>to do? If so, I know that the problem's with the primary.

Domain name, unique file name, address of primary server. Yup, that's it.

>Running DNS Expert over the domain (ldml.com) I'm getting a lame
>delegation together with a comment that the PTR records haven't been set
>up. I'm reasonably sure that this was done on the primary but I may have
>done something stupid like not saving the changes or whatever. I'm not
>with the primary at the moment and I don't have remote access to it so
>I'll check tonight.

The lame delegation message is coming up because the secondary
(ns.gjint.co.uk) isn't set up properly.

The PTR record errors are caused by the fact that delegation for these
addresses ends at the class B subnet. Your servers are not authoritative
for the reverse zone.

>So, all this wasted bandwidth is simply to ask that setting up
>secondary's is as easy as the three quick steps above.
>
>Ooo, no, additional quick question. Our webserver/QDNS machine is
>generally rock solid (touch wood) but on shut down we get it locking
>solid so we have to powercycle it. A brain cell sort of nagged that there
>was a (documented) problem with QDNS which may have been fixed with an
>upgrade so I installed 2.2.1 (from 2.2) yesterday? Time will tell whether
>this has cured the problem but some confirmation or denial of QDNS as a
>likely culprit for this hard crash would be appreciated.

If you can install MacsBug and reproduce the problem, then create a
standard log output, please forward it to our support address
(support@menandmice.com). We'll take a look and try to determine if it's
caused by QuickDNS Pro.

However, please do not downgrade to 2.2 just to reproduce the problem. I
don't recall exactly what was fixed, but I know there was at least one
crashing bug resolved with the update.
____________________________________________________________________
Chris Buxton Men & Mice
cbuxton@menandmice.com http://www.menandmice.com



Messages In This Thread:



Return to Digital Point Solutions' Home Page