View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
0000522Main CAcert Websitepublic2008-03-19 17:212013-01-15 02:15
Reporternetsurf Assigned To 
PrioritynormalSeveritymajorReproducibilityhave not tried
Status closedResolutionfixed 
Fixed in Version2009 Q2 
Summary0000522: DNS A record required to verify domain ownership
DescriptionWhen adding a new domain to cacert.org, if an A record is not in place for the domain (IE, example.com; not sub domains), the e-mail verification fails to send.

When registering dragon-security.net with cacert.org I encountered this problem. I haven't been able to reproduce it, since my only other domain is on cacert.org already.

My zone file is in additional information.

Additional Information$TTL 1h
; dragon-security.net
@ IN SOA ns1.dragon-security.net. admin.dragon-security.net. (
                                        200803182
                                        1h
                                        1h
                                        1h
                                        1h
                                )
<snip>
                IN A 99.135.242.178 ; << this is what I had to add
<snip>
TagsNo tags attached.
Reviewed by
Test Instructions

Relationships

related to 0000592 confirmed The domain name checking have to be improved to be auditable 

Activities

tigerp

2008-03-20 21:32

reporter   ~0001046

Did you already have the MX records for that domain before you tried to register it?
If you didn't then there would be no way to send an e-mail to you, because it is not known where the e-mail should be delivered.

netsurf

2008-03-20 22:04

reporter   ~0001047

MX records were in place. E-mail sent from outside servers worked as expected. The only change made between my multiple attempts that failed and the one that worked was adding that A record.

netsurf

2008-03-20 22:05

reporter   ~0001048

I suppose I can remove the domain from my cacert list and delete the A record. See if that reproduces it.

netsurf

2008-03-27 03:03

reporter   ~0001049

Last edited: 2008-03-27 03:04

 I can't reproduce this error when removing the A record. I'm suggesting this bug be closed. DNS registration was probably not updated at the time I first tried to add the domain and the server undoubtedly cached the record (that's my guess at least).

EDIT: I removed the A record about a week ago and forgot to check so the DNS changes had plenty of time to trickle down. The only other option is that the domain may have been added to a list in the mail server once it verified it. Perhaps? I don't have a way to check this.

Daniel Black

2009-06-03 04:04

reporter   ~0001422

looking through the website code quickly I only saw lookups of MX records and no lookups of A records.

closing as requested.

Issue History

Date Modified Username Field Change
2008-03-19 17:21 netsurf New Issue
2008-03-20 21:32 tigerp Note Added: 0001046
2008-03-20 22:04 netsurf Note Added: 0001047
2008-03-20 22:05 netsurf Note Added: 0001048
2008-03-27 03:03 netsurf Note Added: 0001049
2008-03-27 03:04 netsurf Note Edited: 0001049
2008-08-12 15:09 homer Relationship added related to 0000592
2009-06-03 04:04 Daniel Black Note Added: 0001422
2009-06-03 04:04 Daniel Black Status new => closed
2009-06-03 04:04 Daniel Black Resolution open => fixed
2012-01-25 17:17 NEOatNHNG Project bugs.cacert.org => Main CAcert Website
2013-01-15 02:15 Werner Dworak Fixed in Version => 2008
2013-01-15 02:15 Werner Dworak Fixed in Version 2008 => 2009 Q2