Thanks to all who replied.=A0 I decided to wait out the 48hrs left on the l=
ocal nameserver (Hugo's tip) and then the problem sorted itself. :)
Valuable tips might like these ought to be compiled into a sysadmin pocketb=
ook: 'wisdom from bitfolk'.
Cheers!
--- On Tue, 2/7/12, Hugo Mills <hugo-bf@???> wrote:
From: Hugo Mills <hugo-bf@???>
Subject: Re: [bitfolk] Renumbering: resolver not working? still points to 2=
12.x, instead of 85.y on >=3D1 machine
To: "Max B" <txtmax@???>
Cc: users@???
Received: Tuesday, February 7, 2012, 9:59 PM
On Tue, Feb 07, 2012 at 12:56:19PM -0800, Max B wrote:
> thanks for everyone's response to my wiki proposal.=A0 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.
>=20
> dig returns the old address 212.x elsewhere (at work).
=A0=A0=A0Two things you can look at: dig tells you the TTL remaining on any
entry when you query it. For example:=20
=A0=A0=A0The "86397" in the ANSWER SECTION is the TTL, and shows that I've
got a few seconds short of 24 hours left for this entry in the cache.
This value will count down to zero, at which point the cache expires
and a new authoritative entry (hopefully the right one) will be
retrieved.
=A0=A0=A0The other thing is to use "@servername" in your dig query, which
will explicitly bypass the locally configured resolvers, and query the
named DNS server.
=A0=A0=A0In this case, I'm querying one of the definitive servers for
oxfordflutes.net, and so should get the results that I've asked them
to publish. You can check whether the DNS servers under your control
(usually the primary and one or more secondaries) are sending the
right answers. If they are, then you should simply have to wait until
the TTL in the previous query reaches zero. If not, then you have some
kind of misconfiguration of your servers.
=A0=A0=A0Oh, and you should be able to get the definitive list of
nameservers by issuing an NS query:
