Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
While migrating from the BIND backend to the gsqlite3 backend, the IP addresses of the masters for slave zones are not added to the database's "masters" column in the "domains" table.
zone "powerdns.space" in { type slave; file "/var/lib/powerdns/zones/powerdns.space.zone"; masters { 188.166.104.87; 2a03:b0c0:2:d0::4af:b001; }; };
pdnsutil b2b-migrate bind gsqlite3
$ sqlite3 -column -header /var/lib/powerdns/pdns-public.sqlite3 "select * from domains where name='powerdns.space'" id name master last_check type notified_serial account ---------- -------------- ---------- ---------- ---------- --------------- ---------- 7 powerdns.space SLAVE
That the master IP addresses show up in the table.
That the addresses did not show up.
The text was updated successfully, but these errors were encountered:
a222f04
No branches or pull requests
Short description
While migrating from the BIND backend to the gsqlite3 backend, the IP addresses of the masters for slave zones are not added to the database's "masters" column in the "domains" table.
Environment
Steps to reproduce
pdnsutil b2b-migrate bind gsqlite3
(after configging both backends in pdns.conf)Expected behaviour
That the master IP addresses show up in the table.
Actual behaviour
That the addresses did not show up.
The text was updated successfully, but these errors were encountered: