Trouble with subdomains

Discussion in 'General' started by Been Told, Jan 17, 2009.

  1. Been Told

    Been Told Member

    Hi!
    I have a problem with subdomains. I create one using the co-domains page and tick the "create dns" option and enter the desired folder. But when I try to access the subdomain in my browser I get a shared IP page.
    What could I be doing wrong?
    The specs are in my signature, the root server.
     
    Last edited: Jan 17, 2009
  2. till

    till Super Moderator Staff Member ISPConfig Developer

    1) Is the local DNS Server the authoritive mail server for the domain?
    2) Changes in dns like adding a subdomain may take up to 48 hours to become active.
     
  3. Been Told

    Been Told Member

    Yup.
    I've flushed the DNS cache on my computer and it still didn't change.
     
  4. falko

    falko Super Moderator Howtoforge Staff

    Did you tell your client PC to use your ISPConfig server as the primary DNS server? The DNS servers of your ISP probably use a cache as well...
     
  5. Been Told

    Been Told Member

    Can you explain that a little more? I'm not sure I know what you mean exactly.
     
  6. grungy

    grungy Member

    As I can understand subdomains in ispconfig3 do not have ther own document roots, but they share the document root of the main site, which does not make sense. I would like to be able to create a subdomain which will have it's own document root, vhost etc etc....
     
  7. till

    till Super Moderator Staff Member ISPConfig Developer

    This does not make sense for you if you do not understand how the system works but it makes sense for others.

    Then create a new site for the subdomain. So simple ;)

    Update: @grungy, you realised that Been Told is talking about a different software?
     
    Last edited: Jan 18, 2009
  8. grungy

    grungy Member

    oh :) just seen his signature....lack of sleep :)
     
  9. Been Told

    Been Told Member

    I've just thought, it's just as easy creating the subdomain via htaccess.
    Till, do you know what directive I need to put into the the site's directive box to allow the use of htaccess files? AllowOverride or something like that...

    Edit: I've put in the following directive:
    Code:
    <Directory "/var/www/web9/web">
    Options FollowSymLinks
    AllowOverride All
    </Directory>
    Then I created a htaccess file with this content:
    Code:
    RewriteEngine On
    RewriteCond %{HTTP_HOST} en.domain.tld $ [NC]
        RewriteCond %{REQUEST_URI} !/en_dom/
        RewriteRule ^(.*)$ en_dom/ [L]
    When I go to en.domain.tld I still get a Shared IP page.
     
    Last edited: Jan 18, 2009
  10. Been Told

    Been Told Member

    Hm, this seems to be a bigger problem.
    I have just tried adding a different domain and did everything the usual way. Result: Shared IP page.
    And the best thing: I have no fecking clue as to what might be causing this.
     
  11. falko

    falko Super Moderator Howtoforge Staff

    Does your subdomain point to the right IP? You can check that with
    Code:
    dig subdomain.yourdomain.com
    What's in Vhosts_ispconfig.conf, and what's the output of
    Code:
    ifconfig
    ?
     
  12. Been Told

    Been Told Member

    The output seems fine, it shows the A record with the correct IP.
    However in /etc/apache2/Vhosts_ispconfig.conf there is no mention of the subdomain.
    Also, as I mentioned before, I have added a new domain in ISPconfig. When I try to view it in my browser I get the IP shared page and it also does NOT appear in /etc/apache2/Vhosts_ispconfig.conf
    Code:
    eth0      Link encap:Ethernet  HWaddr XXXXXXXXXXXXXXX
              inet addr:XXXXXXXXXXXXXXX  Bcast:XXXXXXXXXXXXXXX  Mask:XXXXXXXXXXXXXXX
              inet6 addr: XXXXXXXXXXXXXXX Scope:Link
              UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
              RX packets:18787570 errors:0 dropped:0 overruns:0 frame:0
              TX packets:24910971 errors:0 dropped:0 overruns:0 carrier:0
              collisions:0 txqueuelen:1000
              RX bytes:4227855102 (3.9 GiB)  TX bytes:28330200893 (26.3 GiB)
              Interrupt:217 Base address:0xc000
    
    lo        Link encap:Local Loopback
              inet addr:127.0.0.1  Mask:255.0.0.0
              inet6 addr: ::1/128 Scope:Host
              UP LOOPBACK RUNNING  MTU:16436  Metric:1
              RX packets:1083536 errors:0 dropped:0 overruns:0 frame:0
              TX packets:1083536 errors:0 dropped:0 overruns:0 carrier:0
              collisions:0 txqueuelen:0
              RX bytes:223341433 (212.9 MiB)  TX bytes:223341433 (212.9 MiB)
    
     
  13. till

    till Super Moderator Staff Member ISPConfig Developer

  14. Been Told

    Been Told Member

    I have edited Vhosts_ispconfig.conf and added information for the domain2.tld that was already added in ispconfig. Now when I visit domain2.tld with my browser, I get the expected website.

    So it seems ispconfig is simply not writing to the Vhosts_ispconfig.conf file. Or am I mistaken?

    Edit:
    Cool thanks. :)
     
    Last edited: Jan 19, 2009
  15. till

    till Super Moderator Staff Member ISPConfig Developer

    Please follow the instructions that are described in the Link that I posted above!

    and never edit the file Vhosts_ispconfig.conf manually, ISPConfig will remove any changes automatically.
     
  16. Been Told

    Been Told Member

    Okay I've followed the steps. There was a wrong Apache Directive on one of the websites stored on the server. So I corrected that change. Then I deleted the de.domain.tld and domain2.tld from ISPconfig. Both the sites and the DNS records.
    Then suddenly the server became unreachable. All domains stopped working.
    Then I tried to restart apache and it just says:
    Forcing reload of web server (apache2)...httpd (pid 12915?) not running
    failed!

    So I tried to just start the apache2 and it just says "failed".
     
  17. Been Told

    Been Told Member

    Okay the error log was moaning that I had deleted two of the webX folders (I had done that the normal way as described above). But I must have re-uploaded the wrong Vhosts_ispconfig.conf file. Now I've created the folders again. I just need to figure out how to stop apache2 looking for them when starting up.
     
  18. falko

    falko Super Moderator Howtoforge Staff

    I'd modify one of the web sites in ISPConfig so that Vhosts_ispconfig.conf gets rewritten with the current configuration. It should reference old folders anymore afterwards.
     
  19. Been Told

    Been Told Member

    Ah cool, thanks for the tip!
     

Share This Page