IP Migration

In an attempt to organize and make our servers easier to manage, we will be adjusting our current IP allocation. This should not cause any downtime as we will make the transition as seamless as possible. We will maintain old and new IPs simultaneously to prevent DNS propagation errors.

There are a few reasons for this:

1) The 65.57 IP Blocks are not ours and we would like to move off these blocks entirely. We have already been doing this for quite a bit, and stopped allocating these IPs to machines months ago. Some older machines still use these IPs for their main/shared IP and we will be migrating these ones to the new IPs.

2) A few "logical" services coexist on the same "physical" server. When the logical servers were setup, they were all setup with the same IP address. By changing the IPs for these services, the services can be split up so that each has its own physical server. The two physical servers are: CP/NS1 and NS/MySQL/Pg/Mail. Today we are working on assigning these services their new IPs and updating the DNS records. In a few weeks, we will be moving the services to their own machines using the new IPs, so the only downtime will be the actual content move, approx. 2 hours per service.

3) We have recently acquired many new IP blocks, so we now have the chance to organize our servers. By keeping the main IPs of our servers on the same IP Block, it reduces the internal traffic through the router, removes a hop, and speeds up the transfer between the servers. This should prevent the servers from bottlenecking at the router, since they will avoid it entirely.

The new IP Map is below. There is plenty of room for expansion and you should be able to estimate the upcoming IPs for our servers.


// Misc. Servers
216.157.145.2 - cp.hsphere.cc
216.157.145.3 - sitestudio.hsphere.cc
216.157.145.4 - Urchin
216.157.145.5 - Webmail

// NAME SERVERS
216.157.145.10 - ns.hsphere.cc
216.157.145.11 - ns1.hsphere.cc
216.157.145.12 - ns2.hsphere.cc
216.157.145.13 - ns3.hsphere.cc

// MAIL SERVERS
216.157.145.20 - mail.hsphere.cc
216.157.145.21 - mail1.hsphere.cc
216.157.145.22 - mail2.hsphere.cc
216.157.145.23 - mail3.hsphere.cc

// MySQL Servers
216.157.145.40 - mysql.hsphere.cc
216.157.145.41 - mysql1.hsphere.cc
216.157.145.42 - mysql2.hsphere.cc

// PgSQL Servers
216.157.145.50 - pgsql.hsphere.cc
216.157.145.51 - pgsql1.hsphere.cc

// MSSQL Servers
216.157.145.60 - mssql.hsphere.cc
216.157.145.61 - mssql1.hsphere.cc
216.157.145.62 - mssql2.hsphere.cc
216.157.145.63 - mssql3.hsphere.cc

// Win Servers
216.157.145.1XX - ntXX.hsphere.cc
IE: 216.157.145.104 - nt4.hsphere.cc

// Web Servers
216.157.145.2xx - unixxx.hsphere.cc
IE: 216.157.145.200 - unix.hsphere.cc

Posted web server IP addresses will not necessarily be used as the shared IP for sites on a given server. Changes to shared IP addresses will be posted separately.

[Brangwyn]

Any particular reason your putting all DNS on the same C class ? I think many would prefer if you could keep them at least on differen't ranges if possible to make life easier with those registrars who insist upon primary and secondary nameservers not being in the same C Class Range.

Well, they complain regardless, never seen it as an issue causing people to not be able to register nameservers... so they only "warn" because they think one should be in physically different spots.

[Brangwyn]

Fair enough, personally I've never had a problem either, but there have been people here on the forum that have said their registrar refused to accept the nameservers because of it, so there definately are some registrars making a fuss over it.

Could you point me out a post? And if they are refusing as is, then it wont matter

[Brangwyn]

Was a good few months back (like 8 or so) I'll see if I can find the post, recall it was either a UK or european registrar that the post referred too.

[Brangwyn]

Well this definately isn't the post I was thinking of, but it implies .ru requires separate C Class nameservers, have a funny feeling .dk does as well and several other 2LD's ... doesn't one of the newer TLD's also require them ? .biz or .info or something ?

.biz requires dedicated IPs. We use shared IPs so .biz's dont work.

[thecomputerpro]

I think that organization is always a good thing

Question I have. Most of us have ns and ns1 registered with our registrars with the 65.57.xxx.xxx IP's, do we need to make the change there to update IP's or will it update automatically? (hope so but doubt it) And if we do, when should we do it?

[mresell]

For those of us w/ svc domains on 65.* are we gonna have to update or change anything? NS I expect will need changing, but I hope there is no downtime for svc domain.

[digitalthoughts]

When will the migration start? How long before the name server range will be up and working?

[admin]

Originally Posted by mresell

For those of us w/ svc domains on 65.* are we gonna have to update or change anything? NS I expect will need changing, but I hope there is no downtime for svc domain.

We are not updating web servers yet just DNS, Mail and mysql. It will not mess with your "site" at all.

Once we have the switch done about the most reseller will have to do is switch the IPs from 65.57.231.100 and 65.57.231.120 to the new IPs nothing to do with there customers or any thing, its a simple registrar change.. This way the name servers are on IPs own and can go to any provider or network we want with them.. I don't like using Level(3)'s IP address space...

[Solamar]

oops, sorry, misread

We will let you know when to change the IPs with your registrar. Dont until we send out a notice, since we are having some difficulty with the NS and CP IPs.

pg.hsphere.cc is now 216.157.145.50
mail.hsphere.cc is now 216.157.145.20
mysql.hsphere.cc is now 216.157.145.40

They are still located on the ns.hsphere.cc machine (IP 65.57.231.100). Make sure if you are calling these services via IP that you use the new IPs now as once we move the machines you wont be hitting the right server.