|
|
On Jul 14, 2:51 pm, Jim <mckinn...@xxxxxxxx> wrote:
> On Jul 7, 7:43 pm, Malcolm Dunnett <noth...@xxxxxxxxxxxxxxxxx> wrote:
>
>
>
>
>
> > Jim wrote:
>
> > > Here's what has worked for me prior to MN 5.2...
>
> > > SERVER-CONFIG>show/full domain
> > > Service "DOMAINNAME":
> > > INIT() = Merge_Image
> > > Program = "MULTINET:LOADABLE_NAMED_CONTROL"
> > > Parameters = "rewrite-ttl 0"
>
> > That doesn't appear to work on MN 5.2 on Alpha. When I
> > put it in the parameters it ignores it on a server
> > restart (ttl stays at 5 minutes). If I try to enter
> > it directly as a NETCONTROL command I get an error:
>
> > $mu netcon domain rewrite-ttl 60
> > Connected to NETCONTROL server on "LOCALHOST"
> > < malvm9.mala.bc.ca Network Control V5.2(10) at Mon 7-Jul-2008 4:40PM-PDT
> > < Query error, %SYSTEM-F-ILLIOFUNC, illegal I/O function code
>
> And now that I've gotten DNS load balancing working again (with
> assistance from Mike Corbett), I can see that this no longer works on
> IA64 either. I suspect that the TTL was applied when the A records
> were constructed on the fly and now the value is being taken from the
> zone file. It had been our practice to set the TTL for these RRs to 0
> to prevent caching and the associated round robin-ing (as might be
> prevalent when larger terminal servers are used).Looks like this will
> no longer be possible...
It appears that a "$ttl n" directive in your zone master file, where n
is an integer (I've tried as low a 1), will permit you to control the
TTL on the A RRs.
|
|