Static IPs in Perfect Server ISPConfig 3 Ubuntu 12.04...

Discussion in 'Installation/Configuration' started by ifiokjr, Dec 17, 2012.

  1. ifiokjr

    ifiokjr New Member

    Hey

    I'm a nube when it come to linux but have recently taken a serious love to the whole system and mentality. So I'm taking advantage of AWS free trial to hone my skills over the coming years. And become a BOSS on the command line.

    For now though I'm still a complete NUBE!

    During installing ISP Config for Ubuntu using this awesome walk-through, I tentatively typed out the following text:

    Code:
    [FONT="Courier New"]# This file describes the network interfaces available on your system
    # and how to activate them. For more information, see interfaces(5).
    
    # The loopback network interface
    auto lo
    iface lo inet loopback
    
    # The primary network interface
    auto eth0
    iface eth0 inet static
            address 192.168.0.100
            netmask 255.255.255.0
            network 192.168.0.0
            broadcast 192.168.0.255
            gateway 192.168.0.1
            dns-nameservers 8.8.8.8 8.8.4.4
    [/FONT]
    into the following file.

    Code:
    /etc/network/interfaces
    
    Upon restarting I could no longer access the AWS server. I've now started up a new instance and am leaving out that particular step until I understand more.

    I was pretty sure something would go wrong. So before copying I did try to look around and understand what was going on.. but WOAH! Over my head explanations. So I figured, the best way to learn is to BREAK something..

    So to simplify:
    1. I have an elastic IP address (associated with this aws instance), does this go in here?
    2. Do I just make up an IP Address for dns-nameservers?
    3. Which IP addresses are for public access and which ones are internal?

    And even better, if anyone could explain to me what this file does, why it's important for there to be a static IP Address and whether I can just leave things as DHCP and hope for the best... :)

    This forum rocks! And linux is awesome!

    Peace
     
  2. falko

    falko Super Moderator ISPConfig Developer

    On AWS, it's better to leave that part out.

    The nameservers from the tutorial are valid ones (Google nameservers), so you could use these or any other public nameservers.

    http://en.wikipedia.org/wiki/Private_network
     
  3. ifiokjr

    ifiokjr New Member

    My conclusions:
    • On AWS I can ignore setting up a static IP.
      [*]And public nameservers are fine.

    Thanks for this. I was able to set everything up successfully.. and then break it in wonderful ways.

    May the learning continue.
     

Share This Page