GitLab

(2 items replaced)

It tried to bind to 255.255.0.0, which should fail, but doesn't on some
systems (CentOS for example). As a possible way forward, I've changed it
to 192.0.2.0, which does fail on CentOS. If this does not fail on other
systems, we should probably go for the proposed solution from #437, or
remove the test completely.

And fix a bug why it didn't work (a check or nested zonecuts prevented
detection of DNAME).

No need to check every time this added domain isn't origin, we create
one at creation of zone and keep it.

from a pointer to bool (following BIND 9's style convention).
so trivial, skipping review.

Apparently SunStudio's name mangler cannot handle the use of the typedef in the anonymous namespace in asiolink.cc. For now I have removed the offending use of it (the other instances where it was used were ok), we probably want to move it to a header and use it consistently. Much thanks to jinmei for pointing out the problem :)

 - made contextCheck() a const member function
 - move the comment about exception guarantee from contextCheck() to find()
 - parentheses around return

Conflicts:
	src/bin/auth/query.cc

in a function call that triggered typeerror exception.
okayed on jabber.

points to be considered with chaining.

Getting the NS returned delegation, it checked only if the callback is
enabled there and it was enabled because of DNAME.

The tests worked, but the timeouts were so small that on somewhat slower
systems the tests could fail. Increased them a bit.

The tests fail on assert in zonecutCallback currently.

In the previous commit I resolved a few merge conflicts, but too
hastily, this fixes 'em good

Just empty test bodies now.

Conflicts:
	src/bin/resolver/resolver.cc
	src/lib/asiolink/asiolink.cc
	src/lib/asiolink/asiolink.h
	src/lib/asiolink/tests/asiolink_unittest.cc

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

directly commiting to master, skipping review.

trivial doc fix, skipping review.

Also made it more portable not to use select.KQ_* until the add/delete
methods are actually called.

No chaining is implemented. While RFC 1024 indicates we should do it at
last inside the same zone, we don't now and leave it out for later.

The CNAME is handled in the same way as as SUCCESS with slight
modification about additional data (which probably never happen in real
life anyway).

No chaining yet.

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