which<br>will explicitly=
bypass the locally configured resolvers, and query the<br>named DNS server=
.<br><br>hrm@ruthven:~ $ dig @ns1.bb-online.net. oxfordflutes.co.uk<br>[...=
]<br><br> In this case, I'm querying one of the
definitive servers for<br>oxfordflutes.net, and so should get the results =
that I've asked them<br>to publish. You can check whether the DNS servers u=
nder your control<br>(usually the primary and one or more secondaries) are =
sending the<br>right answers. If they are, then you should simply have to w=
ait until<br>the TTL in the previous query reaches zero. If not, then you h=
ave some<br>kind of misconfiguration of your servers.<br><br> &n=
bsp;Oh, and you should be able to get the definitive list of<br>nameservers=
by issuing an NS query:<br><br>hrm@ruthven:~ $ dig NS oxfordflutes.co.uk<b=
r><br>; <<>> DiG 9.7.3 <<>> NS oxfordflutes.co.uk<b=
r>;; global options: +cmd<br>;; Got answer:<br>;; ->>HEADER<<- =
opcode: QUERY, status: NOERROR, id: 43912<br>;; flags: qr rd ra; QUERY: 1, =
ANSWER: 3, AUTHORITY: 0, ADDITIONAL: 0<br><br>;; QUESTION SECTION:<br>;oxfo=
rdflutes.co.uk.
IN NS<br><br>;; AN=
SWER SECTION:<br>oxfordflutes.co.uk. 8=
6400 IN NS &nbs=
p; brain.bb-online.co.uk.<br>oxfordflutes.co.uk.&n=
bsp; 86400 IN &=
nbsp; NS ns1.bb-onl=
ine.net.<br>oxfordflutes.co.uk. 86400&=
nbsp; IN NS &nb=
sp; ns2.bb-online.net.<br><br>;; Query time: 48 msec<br>=
;; SERVER: 10.0.0.10#53(10.0.0.10)<br>;; WHEN: Tue Feb 7 21:54:55 201=
2<br>;; MSG SIZE rcvd: 115<br><br> So here my defini=
tive nameservers are brain, ns1 and<br>ns2.bb-online.net. Check the d=
ata returned by all of the servers<br>(with the @server syntax
above) for the NS query, just to see if one<br>is out of sync with the oth=
ers.<br><br> Hugo.<br><br>-- <br>=3D=3D=3D Hugo Mills: hug=
o@... carfax.org.uk | darksatanic.net | lug.org.uk =3D=3D=3D<br> PGP =
key: 515C238D from wwwkeys.eu.pgp.net or <a href=3D"
http://www.carfax.org.u=
k" target=3D"_blank">
http://www.carfax.org.uk</a><br> &=
nbsp; --- UNIX: Japanese brand of food containers. ---&=
nbsp; <br></div></blockquote></td></tr><=
/table>
---453615747-1753851572-1328812433=:87945--
From ian@??? Fri Feb 10 13:54:15 2012
Received: from semi-divine.com ([85.119.83.38] helo=topcat.semi-divine.com)
by mail.bitfolk.com with esmtp (Exim 4.72)
(envelope-from <ian@???>) id 1RvqvX-0001TA-Nr
for users@???; Fri, 10 Feb 2012 13:54:15 +0000
Received: from [192.168.0.23]
(cpc3-nwrk4-2-0-cust250.12-1.cable.virginmedia.com [86.26.44.251])
by topcat.semi-divine.com (Postfix) with ESMTPSA id B94E8842FC
for <users@???>; Fri, 10 Feb 2012 13:54:12 +0000 (UTC)
Message-ID: <4F352183.4070708@???>
Date: Fri, 10 Feb 2012 13:54:11 +0000
From: Ian <ian@???>
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
rv:9.0) Gecko/20111229 Thunderbird/9.0
MIME-Version: 1.0
To: users@???
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Virus-Scanner: Scanned by ClamAV on mail.bitfolk.com at Fri,
10 Feb 2012 13:54:15 +0000
X-SA-Exim-Connect-IP: 85.119.83.38
X-SA-Exim-Mail-From: ian@???
X-SA-Exim-Scanned: No (on mail.bitfolk.com); SAEximRunCond expanded to false
Subject: [bitfolk] IP address at Nominet's nameservers is wrong
X-BeenThere: users@???
X-Mailman-Version: 2.1.11
Precedence: list
List-Id: Users of BitFolk hosting <users.lists.bitfolk.com>
List-Unsubscribe: <https://lists.bitfolk.com/mailman/options/users>,
<mailto:users-request@lists.bitfolk.com?subject=unsubscribe>
List-Archive: <http://lists.bitfolk.com/lurker/list/users.html>
List-Post: <mailto:users@lists.bitfolk.com>
List-Help: <mailto:users-request@lists.bitfolk.com?subject=help>
List-Subscribe: <https://lists.bitfolk.com/mailman/li
