Not exactly, our domain did not change, our DNS server did. We had only
one DNS server for internal and AD integration. Mirrored drives and
both failed within two days. We ordered the replacement for the first
failure, then the second failed. What luck. We had to rebuild our AD
integrated DNS zones from scratch. Our DNS servers have new IP address
and that is what I change on the 400.
Christopher Bipes
Information Services Director
CrossCheck, Inc.
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[
mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Scott Klement
Sent: Monday, April 02, 2007 2:35 PM
To: Midrange Systems Technical Discussion
Subject: Re: SMTP
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...)
midrange.com
