[bind10-dev] b10-loadzone and origin handling
Evan Hunt
each at isc.org
Mon Mar 8 23:53:42 UTC 2010
> sqlite> select * from zones ;
> 1|.|IN|0
> sqlite> select * from records ;
> 1|1|.|.|12345|SOA||ttltest. root.ttltest. 1 2 3 4 5
> 2|1|.|.|12345|NS||ns.
> 3|1|.|.|12345|A||1.2.3.4
> 4|1|ns.|ns.|12345|A||5.6.7.8
>
> So assumes is ".". Lookups of . A, . NS and . SOA work.
> I can't lookup ns. A though (REFUSED) -- I guess because ns. doesn't
> work with the . zones table entry.
ns. is a glue record, it should be showing up in the ADDITIONAL section.
I don't know why it isn't; that's a bug. (A known one, I think; Jinmei
reported something similar about glitches in glue answers at zone cuts.)
> When adding the -o ttltest origin on command line (after removing
> database):
>
> Then the following has the $ORIGIN ttltest. in the zone file:
Note that these are different, the -o option didn't have a trailing dot.
However, I think there's a bug in there anyway. With "-o ttltest."
you should get exactly the same results as "$ORIGIN ttltest."
eh
More information about the bind10-dev
mailing list