BIND 10 #1553: b10-resolver basic feature test in lettuce
BIND 10 Development
do-not-reply at isc.org
Fri Jan 20 09:06:31 UTC 2012
#1553: b10-resolver basic feature test in lettuce
-------------------------------------+-------------------------------------
Reporter: jreed | Owner: jelte
Type: | Status: reviewing
defect | Milestone:
Priority: major | Sprint-20120124
Component: | Resolution:
resolver | Sensitive: 0
Keywords: | Sub-Project: DNS
Defect Severity: N/A | Estimated Difficulty: 0
Feature Depending on Ticket: | Total Hours: 0.5
Add Hours to Ticket: 0 |
Internal?: 0 |
-------------------------------------+-------------------------------------
Comment (by jelte):
Just for clarity, right now it actually works (as in, is contained)
because we are not doing priming right; we are not using root hints as a
base for priming, but setting the address of a root server permanently in
our cache; if we implement priming (one of the first tasks to do when we
continue work on the resolver, imo), this test *would* send out queries
(simply for starting a resolver). We will then also need to make priming
so that we can configure the root hints and set it to localhost where we
configure a fake root server as well (but currently, as we don't do real
priming at all, this isn't possible).
What is running is an actual resolver, and any queries not for l.root-
servers.net (btw, as a trivial task, shall we change it to f?) sent to it
would result in actual queries. But it is configured to only listen on
localhost port 47806, so I don't see this as a problem.
btw, I've also confirmed this experimentally; I ran this in an environment
without any network connectivity, and one with network but with running.
tcpdump reported no network activity, and as vorner already confirmed,
without (dns) networking, the test succeeds as well.
--
Ticket URL: <http://bind10.isc.org/ticket/1553#comment:11>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development
More information about the bind10-tickets
mailing list