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

DNS recursion bigfix doesn't fix anything (and 'unfixes' fixed configs)

Discussion in 'Plesk for Linux - 8.x and Older' started by breun, Dec 1, 2006.

  1. breun

    breun Golden Pleskian

    29
     
    Joined:
    Jun 28, 2005
    Messages:
    1,647
    Likes Received:
    0
    The Plesk 8.1.0 release notes say:

    While this is a good thing, I believe the bugfix is pretty buggy, because the upgrade to 8.1.0 put the following in my /etc/named.conf:

    Code:
    allow-recursion {
                    any;
            };
    Testing with http://www.kloth.net/services/nslookup.php for instance shows BIND allows recursion. I changed any to 127.0.0.1 and things are fine after restarting named.

    Are other people seeing this too? I've done two upgrades to 8.1.0 so far and both boxes had allow-recursion set to any afterwards. Even if it was set to 127.0.0.1 before starting the upgrade, so the 'fix' actually 'unfixed' my configuration!
     
  2. nb__

    nb__ Guest

    0
     
    My Fedora Core 4's named have a correct settings according to release notes. Your OS, dude?
     
  3. breun

    breun Golden Pleskian

    29
     
    Joined:
    Jun 28, 2005
    Messages:
    1,647
    Likes Received:
    0
    CentOS 4 on the first box, Fedora Core 3 on the second. Both ended up with 'allow-recursion { any };' in /etc/named.conf after the upgrade. What is the exact allow-recursion statement that the upgrade put in your config?
     
  4. ItMan

    ItMan Guest

    0
     
    For 8.0.1 Add all to named.conf


    You can fix it manually:

    named.conf.include.plesk-options
    Code:
            allow-recursion {
                    localnets;
            };
    
     
  5. breun

    breun Golden Pleskian

    29
     
    Joined:
    Jun 28, 2005
    Messages:
    1,647
    Likes Received:
    0
    I understand I can fix this manually, but I shouldn't have to. And the update to Plesk 8.1.0 should definitely not change my config to allow recursion to any host!
     
  6. breun

    breun Golden Pleskian

    29
     
    Joined:
    Jun 28, 2005
    Messages:
    1,647
    Likes Received:
    0
  7. ItMan

    ItMan Guest

    0
     
    It is not critical, just worse that:

    Code:
    listen-on       {127.0.0.1;}
     
  8. breun

    breun Golden Pleskian

    29
     
    Joined:
    Jun 28, 2005
    Messages:
    1,647
    Likes Received:
    0
    What do you mean exactly? I don't have listen-on { 127.0.0.1; } in my named.conf.
     
  9. ItMan

    ItMan Guest

    0
     
    After Update i have:
    * recursion fixed
    * but fixed listen-on, that bind didn't work at all.

    sorry for my bad English =(
     
Loading...