Named in a private lab

Discussion in 'Server Operation' started by Dsmith, Sep 3, 2008.

  1. Dsmith

    Dsmith New Member

    I am creating a lab for familiarizing myself with a few protocols. My goal is to produce a server offering dhcp, dns, & http to a client (in this case the client is through a Dlink router). The physical architecture of the network is:

    comcast ]---->cable modem]---->Linksys router]---->192.168.1.0/24

    Form the LAN I have an interface (eth0) on my RH9 set as a dhcp client on the 192.168.1.0 network.

    My RH9 box is multi-homed. Eth1 is 172.22.146.0/16 and offers DHCP, DNS, and HTTP to clients on that side of the network. DHCP and HTTP is working great but I have hit the wall on the DNS.

    Currently my short term goal is to resolve the requests to the TwelxNet domain (172.22.146.0) to 172.22.146.1.

    My long term goal is to forward DNS requests through to the 192.168.1.0 network and then to comcast.

    Any ideas would be welcome.

    Cheers!
    Dale
     
  2. falko

    falko Super Moderator ISPConfig Developer

    You must forward the ports 53 TCP and UDP for DNS to work through a firewall.
     

Share This Page