ddns-update-style interim doesn't work with AAAA-records

Bug #56724 reported by Nafallo Bjälevik
6
Affects Status Importance Assigned to Milestone
dhcp3 (Ubuntu)
Expired
Medium
Unassigned

Bug Description

 Hi!

When I have IPv6 AAAA-records in my zone-file dhcpd can't add the A-record cause the name is already in use. This makes backuppc break, since that doesn't look up IPv6-records (see bug #54918). Maybe we could fix dhcpd so that it actually can add A-records even when an AAAA-record exists for that host?

Tags: ipv6
Revision history for this message
Nafallo Bjälevik (nafallo) wrote :

Should we forward this one upstream? :-)

Revision history for this message
Martin Pitt (pitti) wrote :

> Should we forward this one upstream? :-)

Yes, please.

Revision history for this message
will_in_wi (will-in-wi) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering is this still an issue for you? Can you try with latest Ubuntu release? Thanks in advance.

Revision history for this message
Nafallo Bjälevik (nafallo) wrote :

To be fair. I can't remember what happened with this one. Assuming I've reported it upstream somewhere...

Revision history for this message
RJ Clay (rjclay) wrote :

Is this still an issue for you? Have you tried with the most recent Ubuntu release?

Changed in dhcp3:
status: New → Incomplete
Revision history for this message
RJ Clay (rjclay) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

Changed in dhcp3:
status: Incomplete → Invalid
Revision history for this message
Nafallo Bjälevik (nafallo) wrote :

I haven't an environment to try this at the moment. However I haven't seen a change in any of the affected packages to make me assume this will have been fixed. I'll leave this open until we have evidence to the contrary, and I suggest that it will stay open until evidence exist that this have been fixed. Thanks.

Changed in dhcp3:
importance: Undecided → Medium
status: Invalid → Incomplete
Revision history for this message
Dimitrios Symeonidis (azimout) wrote :

setting back to new...

Changed in dhcp3:
status: Incomplete → New
Chuck Short (zulcss)
Changed in dhcp3 (Ubuntu):
status: New → Triaged
Revision history for this message
Thierry Carrez (ttx) wrote :

Are we still experiencing this in Lucid/Maverick ?

Changed in dhcp3 (Ubuntu):
status: Triaged → Incomplete
Revision history for this message
rusivi2 (rusivi2-deactivatedaccount) wrote :

We'd like to figure out what's causing this bug for you, but we haven't heard back from you in a while. Could you please provide the requested information? Thanks!

Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for dhcp3 (Ubuntu) because there has been no activity for 60 days.]

Changed in dhcp3 (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.