22 Jan
2012
22 Jan
'12
8:04 a.m.
I renumbered my Ubuntu VPS at the end of december, I had thought
successfully, until this week I got an email letting me know that my
website was still using the old IP address. I didn't disable the old
address, but I did add the new one and change the address in the bind zone
file. I updated the serial number in the file, which I thought was
sufficient to send the file up the chain (pardon, my understanding of
what's really happening in this step is sketchy), but nslookup confirms
that the site is still using the old IP address. Is there something I'm
missing to get the Bitfolk nameservers to take the updated file?
Thank you,
Mike
22 Jan
22 Jan
8:09 a.m.
Hi Michael,
On Sun, Jan 22, 2012 at 02:04:31AM -0600, Michael Corliss wrote:
I renumbered my Ubuntu VPS at the end of december, I
had thought
successfully, until this week I got an email letting me know that my
website was still using the old IP address.
Do note that those emails are sent based on packet counts and it is
possible that just random Internet noise triggered it.
nslookup confirms that the site is still using the old
IP address.
First, can you let us know what the host name of the site is?
Cheers,
Andy
--
http://bitfolk.com/ -- No-nonsense VPS hosting
8:24 a.m.
The hostname is ilovephilosophy.com. It'd be great if it were just noise,
but could it show the old IP with nslookup if it had actually changed?
(sorry Andy for the duplicate, forgot to reply all)
On Sun, Jan 22, 2012 at 2:09 AM, Andy Smith <andy(a)bitfolk.com> wrote:
Hi Michael,
On Sun, Jan 22, 2012 at 02:04:31AM -0600, Michael Corliss wrote:
I renumbered my Ubuntu VPS at the end of
december, I had thought
successfully, until this week I got an email letting me know that my
website was still using the old IP address.
Do note that those emails are sent based on packet counts and it is
possible that just random Internet noise triggered it.
nslookup confirms that the site is still using
the old IP address.
First, can you let us know what the host name of the site is?
Cheers,
Andy
--
http://bitfolk.com/ -- No-nonsense VPS hosting
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
iEYEAREDAAYFAk8bxDQACgkQIJm2TL8VSQsJfgCg+cYZ+DiI8uktaKzDjsj9tHk6
9gUAn2vXFCHD4rRrKmvzndAyPTbAe4Zg
=6eUf
-----END PGP SIGNATURE-----
_______________________________________________
users mailing list
users(a)lists.bitfolk.com
https://lists.bitfolk.com/mailman/listinfo/users
9:44 a.m.
Hi Michael,
On Sun, Jan 22, 2012 at 02:24:04AM -0600, Michael Corliss wrote:
The hostname is ilovephilosophy.com. It'd be
great if it were just noise,
but could it show the old IP with nslookup if it had actually changed?
Probably not, but I wanted to be sure.
Let's see what's going on then:
$ dig +noall +answer +auth +comments -t a ilovephilosophy.com
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 55221
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 3, ADDITIONAL: 0
;; ANSWER SECTION:
ilovephilosophy.com. 86365 IN A 212.13.195.254
;; AUTHORITY SECTION:
ilovephilosophy.com. 86365 IN NS a.authns.bitfolk.com.
ilovephilosophy.com. 86365 IN NS c.authns.bitfolk.com.
ilovephilosophy.com. 86365 IN NS b.authns.bitfolk.com.
So yes, it seems DNS holds your old IP address.
Nameservers for this domain?:
$ dig +short -t ns ilovephilosophy.com
c.authns.bitfolk.com.
a.authns.bitfolk.com.
b.authns.bitfolk.com.
Only BitFolk.
What's the address record at each one, and your own server?:
$ for n in {a,b,c}.authns.bitfolk.com 85.119.83.254; do echo ${n}:; dig +short -t a
ilovephilosophy.com @${n}; done
a.authns.bitfolk.com:
212.13.195.254
b.authns.bitfolk.com:
212.13.195.254
c.authns.bitfolk.com:
212.13.195.254
85.119.83.254:
212.13.195.254
Your server has 212.13.195.254; not a BitFolk issue.
If I go to http://85.119.83.254/ then it looks like it's working.
So, your mission, should you choose to accept it, is to make your
nameserver at 85.119.83.254 return the correct address record for
ilovephilosophy.com and www.ilovephilosophy.com.
That will involve a zone update, which BitFolk's servers should then
pick up.
You can test from another unix box like this:
dig +short -t a ilovephilosophy.com @85.119.83.254
I have repressed all memories of how to check this under Windows using
nslookup.
Do let the list know if you have any problems.
Cheers,
Andy
--
"I'm /extremely/ miffed about today's events and in my quest to try to make
you understand the level of my unhappiness, I'm likely to use an awful lot
of what we would call /violent sexual imagery/ and I just wanted to check
that neither of you would be terribly offended by that." — Malcolm Tucker
4:37 p.m.
Thanks Andy, Stewart. I had neglected to run "rndc reload". After
running, Andy's test returns:
localhost:~ mcorliss$ dig +short -t a ilovephilosophy.com @85.119.83.254
85.119.83.254
The Bitfolk nameservers still show the old IP, but I think that's right.
Is it the refresh or the expire value in the zone file that dictates when
they will update? And if not specified, the default unit is seconds,
correct? This is the top of my zone file:
$TTL 86400
@ SOA ns0.bitfolk.com. hostmaster.ilovephilosophy.com. (
2011122101
14400
7200
1209600
43200)
Thanks,
Mike
On Sun, Jan 22, 2012 at 5:27 AM, Stuart Swindells <bitfolk(a)lumo.me.uk>wrote;wrote:
On 22/01/2012 08:04, Michael Corliss wrote:
I updated the serial number in the file, which I
thought was sufficient
to send the file up the chain
Unless I'm missing something, you'd also need an "rndc reload"
to get Bind
to pick up the updated zone file.
Stuart
______________________________**_________________
users mailing list
users(a)lists.bitfolk.com
https://lists.bitfolk.com/**mailman/listinfo/users<https://lists.bitfolk…
4:41 p.m.
Hi Michael,
They should have updated pretty much instantly. I'll continue this
in a support ticket.
Cheers,
Andy
On Sun, Jan 22, 2012 at 10:37:13AM -0600, Michael Corliss wrote:
Thanks Andy, Stewart. I had neglected to run
"rndc reload". After
running, Andy's test returns:
localhost:~ mcorliss$ dig +short -t a ilovephilosophy.com @85.119.83.254
85.119.83.254
The Bitfolk nameservers still show the old IP, but I think that's right.
Is it the refresh or the expire value in the zone file that dictates when
they will update?
--
http://bitfolk.com/ -- No-nonsense VPS hosting
4486
days inactive
4486
days old
6 comments
3 participants
participants (3)
-
Andy Smith -
Michael Corliss -
Stuart Swindells