#2872 DDNS - add server and realm commands for AAAA
Closed: Fixed 4 years ago by thalman. Opened 8 years ago by preichl.

Change fallback attempt from:

;sever is present only if option dyndns_server is set in sssd.conf 
server 192.168.122.20
;realm is used always in fallback message
realm IPA.WORK
update delete husker.human.bs. in A
update add husker.human.bs. 1200 in A 192.168.122.180
send
update delete husker.human.bs. in AAAA
update add husker.human.bs. 1200 in AAAA 2001:cdba::666
send

to:

;sever is present only if option dyndns_server is set in sssd.conf 
server 192.168.122.20
;realm is used always in fallback message
realm IPA.WORK
update delete husker.human.bs. in A
update add husker.human.bs. 1200 in A 192.168.122.180
send
;sever is present only if option dyndns_server is set in sssd.conf 
server 192.168.122.20
;realm is used always in fallback message
realm IPA.WORK
update delete husker.human.bs. in AAAA
update add husker.human.bs. 1200 in AAAA 2001:cdba::666
send

I also thought we were expected to only use the server option if the first update fails?

Yes, it's just for the fall back attempt.

server command is expected only if the first attempt fails and server option is set.
realm command is expected only if the first attempt fails.

If I understand Petr Spacek correctly 'realm' and 'server' commands would be used only for the first transacton - finished by send. Server would not remember 'realm' and 'server' commands for the next AAAA transaction.

Let me clarify this: server and realm commands affect nsupdate's behavior. The workaround which executes nsupdate binary again for each DNS update transaction forces us to start each transaction without hacks (explicit keyword usage) and add the keywords again in second attempt for each transaction.

... Or more specifically, keywords shold be used for each name separately.

I.e.

  • A RR type - attempt 1:

    update add name.example ... A ...
    send

  • A RR type - attempt 2:

    server 192.0.2.1
    realm EXAMPLE.COM
    update add name.example ... A ...
    send

  • AAAA RR type - attempt 1:

    update add name.example ... AAAA ...
    send

  • AAAA RR type - attempt 2:

    server 192.0.2.1
    realm EXAMPLE.COM
    update add name.example ... AAAA ...
    send

and so on for each name containing PTR recods.

Fields changed

patch: 0 => 1

Fields changed

owner: somebody => preichl
status: new => assigned

This should be merged into 1.14 if we can get review, not to stable branches unless we get a bug report.

1.15 is fine actually.

milestone: NEEDS_TRIAGE => SSSD 1.15 beta

Sorry wrong ticket and hence wrong milestone. This one has patch, so it should be 1.14.

milestone: SSSD 1.15 beta => SSSD 1.14 alpha

Fields changed

rhbz: => todo

I suspect this can be deferred.

milestone: SSSD 1.14 alpha => NEEDS_TRIAGE

Replying to [comment:11 jhrozek]:

This one has patch, so it should be 1.14.

Just curious: Why is it getting postponed if it has a patch?

Because the patch needs quite some work and the developer who submitted it is no longer around.

OK, let's not defer this but there is no time in the current milestone.

milestone: NEEDS_TRIAGE => SSSD 1.15 beta

Metadata Update from @preichl:
- Issue assigned to preichl
- Issue set to the milestone: SSSD Future releases (no date set yet)

7 years ago

Metadata Update from @thalman:
- Custom field design_review adjusted to on (was: 0)
- Custom field mark adjusted to on (was: 0)
- Custom field patch adjusted to on (was: 1)
- Custom field review adjusted to on (was: 0)
- Custom field sensitive adjusted to on (was: 0)
- Custom field testsupdated adjusted to on (was: 0)
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

4 years ago

SSSD is moving from Pagure to Github. This means that new issues and pull requests
will be accepted only in SSSD's github repository.

This issue has been cloned to Github and is available here:
- https://github.com/SSSD/sssd/issues/3913

If you want to receive further updates on the issue, please navigate to the github issue
and click on subscribe button.

Thank you for understanding. We apologize for all inconvenience.

Login to comment on this ticket.

Metadata