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

Secondary DNS can't transfer zone info - firewall issue?

Discussion in 'Plesk for Linux - 8.x and Older' started by matthew@, Jan 13, 2006.

  1. matthew@

    matthew@ New Pleskian

    22
    73%
    Joined:
    Jan 13, 2006
    Messages:
    11
    Likes Received:
    0
    Just setting up domains on Plesk (FreeBSD) and trying to get a secondary DNS server working, without much luck - can anyone help?

    I think it's a firewall issue. Assume: ns.domain1.com is the primary DNS on this server, using IP 1.1.1.2. I'm setting up domain2.com on there on IP 1.1.1.1 and trying to use a secondary DNS for it, using secondary DNS server ns.second.com, 2.2.2.2. I have:

    * In Server > DNS > Common ACL, added 2.2.2.2

    * In Domains > domain2.com > DNS, added NS records:
    domain2.com > NS > ns.domain1.com
    domain2.com > NS > ns.second.com

    * In Modules > Firewall, added:
    Allow outgoing to 2.2.2.2 on 53tcp, 53udp
    (The built-in DNS rule allows incoming from all to 53?)

    * In /etc/named.conf, uncommented:
    query-source address * port 53 (although I'm not sure this was necessary)

    I'm pretty sure that my ns.domain1.com is all working fine, 'cos domain2.com is up and running. However, when I try to add it to the secondary DNS service:

    * Master DNS: 1.1.1.2
    * Domain name: domain2.com

    It gives me an error: 'ns.second.com can't read from primary server. hint: check firewall.'

    Am I missing something? (Likely) Any insights much appreciated.
     
  2. rank1st

    rank1st Guest

    0
     
    Check out ARTs secondary dns feature, it works great and may have some firewall configuration information in the setup as well.
     
  3. matthew@

    matthew@ New Pleskian

    22
    73%
    Joined:
    Jan 13, 2006
    Messages:
    11
    Likes Received:
    0
    Hi, thanks for the tip - I'm looking into this, it looks useful. Meantime my problem seems to have resolved itself of its own accord. Don't know why but I'm not complaining!
     
  4. nero0247

    nero0247 Guest

    0
     
    make sure the dns port is open to UDP and TCP requests
     
Loading...