Adding arbitrary SRV/TXT/SPF records not attached to an existing host

cohoe / starrs

System Technology Accounting and Resource Registration Solution

grantcohoe.com/projects/starrs

Other

16 stars 6 forks source link

Adding arbitrary SRV/TXT/SPF records not attached to an existing host #106

Closed worr closed 12 years ago

worr commented 12 years ago

Oh and modification too.

cohoe commented 12 years ago

SRV records will never be associated with a zone since they point to a specific host. However TXT records do need this functionality. See also #115

cohoe commented 12 years ago

This has been completed and ready for v2.

clockfort commented 12 years ago

As a result of this, will you be doing full zonefile regeneration / clearing?

cohoe commented 12 years ago

That is now entirely possible. Right now you can only get table containing all the data that should not exist in the zonefile as far as IMPULSE is concerned. Once I get the last table restructure complete (#116 and #117) then a function can be easily added to automatically blow away all old data, cleaning the file.

clockfort commented 12 years ago

This will make you better than original start :-)

worr commented 12 years ago

What about SPF records?

cohoe commented 12 years ago

SPF's are stored as TXT in the zone, so a dedicated table to record type for them is not appropriate.

worr commented 12 years ago

Yes, sometimes they are. Sometimes they're stored as SPF records in the zone file as well.

Not making this up. http://en.wikipedia.org/wiki/Sender_Policy_Framework

cohoe commented 12 years ago

I stand corrected. However since the current RFC requires only one type for compliance (TXT or SPF) I am going to call it good enough. If the RFC changes, we can open this back up.