New issue

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

cron: DNS servers doesn't get the new zones whenever there is something in fm_dns_track_reloads #66

Closed
ldperron opened this Issue Feb 6, 2014 · 4 comments

Comments

Projects
None yet
2 participants
@ldperron

ldperron commented Feb 6, 2014

I can't add new domain in a reliable manner. I don't know if this is directly related to the cron mode, but my DNS doesn't pick up the new domains names.

I started to pinpoint the issue with fm_dns_track_reloads, but I think that other flags may also have issue, like fm_dns_servers.server_update_config, fm_dns_servers.server_build_config, which I don't understand completly.

Thanks

@WillyXJ

This comment has been minimized.

Owner

WillyXJ commented Feb 6, 2014

The user process is supposed to be the following:

  1. Create the new domain
  2. Create the required records for the domain (i.e. SOA, NS, etc.)
  3. Go to the servers page and "Build Config" for the server(s) hosting the domain
  4. The servers get updated using the defined update method

On the backend, the process looks like the following:

  1. Add the domain to fm_dns_domains
  2. Add the user inputed domain records to fm_dns_records and fm_dns_soa
  3. If all required records exist, set fm_dns_servers.server_build_config = 'yes'
  4. User clicks "Build Config"
  5. For cron, this will
    a. Add a record to fm_dns_track_reloads with VALUES($domain_id, $server_serial_no, $soa_serial_no)
    b. Set fm_dns_servers.server_update_config = 'yes'
  6. The client requests $fm_host/buildconf.php which then pulls the server configs and domains set in step 5 above

You can run the following on your dns server that is updated via cron to see if there are any error messages as it could be a simple issue:

sudo php /usr/local/facileManager/fmDNS/dns.php cron debug

@WillyXJ WillyXJ added the fmDNS label Feb 6, 2014

@ldperron

This comment has been minimized.

ldperron commented Feb 7, 2014

It unfortunately doesn't works as expected. I will try the ssh method for now on a new server, and keep looking in the cron method when I have more time.

@WillyXJ

This comment has been minimized.

Owner

WillyXJ commented Feb 21, 2014

This is indeed not working properly. I had a chance to take a look and found some big bugs with the cron update method. This issue is targeted for v1.1.

@WillyXJ WillyXJ added this to the 1.1 release milestone Feb 21, 2014

@WillyXJ WillyXJ added the bug label Feb 21, 2014

WillyXJ pushed a commit that referenced this issue Feb 21, 2014

@WillyXJ

This comment has been minimized.

Owner

WillyXJ commented Feb 21, 2014

The code has been checked in for v1.1.

@WillyXJ WillyXJ closed this Feb 21, 2014

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment