GitLab

Add -I flag for builddir to find generated spec_config.h.

Also remove the ../spec_config.h target. It didn't work as-is
since it referenced file in the wrong directory. Instead of fixing
this I decided to remove. In normal build, the previous directory
does build it first. In the case of attempting to build specific
directories first, doesn't work yet due to other problems already
(like missing dns components).

This was noticed in a failed distcheck.

It failed to build a test, because the file was generated in another
directory and probably didn't yet exist at the time.

This is in the private range, so it should not conflict with anything
(we still might be unlucky if two tests run at the same time, but the
chance is low).

should be sufficiently trivial, directly committing to master.

ie. make sure no headers lead to it unintentionally (i.e.2 headers should not include asiolink.h, but the specific subparts we need) and cc files that include asiolink.h should include config.h first

needed to rename the terribly named src/bin/auth/config.h for this

It is taken from resolver tests and made generic. Then it is reused for
both resolver and authoritative tests.

It only stores the final result, and only looks into the cache at the start of a resolve() call right now, but it appears to work

Checks that we don't reject synthesized name of the maximum length by
mistake.

We overflow the size of name by prolonging a name of full length by
little bit.

As agreed, we don't provide the authority section for the original
DNAME/CNAME, only for the last target. As we don't chain, we don't
provide it at all.

It seems the RFC 2672 isn't too clear about it, but all checked
authoritative servers don't provide the authority section in case of
YXDOMAIN caused by too long synthesized name.

In particular:
* Use Use asiolink abstractions instead of Boost::asio directly
* Add cross-section checks (answer/question v authority)
* Extended description of bailiwick
* Methods added to isc::dns::Message and asiolink::IOAddress

points to be considered with chaining.

They are almost the same right now, but they will be different once the
CNAME chaining is implemented.

No chaining yet.

* Fixed a comment
* Modified condition in MockZone to match the one in MemoryZone.

Renamed IntervalTimer::setupTimer() -> IntervalTimer::setup()
Renamed IntervalTimerImpl::updateTimer() -> IntervalTimerImpl::update()