[bitfolk] Renumbering: resolver not working? still points to 212.x, instead of 85.y on >=1 machine

Hi all, thanks for everyone's response to my wiki proposal.  I hadn't intended a flame war, and may respond selectively at a future date, when for instance, I am not faced with a puzzle, as follows. dig returns the correct value 85.y on my VPS. dig returns the old address 212.x elsewhere (at work). Should I be concerned?  I must access the ethernet address to my VPS--not the name--from 'elsewhere'.  I changed bind at least 24h ago.  Is the 'expire' time* of 7 days (current setting) responsible for this, or is my problem more insidious? *the third entry after the 'serial number' in a bind config Thanks for any/all replies.   Cheers, Max