Two hosts, one VPS server

Discussion in 'Apache' started by aidso, Apr 25, 2012.

  1. #1
    Hello guys, first time on the forum and hopefully you can help me.

    I have a VPS running Ubuntu 11.
    On it I have two websites: one is pure HTML and the other is a WordPress site. As far as I was aware, everything was setup correctly but some people are reporting strange results.

    MyWebsite1 - Pure Html
    YourWebsite2 - WordPress

    Some people are reporting that when they access "YourWebsite2" they are getting the "MyWebsite1" being returned. I am not getting this result on any pc that I try. Is there something in my settings that is prioritising the site they are seeing or is this down to ISPs? "YourWebsite2" only went Live on Saturday and is reached via a DNS Host at 123-reg.co.uk. It used to point to a SiteFusion site, but now it points to my Wordpress site instead. It did take close to 40 hours for people to see the new site and I thought all was well.

    My question is why is "MyWebsite1" being returned to users, when it is not being called??

    Here are some of my files:

    /etc/apache2/conf.d/virtual.conf
    NameVirtualHost *.80


    /etc/apache2/sites-enabled/MyWebsite1
    <VirtualHost *.80>
    ServerName www.MyWebsite1.com
    ServerAlias MyWebsite1.com
    DocumentRoot /var/www/MyWebsite1

    Options -Indexes
    </VirtualHost>

    /etc/apache2/sites-enabled/YourWebsite2
    <VirtualHost *.80>
    ServerName www.YourWebsite2.com
    ServerAlias YourWebsite2.com
    DocumentRoot /var/www/YourWebsite2

    Options -Indexes
    </VirtualHost>


    ----
    There is no correlation between the two sites other than being stored on the same VPS server and therefore having the same IP address: for example, they don't call each other.
    Is there something wrong with my setup or does everything appear fine?

    Thank you,
    A.
     
    aidso, Apr 25, 2012 IP
  2. djacobs

    djacobs Well-Known Member

    Messages:
    238
    Likes Received:
    6
    Best Answers:
    0
    Trophy Points:
    140
    #2
    If your DNS is setup properly and considering it just went live Saturday it probably hasn't propagated fully. Some ISP cache updates faster than others
     
    djacobs, Apr 25, 2012 IP
  3. aidso

    aidso Peon

    Messages:
    4
    Likes Received:
    0
    Best Answers:
    0
    Trophy Points:
    0
    #3
    Thanks for the quick reply.

    Do you think it should take that long? That's nearly 4 days.
    The frustrating thing is "Website1" is a business and while it doesn't directly compete with Website2, I think the owners are biting their lip before they start complaining to me as it looks like I'm doing a local redirect:(.
     
    aidso, Apr 25, 2012 IP
  4. djacobs

    djacobs Well-Known Member

    Messages:
    238
    Likes Received:
    6
    Best Answers:
    0
    Trophy Points:
    140
    #4
    PM me your sites.

    You can also look through a proxy
    anonymouse.org/cgi-bin/anon-www.cgi/http://domain.com
     
    djacobs, Apr 25, 2012 IP
  5. djacobs

    djacobs Well-Known Member

    Messages:
    238
    Likes Received:
    6
    Best Answers:
    0
    Trophy Points:
    140
    #5
    The sites you PM'd me work fine.
    DNS propagation can take up to 72hours NORMALLY
    But it depends on several factors.
    Your TTL settings
    The ISP of the person trying to visit your site (biggest issue), some ISP's set long minumum TTL settings.

    Give it another day or two. But I see nothing wrong with your Apache config, and the sites work fine where Im from
     
    djacobs, Apr 25, 2012 IP
  6. aidso

    aidso Peon

    Messages:
    4
    Likes Received:
    0
    Best Answers:
    0
    Trophy Points:
    0
    #6
    OK thanks.
    When I was migrating the sites I was fannying about with Apache and hadn't taken into consideration the DNS Propagation and was wondering why things were not updating.
    So, good to know my Apache files are looking good.

    A.
     
    aidso, Apr 25, 2012 IP
  7. PK-Host

    PK-Host Guest

    Messages:
    109
    Likes Received:
    3
    Best Answers:
    1
    Trophy Points:
    0
    #7
    I would recommend when you next plan on changing your DNS 24 hours + before you plan on changing your DNS set the ttl to around 1800 or 3600 this will ensure your DNS will be updated quicker, although around 24 hours after you have updated your dns ensure you set it back to what the ttl to what it was originally.
     
    PK-Host, Apr 25, 2012 IP
  8. aidso

    aidso Peon

    Messages:
    4
    Likes Received:
    0
    Best Answers:
    0
    Trophy Points:
    0
    #8
    I don't see how to do this.
    I have the Domain Name purchased with 123-reg.co.uk and the DNS Settings set to point to my VPS(Type A). There is no field to change the TTL beside this configuration value.
    Would I also be right in saying that although there is a TTL value with the domain company, ISPs have their own TTL?
     
    aidso, Apr 25, 2012 IP