Re: SMTP

[Scott Klement <midrange-l@xxxxxxxxxxxxxxxx>]

You changed your domain?   I.e. you changed from cross-check.com to 
something else (example.com or something).

While changing the resolver to point to different records (i.e. 
CHGTCPDMN) will update your i5/OS to see the new values, those values 
won't be recognized by everything else until DNS propagates.  Take a 
look at the Maximum number on the SOA to determine the longest time it 
can take for a secondary to update.  Then, take a look at the individual 
TTL on each record for an idea of how long it'll take for the records to 
totally propagate after the secondaries have updated.  (These are 
maximum numbers, of course, many servers will update much sooner...)


Chris Bipes wrote:
> Scott,
>
> Perhaps you know, when changing TCP Domain CHGTCPDMN and in particular
> changing the DNS servers, When does the changes get picked up for the
> SMTP job?  I thought that end/start SMTP would work.  NSLOOKUP works.
> PING works.  I changed the WIN in NETSERVER and that was picked up with
> a restart but SMTP just would not send emails.  Forcing through MSF
> worked though.  Go figure.  I did not journal so there was no help
> there.  Now I am forwarding all through our mail server, using MSF and
> have journaling on.  Now mail is flowing.  Go Figure.
>
> Christopher Bipes
> Information Services Director
> CrossCheck, Inc.