Subdomain and go daddy help

Discussion in 'Installation/Configuration' started by djmidknight, Apr 5, 2010.

  1. djmidknight

    djmidknight New Member

    I am trying to setup a subdomain on my personal server but I am having issues first off the dns which I thought was working apparently was not and was allowing only local lan clients to access the site. I did check the router and the port for dns was open but still not sure why it did not work other than I am sure something I did was not the right thing.
    On to the main problem I have my website and using godaddys dns servers it works fine I can access it no problems but I cannot figure out how to get a subdomain to work.

    I've read several tutorials but they are all 3-6 years old and the screen shots although nothing now like the interface in godaddy anymore were simple enough to follow but did not work.

    so the layout right now is :

    1: website visable using godaddy dns servers
    2: subdomain setup steps in isp config to use with outside dns?
    3: what method to use in ispconfig
    a: create codomain and hack the config file to not change name
    b: create new site as

    4: setup what in godaddy?
    a: add subdomain - forward to what?
    b: add A Cname? if so what?
    5: not sure just what I am missing maybe more or less steps

    sorry I am new to the ispconfig and have tried to follow the tutorials but alas I have been stonewalled on them

    thanks for any help
  2. falko

    falko Super Moderator ISPConfig Developer

    Please create a Co-Domain in ISPConfig and then create an A record for that Co-Domain in the GoDaddy interface.
  3. djmidknight

    djmidknight New Member

    sorry still new to this what should I point the A record to?
    I have it pointed to the same IP as my main domain but still doesnt work Ill check my ispconfig and see but I am still trying to figure out settings overasll.

    Last edited: Apr 7, 2010
  4. falko

    falko Super Moderator ISPConfig Developer

    That should work, but it can take up to 72 hours until DNS changes propagate.

Share This Page