subdomain not updating, mapped to diff IP

I have a subdomain that I've mapped to a different IP through an A record on my server. Here is the record:

$TTL 86400

@ IN SOA ns.relientk.com. greg.gotee.com. (
1091569904 ; Serial
10800 ; Refresh
3600 ; Retry
604800 ; Expire
86400 ) ; Minimum

relientk.com. IN NS ns.relientk.com.
ns.relientk.com. IN A 64.207.133.130
relientk.com. IN A 64.207.133.130
webmail.relientk.com. IN A 64.207.133.130
mail.relientk.com. IN A 64.207.133.130
forums.relientk.com. IN A 69.57.138.93
ftp.relientk.com. IN CNAME relientk.com.
www.relientk.com. IN CNAME relientk.com.
relientk.com. IN MX 10 mail.relientk.com.

forums.relientk.com is the subdomain that I set up. First off I need to know if I've done this correctly. I thought it was, a linux host query shows that it is mapping to that IP but it still returns goes to 64.207.133.130 instead. The second problem is that the first time I created the record I accidentally entered the IP as 64.57.138.93 rather than 69.57.138.93 Whenever I query shell>host forums.relientk.com it still shows the incorrect IP. I've tried restarting my BIND and Apache several times and nothing seems to flush out the old record. Any idea whats going on?

Thanks,
Greg

It appears that you use a TTL of 1 day and since I'm guessing your resolv.conf lists a server other than your own, the resolver server has the previous IP cached. The old IP will expire sometime tomorrow.

Would this be a caching issue from another server? I thought that since this was a subdomain that an outside name server would first resolve to my server which would then point the subdomain to the correct IP. The curious thing is that when I'm logged into my server through SSH and I run shell>host forums.relientk.com it shows me the incorrect IP I entered yesterday 64.57.138.93 but when I run the same command from my machine I get my original server's IP 64.207.133.130. I can't see that I have the 64.57.138.93 IP entered in any records at all.

ok, I suppose we'll take a look, even if it's only to see how long you got to wait for the cache to expire. On the machine that you get the wrong IP address, I want to see the results these commands:

(if it's a windows machine)

ipconfig /all

(if it's a linux machine)

cat resolv.conf

I'm on a linux box running RH9. Here's what I came up with on cat resolv.conf:

nameserver 64.207.128.21
nameserver 64.207.129.21

Any ideas? Is there anyway to force a refresh of that server?

Thanks,
Greg

looks like the correct IP is resolving out in Texas now. If only it'd make its way out to TN! Thanks for the help.

--Greg

to find out how long you gotta wait, make this query:

dig @64.207.128.21 forums.relientk.com

The TTL value will tell you how many seconds that information will remain in cache. If you have access to the server then yes, there's a way to make it flush out the old info. Otherwise, you gotta wait. Perhaps change the TTL on your zone so that you don't have to wait so long next time.