Ticket #2095 (closed defect: fixed)

Opened 2 years ago

Last modified 18 months ago

The serial from alias domains never gets updated, part II

Reported by: aseques Owned by: nuxwin
Priority: critical Milestone: ispCP ω 1.0.7
Component: Backend (Engine) Version: ispCP ω 1.0.3
Severity: Medium Keywords:
Cc:

Description

This is a follow-up from #2040, wich I can't reopen, and with a different testcase:

1.- Create a new user with privilege to edit dns examplea.com

2.- As a resseller, create a domain Alias exampleb.com and assign it to examplea.com

3.- Switch to the user examplea.com and go to manage domains. You should see something like this for exampleb.com zone: 2009120900 (YYYYMMDD00)

4.- Add the subdomain a.exampleb.com, the serial should be increased by one (2009120901)

5.- Add the A entry test.exampleb.com pointing to 127.0.0.1, the serial should be 2009120902, but it still is 2009120901

It seems to me that the serial increases as expected when creating subdomains, but that it doesn't when we are creating DNS entries.

Change History

comment:1 Changed 2 years ago by aseques

Also, I can see that the serial is decreased after changing the dns (for example when deleting a subdomain).

The serial numbers should never be decreased, if they are not increased, the zones won't propagate to the slave dns servers.

comment:2 Changed 2 years ago by benedikt

  • Milestone changed from ispCP ω 1.0.3 to ispCP ω 1.1.0

code freeze.

comment:3 Changed 2 years ago by aseques

Shouldn't this be treated as a bug in 1.0.3? It is a new feature that is not properly working. It can be quite annoying if you are creating by yourselve the dns entries, and it's difficult to debug dns problems like that (and really difficult if you are not the admin of the dns server) For example in case I want to be able to create custom mx servers and the www entry, I have to update the serial by hand afterwards.

comment:4 Changed 2 years ago by benedikt

"Marked Manual DNS as EXPERIMENTAL. Please use for test purposes only. It can not guaranteed that the DNS feature is working as expected. Please communicate it this way!"

Because of this, we will fix it later. Actually external DNS is not working as expected… compare #2086.

comment:5 Changed 2 years ago by nuxwin

  • Milestone changed from ispCP ω 1.1.0 to ispCP ω 1.0.4

comment:6 Changed 2 years ago by nuxwin

  • Owner set to nuxwin
  • Status changed from new to assigned

comment:7 Changed 2 years ago by nuxwin

  • Priority changed from normal to critical
  • Component changed from Frontend (GUI) to Backend (Engine)
  • Severity changed from Don't know to Medium

Confirmed ; I'll fix now

comment:8 Changed 2 years ago by nuxwin

  • Milestone changed from ispCP ω 1.0.4 to ispCP ω 1.0.5

I've rewritten completly this feature, and I've not finish the internal tests, so, I move this ticket to 1.0.5.

Sorry for the delay.

comment:9 Changed 2 years ago by nuxwin

  • Milestone changed from ispCP ω 1.0.5 to ispCP ω 1.0.6

comment:10 Changed 18 months ago by nuxwin

  • Status changed from assigned to closed
  • Resolution set to fixed

See r3159 (only issue related to this ticket was fixed)

Note: See TracTickets for help on using tickets.