-This test checks section 3.2.1 and 3.2.3 of RFC2136, which is the prerequisite section.
-This test also checks to see what happens when a backend does NOT support RFC2136.
+This test checks section 3.2.1 and 3.2.3 of RFC2136, which is the prerequisite
+section. This test also checks to see what happens when a backend does NOT
+support RFC2136.
-This test checks the specific case mentioned in RFC2136 3.2.3, where an RRSet is needed, and not the specific record.
+This test checks the specific case mentioned in RFC2136 3.2.3, where an RRSet is
+needed, and not the specific record.
-PowerDNS truncates incoming UDP packages. This might have effect on RFC2136 operation as packages might be very big.
+PowerDNS truncates incoming UDP packages. This might have effect on RFC2136
+operation as packages might be very big.
-This test performs a simple add and delete of a A and TXT record. This is typically with ISC's DHCPD does.
-The interesting thing is the case-sensativity, as hosts can have capital letters in them (it's how you configure the dhcpd's client machine).
+This test performs a simple add and delete of a A and TXT record. This is
+typically with ISC's DHCPD does. The interesting thing is the case-sensativity,
+as hosts can have capital letters in them (it's how you configure the dhcpd's
+client machine).
-A test to see if RFC2136 add and delete record works properly on a cname record. This is important because CNAME's have a special function
-when they are replaced. This test aims to check add/delete of the cname.
+A test to see if RFC2136 add and delete record works properly on a cname record.
+This is important because CNAME's have a special function when they are
+replaced. This test aims to check add/delete of the cname.
-This test tries to add SOA records in different ways which should all fail. Soa's are only updated (see 2dyndns-update-replace-soa)
+This test tries to add SOA records in different ways which should all fail.
+Soa's are only updated (see 2dyndns-update-replace-soa)
-This test performs a simple add and delete of an A-record on a very deep level, which should cause ENT's to be inserted.
-This test also validates if the cache is cleaned properly and NSEC(3) records are returned correctly.
+This test performs a simple add and delete of an A-record on a very deep level,
+which should cause ENT's to be inserted. This test also validates if the cache
+is cleaned properly and NSEC(3) records are returned correctly.
-This test adds a delegate and a delegate at a deeper level. It validates that ordername and auth are set correctly and no ENT's are inserted.
\ No newline at end of file
+This test adds a delegate and a delegate at a deeper level. It validates that
+ordername and auth are set correctly and no ENT's are inserted.
-This tests adds a delegate between two (existing) records. The test validates that we set our ordername correctly.
-It also validates that our cache is correctly purged (when we are selective about it).
\ No newline at end of file
+This tests adds a delegate between two (existing) records. The test validates
+that we set our ordername correctly. It also validates that our cache is
+correctly purged (when we are selective about it).
-For DNSSEC, PowerDNS uses the Auth and Ordername fields in the database. This tests adds an (delegate) NS and A record
-to the test.dyndns zone, it also deletes these records. The test is rather big because it should cover
-all the scenario's. This thus validates the correction of these records, known as rectify-zone.
+For DNSSEC, PowerDNS uses the Auth and Ordername fields in the database. This
+tests adds an (delegate) NS and A record to the test.dyndns zone, it also
+deletes these records. The test is rather big because it should cover all the
+scenario's. This thus validates the correction of these records, known as
+rectify-zone.
-This test deletes a record and add's it again. Another record with the same name exists, this test check if we only delete the correct record.
+This test deletes a record and add's it again. Another record with the same name
+exists, this test check if we only delete the correct record.
-This test performs a delete without a record type (which removes all the items with that name).
-It then adds the records again. Also contains an 'add' to the TXT
+This test performs a delete without a record type (which removes all the items
+with that name). It then adds the records again. Also contains an 'add' to the TXT
-This test checks to see if deleting a MX record with a specific Priority works correctly. This is
-interesting because the gsql-backends store priority in a seperate field, where other backends probably store it together with the content (or RDATA).
+This test checks to see if deleting a MX record with a specific Priority works
+correctly. This is interesting because the gsql-backends store priority in a
+seperate field, where other backends probably store it together with the content
+(or RDATA).
-This test checks if we delete NS records properly from the zone apex. There must always remain 1 NS record at the zone apex.
+This test checks if we delete NS records properly from the zone apex. There must
+always remain 1 NS record at the zone apex.
-This test adds 2 delegates below each other and deletes the top delegate.
\ No newline at end of file
+This test adds 2 delegates below each other and deletes the top delegate.
-This test checks if we add a record correctly in between two other records. This requires us to correct ENT records.
-The test is also focussed on checking if we purge our cache correctly.
\ No newline at end of file
+This test checks if we add a record correctly in between two other records.
+This requires us to correct ENT records. The test is also focussed on checking
+if we purge our cache correctly.
-We allow to add/remove the NSEC3PARAM record, this test confirms that everything is working correctly.
-The test operates a bit different when in NSEC mode, as we don't add a NSEC3PARAM at the end.
-In NSEC3-NARROW mode, we do add NSEC3PARAM's at the end, but these are then in non-narrow mode as we cannot
-specify narrow mode in the NSEC3PARAM and the delete of the NSEC3PARAM also removed the narrow flag.
+We allow to add/remove the NSEC3PARAM record, this test confirms that everything
+is working correctly. The test operates a bit different when in NSEC mode, as we
+don't add a NSEC3PARAM at the end. In NSEC3-NARROW mode, we do add NSEC3PARAM's
+at the end, but these are then in non-narrow mode as we cannot specify narrow
+mode in the NSEC3PARAM and the delete of the NSEC3PARAM also removed the narrow
+flag.
-A test for RFC2136 which checks section 3.4.2.2 - Replacing CNAME record.
\ No newline at end of file
+A test for RFC2136 which checks section 3.4.2.2 - Replacing CNAME record.
-A test for RFC2136 which checks section 3.4.2.2 - Replacing a record.
-In this test, we specifically use MX record, to see if the TTL changes of the MX record with the correct priority.
\ No newline at end of file
+A test for RFC2136 which checks section 3.4.2.2 - Replacing a record. In this
+test, we specifically use MX record, to see if the TTL changes of the MX record
+with the correct priority.
-This test checks to see if SRV records are parsed/handled correctly when adding/updating/deleting
-via RFC2136.
+This test checks to see if SRV records are parsed/handled correctly when
+adding/updating/deleting via RFC2136.
-A test for RFC2136 which checks section 3.4.2.2 - Update the TTL, which occurs if the record + content is the same.
+A test for RFC2136 which checks section 3.4.2.2 - Update the TTL, which occurs
+if the record + content is the same.
-A test for RFC2136 which checks section 3.4.2.2 - Replacing a SOA record.
-This is special because we can 'set' the soa serial.
-This test also does not use the hidesoaserial option because we want to compare that serial. It's also the reason why the test is run only once.
-
+A test for RFC2136 which checks section 3.4.2.2 - Replacing a SOA record. This
+is special because we can 'set' the soa serial. This test also does not use the
+hidesoaserial option because we want to compare that serial. It's also the
+reason why the test is run only once.
-Restore SOA resial to it's original value
\ No newline at end of file
+Restore SOA resial to it's original value.
projects / pdns / commitdiff