1. Please take a little time for this simple survey! Thank you for participating!
    Dismiss Notice
  2. Dear Pleskians, please read this carefully! New attachments and other rules Thank you!
    Dismiss Notice
  3. Dear Pleskians, I really hope that you will share your opinion in this Special topic for chatter about Plesk in the Clouds. Thank you!
    Dismiss Notice

Plesk DNS behind firewall and switch

Discussion in 'Plesk for Linux - 8.x and Older' started by bluefossil, Oct 4, 2005.

  1. bluefossil

    bluefossil Guest

    Hi all,

    I have just set up Plesk 7.5.4 on my RHEL4 box, which is sitting behind a Cisco PIX506E firewall and Cisco Catalyst 2950 switch with NAT. I am now trying to set up a new domain, let's call it example.com.

    I have registered ns1.example.com (x.x.x.34) and ns2.example.com (x.x.x.35) as the nameserver domains. In Plesk, I manually added the public IP address x.x.x.39 and assign this IP to the new domain in order for Plesk to create the DNS entries in public IPs instead of private.

    This is an example of the DNS setup for this domain:
    example.com.	NS	ns1.example.com.	
    example.com.	NS	ns2.example.com.	
    example.com.	A	x.x.x.39	
    webmail.example.com.	A	x.x.x.39	
    pop.example.com.	A	x.x.x.39	
    smtp.example.com.	A	x.x.x.39	
    ns1.example.com.	A	x.x.x.34	
    ns2.example.com.	A	x.x.x.35	
    ftp.example.com.	CNAME	example.com.	
    www.example.com.	CNAME	example.com.
    example.com.	MX (10)	pop.example.com.	
    x.x.x.39 / 24	PTR	example.com.
    I also manually added A records for ns1.example.com and ns2.example.com as you can see above.

    With that all set up, I tried to surf to www.example.com, but was greet by the "Default PLESK page", instead of the placeholder page for example.com that I was expecting.

    Have I made some mistakes in the setup that I missed out? Is there any impact in adding public IPs into the mix of the private IPs in the Plesk interface?
  2. sieb@

    sieb@ Guest

    Are you using a different IP for the internal network from the external network?

    If so, DNS for a domain needs to be set to the external IP, but the physical hosting needs to be set to the internal network IP so Apache knows what to reply to. Since NAT will change requests into the internal network IP, Apache needs to know to respond to the internal IP, it wont get requests using the external IP. I have to do this for my servers in a DMZ.
  3. bluefossil

    bluefossil Guest


    Great! I finally got it to work, but I thought I should post my solution here in case someone stumbles upon this in future seeking an answer.

    I took your advice, and went ahead to manually edit the httpd.include file for that domain from public IP to private IP. And sure enough, the site got to working instantly.

    Now, the problem was that Plesk writes both the DNS and the Apache files, but these two files need public IP and private IP respectively. Basically, it means it's impossible to do it through Plesk without manually editing one of the files...

    Until I found out about DNS Rewrite in my Cisco firewall. That feature is able to send the correct public IP address to the outside from the inside DNS server. So I enabled it, and configured Plesk to only use the private IPs when writing the DNS and Apache files, and voila, it now works smoothly.

    Erm, I hope that doesn't add to the confusion. Hope it helps anyone with the similar kind of setup as mine.


  4. sieb@

    sieb@ Guest

    Actually, you took the hard path :p. In PSA, you need to bind both the internal and external IP to the server so they are in the IP Pool. Then, when you setup websites, give the account both IPs from the pool. When it asks for the IP of the physical hosting setup, give it the internal IP. This will cause it to default the DNS to the internal IP as well. To fix that, just go into the sites DNS settings and default it to the external IP. No need to mess with the configs because as you said, PSA rewrites those.

    Following my instructions sets Bind to send out dns requests/updates using the correct external IP, and sets Apache to listen for requests coming to the internal IP since the router transforms packets as it passes them through NAT.

    *NOTE* that I have found on some RH installs, when you bind another IP to the network adapter in PSA, it will create a sub interface config file in /etc/sysconfig/scripts IIRC. So there will be a en0:00 and en0:01 or thereabouts. Delete the subinterface config and restart the network service. Otherwise this setup won't work. We don't want the network service to use sub-interfaces since this is still technically interfacing with one network subnet, you only need PSA to tell Apache to listen to a different IP request coming in on that network interface.

    I should probably write a how-to about this when I get a chance. :D