7 Nov
2011
7 Nov
'11
7:04 p.m.
Not a problem but may be when I remove the 212.13 address from my VPS
When I first took on this VPS, I was unable immediately to switch my domain
name across, so it was called wnrspca.vps.bitfolk.com This weekend, I did
the renumbering on it and it went so smoothly, I thought I must have done
something wrong. I changed the DNS A record etc for the domain hosted on it
- westnorfolkrspca.org.uk. Everything is working and as I had prepared for
the change by setting TTL on the nameserver to 15 minutes, by the end of
the day, the old address was history and all was working well.
This evening, I was thinking about the log in for the console and realised
I use wnrspca.vps.bitfolk.com as the access address, so I did a dig of that
name and it came up with the old 212.13 address. Perhaps I ought to put off
removing the old address for a while
Andy, is that something on your todo list or do you want me to raise a
support ticket?
Keith
--
Keith Williams
If the only tool you have is a hammer, you tend to see every problem as a
nail.
- Abraham Maslow
ทำดีได้ดี ทำชั่วไดชั่ว
7 Nov
7 Nov
7:50 p.m.
Hi Keith,
On Mon, Nov 07, 2011 at 07:04:45PM +0000, Keith Williams wrote:
This evening, I was thinking about the log in for the
console and realised
I use wnrspca.vps.bitfolk.com as the access address, so I did a dig of that
name and it came up with the old 212.13 address. Perhaps I ought to put off
removing the old address for a while
I must admit I had completely failed to consider the
<acct>.vps.bitfolk.com names.
I don't know what is best to do about them.
If I change them all now, then anyone using them who hasn't yet
renumbered will end up being directed to something that doesn't
respond.
I can't see any way out of this other than having people who use
those names put in a support ticket when they are ready to have them
switched. :(
Cheers,
Andy
--
http://bitfolk.com/ -- No-nonsense VPS hosting
8:10 p.m.
I feared that may be the case.
I can leave both addresses on the VPS for a couple of weeks, but put a
support ticket in, then you could save them up till you have a big enough
batch to make it worthwhile looking at. Alternatively you could do the
whole batch on the deadline day as anyone who hasn't changed by then would
be cut off anyway (that sounds cruel I know) I am in no hurry to remove the
old one as everything else is working OK on the new address.
I am beginning to look at IPv6 with a view to getting it all up and running
properly when we have the v6 renumbering next year. Just out of interest,
my interfaces files on both VPS show the correct v6 IPs but have gateways
starting fe80: that must be wrong according to the wiki article. Anyway
that's another tale for another day
Keith
On 7 November 2011 19:50, Andy Smith <andy(a)bitfolk.com> wrote:
Hi Keith,
On Mon, Nov 07, 2011 at 07:04:45PM +0000, Keith Williams wrote:
--
Keith Williams
If the only tool you have is a hammer, you tend to see every problem as a
nail.
- Abraham Maslow
ทำดีได้ดี ทำชั่วไดชั่ว
This evening, I was thinking about the log in for
the console and
realised
I use wnrspca.vps.bitfolk.com as the access
address, so I did a dig of
that
name and it came up with the old 212.13 address.
Perhaps I ought to put
off
removing the old address for a while
I must admit I had completely failed to consider the
<acct>.vps.bitfolk.com names.
I don't know what is best to do about them.
If I change them all now, then anyone using them who hasn't yet
renumbered will end up being directed to something that doesn't
respond.
I can't see any way out of this other than having people who use
those names put in a support ticket when they are ready to have them
switched. :(
Cheers,
Andy
--
http://bitfolk.com/ -- No-nonsense VPS hosting
_______________________________________________
users mailing list
users(a)lists.bitfolk.com
https://lists.bitfolk.com/mailman/listinfo/users
8 Nov
8 Nov
10:30 a.m.
2011/11/7 Keith Williams <keithwilliamsnp(a)gmail.com>
I am beginning to look at IPv6 with a view to getting it all up and
running properly when we have the v6 renumbering next year. Just out of
interest, my interfaces files on both VPS show the correct v6 IPs but have
gateways starting fe80: that must be wrong according to the wiki article.
Anyway that's another tale for another day
This IPv6 is a steep learning curve! The fe80 addresses are link-local
IPs. It's all beginning to make sense now
--
Keith Williams
If the only tool you have is a hammer, you tend to see every problem as a
nail.
- Abraham Maslow
ทำดีได้ดี ทำชั่วไดชั่ว
9 Nov
9 Nov
2:21 p.m.
Hi,
Could you create a new subdomain and populate it with the new IP
addresses using a script?
e.g. redfox.vps.bitfolk.com = old 212 address,
redfox.new.vps.bitfolk.com = new IP address.
That way we would have working DNS A records for the new IP addresses
and could change then submit the ticket to change the .vps.bitfolk.com
addresses.
That would meet my needs. Would it work for others?
Cheers,
Paul.
3:08 p.m.
Hi Paul,
On Wed, Nov 09, 2011 at 02:21:43PM +0000, Paul Stimpson wrote:
Could you create a new subdomain and populate it with
the new IP
addresses using a script?
This could be done, but..
That way we would have working DNS A records for the
new IP addresses and
could change then submit the ticket to change the .vps.bitfolk.com
addresses.
From my point of view this still involves having
support tickets,
but with some more work besides.
That would meet my needs.
What are your needs? Can't you just use the IP address until you've
put a support ticket in to have redfox.vps.bitfolk.com changed?
I never really considered that someone running a server would not
have a domain name that they could use (you can get them for free),
and only ever intended the <account>.vps.bitfolk.com thing to be a
convenience for people in the time between ordering a VPS and
sorting out their own domain name.
Are there really so many of you out there with no domain name of
your own such that you're relying on <account>.vps.bitfolk.com
resolving to the correct place?
The point of some <account>.new.vps.bitfolk.com seems quite tenuous;
what would you be using it for that an IP address wouldn't suffice?
It would after all be temporary so I can't really imagine its
purpose.
Cheers,
Andy
--
http://bitfolk.com/ -- No-nonsense VPS hosting
3:17 p.m.
I didn't even realise those records existed until this week - I don't have one
for my VPS! (I don't need one either... :-) )
Paul
-----Original Message-----
From: users-bounces+paul=pjlewis.org(a)lists.bitfolk.com
[mailto:users-bounces+paul=pjlewis.org@lists.bitfolk.com] On Behalf Of Andy Smith
Sent: 09 November 2011 15:08
To: users(a)lists.bitfolk.com
Subject: Re: [bitfolk] Small issue related to renumbering
Hi Paul,
On Wed, Nov 09, 2011 at 02:21:43PM +0000, Paul Stimpson wrote:
Could you create a new subdomain and populate it with
the new IP
addresses using a script?
This could be done, but..
That way we would have working DNS A records for the
new IP addresses
and could change then submit the ticket to change the .vps.bitfolk.com
addresses.
From my point of view this still involves having
support tickets, but with some more work besides.
That would meet my needs.
What are your needs? Can't you just use the IP address until you've put a support
ticket in to have redfox.vps.bitfolk.com changed?
I never really considered that someone running a server would not have a domain name that
they could use (you can get them for free), and only ever intended the
<account>.vps.bitfolk.com thing to be a convenience for people in the time between
ordering a VPS and sorting out their own domain name.
Are there really so many of you out there with no domain name of your own such that
you're relying on <account>.vps.bitfolk.com resolving to the correct place?
The point of some <account>.new.vps.bitfolk.com seems quite tenuous; what would you
be using it for that an IP address wouldn't suffice?
It would after all be temporary so I can't really imagine its purpose.
Cheers,
Andy
--
http://bitfolk.com/ -- No-nonsense VPS hosting
_______________________________________________
users mailing list
users(a)lists.bitfolk.com
https://lists.bitfolk.com/mailman/listinfo/users
3:23 p.m.
Hi Paul,
On Wed, Nov 09, 2011 at 03:17:30PM +0000, Paul Lewis wrote:
I didn't even realise those records existed until
this week - I don't have one for my VPS! (I don't need one either... :-) )
Only people with no domain at sign up have them, so that they would
have some fully-qualified host name and reverse DNS. I really only
imagined it to be temporary for them..
Cheers,
Andy
--
http://bitfolk.com/ -- No-nonsense VPS hosting
3:36 p.m.
Oh! I have a *.vps.bitfolk.com name for a VPS because of the reason that
Andy gave. Only ever use it to get to the console, my "proper" domain name
is what I always use for everything. Never thought to ask Andy to make any
change because I thought, it does no harm so no point in making work
unnecessarily.
I'll go sort out the reverse DNS in the panel now then to point to my IP to
my real domain and the old name can be scrapped
Keith
On 9 November 2011 15:23, Andy Smith <andy(a)bitfolk.com> wrote:
Hi Paul,
On Wed, Nov 09, 2011 at 03:17:30PM +0000, Paul Lewis wrote:
--
Keith Williams
If the only tool you have is a hammer, you tend to see every problem as a
nail.
- Abraham Maslow
ทำดีได้ดี ทำชั่วไดชั่ว
I didn't even realise those records existed
until this week - I don't
have one for my VPS! (I don't need one either...
:-) )
Only people with no domain at sign up have them, so that they would
have some fully-qualified host name and reverse DNS. I really only
imagined it to be temporary for them..
Cheers,
Andy
--
http://bitfolk.com/ -- No-nonsense VPS hosting
_______________________________________________
users mailing list
users(a)lists.bitfolk.com
https://lists.bitfolk.com/mailman/listinfo/users
3:17 p.m.
Hi,
On 09/11/11 15:08, Andy Smith wrote:
Are there really so many of you out there with no
domain name of
your own such that you're relying on<account>.vps.bitfolk.com
resolving to the correct place?
The point of some<account>.new.vps.bitfolk.com seems quite tenuous;
what would you be using it for that an IP address wouldn't suffice?
It would after all be temporary so I can't really imagine its
purpose.
Cheers,
Andy
TBH, you're right. It wasn't a very well thought out suggestion. I might
as well put in an ip address.
Do you think you may automate the process of the DNS switch? If so would
you rather we waited until that is in place to save you the support
tickets or did it now to get it out the way?
Cheers,
Paul.
3:32 p.m.
On Wed, Nov 09, 2011 at 03:17:54PM +0000, Paul Stimpson wrote:
Do you think you may automate the process of the DNS
switch?
Just to be sure we're talking about the same thing, I take this to
mean the addresses that <account>.vps.bitfolk.com points to..
If so would you rather we waited until that is in
place to save
you the support tickets or did it now to get it out the way?
As I say I have to admit I didn't consider these host names before
we started, but now that the renumbering is underway it seems to me
that changing what they point to en masse at any particular time is
going to cause some problems for some people who are making use of
them. The mapping would change before some people are ready.
Meanwhile it seems likely that if the <account>.vps.bitfolk.com
hosts continue to point at the old IP addresses until we are asked
to change them, then this will cause least disruption. The mapping
won't change but would still be pointing at an IP address that most
likely works.
So, at the moment it seems like the best thing to do is wait for
support tickets asking for this mapping to be changed.
Cheers,
Andy
--
http://bitfolk.com/ -- No-nonsense VPS hosting
4800
days inactive
4802
days old
10 comments
4 participants
participants (4)
-
Andy Smith -
Keith Williams -
Paul Lewis -
Paul Stimpson