WARNING: MyBatis.org IP Address Change -- watch your DTD in production...

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

WARNING: MyBatis.org IP Address Change -- watch your DTD in production...

Clinton Begin
Administrator
Hi all,

This is just a quick note that I've changed the host for MyBatis.org.  The new IP Address is:  184.106.174.238

You might want to do a ping/trace from your production servers to make sure that mybatis.org resolves to this IP address and no other.  The TTL has always been set really low on the mybatis.org DNS configuration.  But some servers, sites, ISPs or even companies tend to ignore TTL and hold onto it too long (or not long enough, but that's not a problem in this case).

Normally MyBatis should not access the DTD on the web (except maybe from within an IDE during development).   But in some cases despite the custom entity resolver etc... some app servers or XML parsers will do it anyway. 

Do a quick spot check on your production servers to ensure that mybatis.org resolves to the correct IP address, before the old one disappears in less than a month.

Cheers,
Clinton
Reply | Threaded
Open this post in threaded view
|

Re: WARNING: MyBatis.org IP Address Change -- watch your DTD in production...

Clinton Begin
Administrator

FYI:  The IP address for mybatis.org, including DTD hosting is now going to change again.  

The new IP Address is:  97.74.144.93

The TTL for the domain is only 1 hour, but you might want to be sure and flush your DNS caches, including the JVM DNS cache (which may require a restart of your JVM).  

Sorry for the inconvenience.

Clinton



On Mon, Sep 5, 2011 at 9:54 AM, Clinton Begin <[hidden email]> wrote:
Hi all,

This is just a quick note that I've changed the host for MyBatis.org.  

You might want to do a ping/trace from your production servers to make sure that mybatis.org resolves to this IP address and no other.  The TTL has always been set really low on the mybatis.org DNS configuration.  But some servers, sites, ISPs or even companies tend to ignore TTL and hold onto it too long (or not long enough, but that's not a problem in this case).

Normally MyBatis should not access the DTD on the web (except maybe from within an IDE during development).   But in some cases despite the custom entity resolver etc... some app servers or XML parsers will do it anyway. 

Do a quick spot check on your production servers to ensure that mybatis.org resolves to the correct IP address, before the old one disappears in less than a month.

Cheers,
Clinton