The Community Forums

Interact with an entire community of cPanel & WHM users!
  1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

Nearly there... Need guidance on system domain zone

Discussion in 'E-mail Discussions' started by stardotstar, Sep 18, 2009.

  1. stardotstar

    stardotstar Well-Known Member

    Joined:
    Sep 14, 2009
    Messages:
    68
    Likes Received:
    0
    Trophy Points:
    6
    Hi all,

    I am snowed with the relocation and a mostly complete migration of my shared hosting from my original server "Helios" to the new whm/cp box "Jupiter"

    I have migrated the ns1 and ns2 IPs of my nameservers which were A records on Helios to Jupiter and therefore
    ns1.sourcepoint.com.au and
    ns2.sourcepoint.com.au are now authoritative for all the domains I host from the Jupiter server using whm...

    So far so good.

    I associated a free IP from Helio's subnet to eth0 on Jupiter so ns2 could run on a separate network (even if same host is single point of failure - ok for now)

    therefore where (on Helios)
    ns1.sourcepoint.com.au was 202.130.34.115 and
    ns2.sourcepoint.com.au was 202.130.34.116

    NOW on Jupiter is
    ns1.sourcepoint.com.au at 202.130.33.50
    ns2.sourcepoint.com.au at 202.130.34.117

    So far so good.

    All the sites i have copied over, even ones with databases and gallery/forum constructs are working and being served by whm/cpanel Jupiter.

    My problem is this:

    since the whm host Jupiter is in the same domain as the old server Helios and they both share the same fully qualified domain suffix: sourcepoint.com.au

    I found that I had to add the domain as a system owned domain:
    Code:
    root@jupiter [/etc]# cat /var/named/sourcepoint.com.au.db 
    ; cPanel first:11.24.5-CURRENT_38506 latest:11.24.5-NIGHTLY_38436 Cpanel::ZoneFile::VERSION:1.2 mtime:1253315633 hostname:jupiter.sourcepoint.com.au
    ; Zone file for sourcepoint.com.au
    $TTL 14400
    sourcepoint.com.au.	86400	IN	SOA	ns1.sourcepoint.com.au.	stardotstar.sourcepoint.com.au.	(
    						2009091802 ;Serial Number
    						86400 ;refresh
    						7200 ;retry
    						604800 ;expire
    						86400 ;minimum
    	)
    sourcepoint.com.au.	86400	IN	NS	ns1.sourcepoint.com.au.
    sourcepoint.com.au.	86400	IN	NS	ns2.sourcepoint.com.au.
    ns1	14400	IN	A	202.130.33.50
    ns2	14400	IN	A	202.130.34.117
    sourcepoint.com.au.	14400	IN	A	202.130.34.115
    localhost	14400	IN	A	127.0.0.1
    sourcepoint.com.au.	14400	IN	MX	0	sourcepoint.com.au.
    mail	14400	IN	CNAME	sourcepoint.com.au.
    www	14400	IN	CNAME	sourcepoint.com.au.
    ftp	14400	IN	CNAME	sourcepoint.com.au.
    sourcepoint.com.au.	14400	IN	TXT	�v=spf1 a mx -all�
    jupiter	14400	IN	A	202.130.33.50
    ns1	14400	IN	A	202.130.33.50
    ns2	14400	IN	A	202.130.34.117
    root@jupiter [/etc]# 
    
    Because if I created a whm/cpanel "account" the records for the redirection of various web pages would not necessarily go back to my Helios server

    Sorry this seems hard to explain but what I have now is my whole sourcepoint.com.au mail, database and so on running on Helios (202.130.34.115) and these sites are taking orders because of the way that the above zone file has been created. If I were to add sourcepoint as an account on Jupiter in whm I would have to do some jiggery pokery with the a records and so on because mail and ftp associated with the "account" sourcepoint would not be representative of the real server answering to helios.sourcepoint.com.au - ie proftpd, sshd, the apache server for RoundCube Webmail :: Welcome to RoundCube Webmail and so forth.

    If this makes sense could I please ask for some feedback on how one would handle this - eventually migrating the mail and "sourcepoint" infrastructure from Helios leaving only a couple of other database intensive sites on that box which can be served in the name servers by creating system zones that redirect.

    archeli.com.au and arcplane.com.au are the most critical of these.

    Again I am sorry I seem to be so close to a working setup (afterall my customers are all working!) but still some way from getting my head around the way that I can administer two servers until a migration to a fully mangaged whm service can be completed.

    Will
     
  2. serversignature

    serversignature Well-Known Member

    Joined:
    Nov 26, 2007
    Messages:
    107
    Likes Received:
    0
    Trophy Points:
    16
    Location:
    Bangalore
    If i got it right ...

    You already have the DNS pointing to Jupiter.

    $ dig @202.130.34.117 sourcepoint.com.au and dig @202.130.33.50 sourcepoint.com.au shows sourcepoint.com.au pointing to 202.130.34.115, you need to make changes in the DNS at Jupiter to make sourcepoint.com.au point to the new server IP 202.130.33.50.

    Current entry at Jupiter.
    sourcepoint.com.au. 14400 IN A 202.130.34.115

    202.130.34.115 - Helios
     
  3. stardotstar

    stardotstar Well-Known Member

    Joined:
    Sep 14, 2009
    Messages:
    68
    Likes Received:
    0
    Trophy Points:
    6
    Thank you.

    The web tree for sourcepoint is correctly pointing to the helios server...

    I think things are starting to come together.
     
Loading...

Share This Page