Designate fails to create zone on a target in different region when bind is used
Bug #1691416 reported by
sonu
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Designate |
Invalid
|
Undecided
|
Unassigned | ||
Bug Description
when we use nameserver of different region in pool configuration and when we create a zone designate fails to create zones on the targets of different region and goes into error state.
pools config: http://
worker-logs: http://
| summary: |
- Designate fails to create zone on a target in different region + Designate fails to create zone on a target in different region when + bind is used |
| description: | updated |
Revision history for this message
| Tim Simmons (timsim) wrote | #1 |
| Changed in designate: | |
| status: | New → Invalid |
To post a comment you must log in.
Connection refused via rndc isn't a Designate error, it's likely that there's some sort of network issue between Designate and the bind server in question. Maybe try debugging rndc locally on that machine.