Synchronization stopped working PowerDNS to Bind DNS server

Discussion in 'Troubleshooting' started by Naymen, May 25, 2017.

  1. Naymen

    Naymen Kilo Poster

    Messages:
    13
    Hello!
    The synchronization of PowerDNS and the DDN of the Bind server ceased to work.
    Previously, files with zones and configuration for pointing to the zone file was created in /var/named/named.zones
    And in the / var / named /
    Now nothing is created and synchronization is not working.

    OBAS-4.5.7-43
    ====

    Перестало работать синхронизация PowerDNS и днс сервера Bind.
    Раньше файлы с зонами и настройка на указание на файл зоны создавалась в /var/named/named.zones
    и в папке /var/named/
    Теперь ничего не создается и не работает синхронизация.

    OBAS-4.5.7-43

    ls -la /var/named/ekstrahovanie.ru.zone
    ls: невозможно получить доступ к /var/named/ekstrahovanie.ru.zone: Нет такого файла или каталога
     
  2. Naymen

    Naymen Kilo Poster

    Messages:
    13
    in the file "/etc/powerdns/pdns.conf." All OBAS-managed name servers must be listed in the parameter allow-axfr-ips, or this parameter may even be commented out (which is not recommended for the sake of security).

    allow-axfr-ips=185.173.178.71 185.173.178.2


    #dig axfr ekstrahovanie.ru @185.173.178.71

    ; <<>> DiG 9.8.2rc1-RedHat-9.8.2-0.30.rc1.el6 <<>> axfr ekstrahovanie.ru @185.173.178.71
    ;; global options: +cmd
    ; Transfer failed.

    KB NO WORK: https://kb.odin.com/en/8221

    LOG:
    # cat /var/log/messages | grep ekstrahovanie.ru

    May 25 20:34:10 pbas pdns[5442]: Queued notification of domain 'ekstrahovanie.ru' to 185.173.178.2:53
    May 25 20:34:11 pbas pdns[5442]: IXFR of domain 'ekstrahovanie.ru' initiated by 185.173.178.2 with serial 2017052500
    May 25 20:34:11 pbas pdns[5442]: AXFR of domain 'ekstrahovanie.ru' allowed: client IP 185.173.178.2 is in allow-axfr-ips
     
  3. Naymen

    Naymen Kilo Poster

    Messages:
    13
    Ошибка была в том, что домене не было указано остальных NS записей
    Добавил в шаблоны DNS записи ns серверов и синхронизация заработала.

    4_016.png 8_022.png
     
  4. SouthO

    SouthO Kilo Poster

    Messages:
    10
    I'm noticing a problem since updating also it seems. My customers on plesk are making changes to their zones in the plesk cp which is updating OBAS. But, OBAS is not in sync with plesk zone. It seems to add records but doesn't remove any when synchronizing suppliers. Thus, when my primary nameserver attemps to transfers the new zone changes it fails. For example,

    In OBAS no error during transfer.
    Aug 22 20:05:46 prov1 pdns[752]: AXFR of domain 'lovesoutho.com' initiated by 10.11.12.148
    Aug 22 20:05:46 prov1 pdns[752]: AXFR of domain 'lovesoutho.com' allowed: client IP 10.11.12.148 is in allow-axfr-ips
    Aug 22 20:05:46 prov1 pdns[752]: AXFR of domain 'lovesoutho.com' to 10.11.12.148 finished

    In BIND transfer fails.
    Aug 22 20:05:46 dns1 named[513]: zone lovesoutho.com/IN/pbas_resolver: Transfer started.
    Aug 22 20:05:46 dns1 named[513]: transfer of 'lovesoutho.com/IN' from 10.11.12.136#53: connected using 10.11.12.148#35110
    Aug 22 20:05:46 dns1 named[513]: transfer of 'lovesoutho.com/IN' from 10.11.12.136#53: failed while receiving responses: CNAME and other data
    Aug 22 20:05:46 dns1 named[513]: transfer of 'lovesoutho.com/IN' from 10.11.12.136#53: end of transfer
     
  5. dkolvakh

    dkolvakh Odin Team

    Messages:
    348
    Please create request in Odin Support about this issue.
     

Share This Page