IP address change not being propagated

[Peter H. Lemieux]

Recently one of my clients changed ISP's, and we published new IP
address mappings for all their hosts and domains.  Everything has worked
fine with one exception.  If you look up www.seacoins.com on some
nameservers they report the old address 207.94.138.2, not the correct
address of 12.25.42.244.  

For instance,
[phl at psyduck public_html]$ host www.seacoins.com ns.novell.com
Using domain server:
Name: ns.novell.com
Address: 137.65.1.1
Aliases:
 
www.seacoins.com has address 207.94.138.2  

yet other places have the correct data:

[phl at psyduck public_html]$ host www.seacoins.com ns1.shore.net
Using domain server:
Name: ns1.shore.net
Address: 192.233.85.129
Aliases:
 
www.seacoins.com has address 12.25.42.244

I haven't a clue as to why some nameservers are correctly updated, but
others are not.  The primary nameservers have the correct information,
and even nameservers that report the wrong A info have correct SOA
records with the most recent serial number!  It's as if they check with
the primary and get everything but the A records.

I've wondered if there's some way to redirect in-addr.arpa queries to a
different IP address.  That is, can I make 2.138.94.207.in-addr.arpa
send people to 12.25.42.244? 

Help!

Peter