[bind10-dev] b10-loadzone and origin handling

[Jeremy C. Reed]

Evan,

The following are results from loading my zone without an origin:

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.

When adding the -o ttltest origin on command line (after removing 
database):

sqlite> select * from zones ;
1|ttltest.ttltest|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

And I can't lookup any of these (at least I can't figure out how).

Then the following has the $ORIGIN ttltest. in the zone file:

sqlite> select * from zones ;
1|ttltest.|IN|0
sqlite> select * from records ;
1|1|ttltest.|ttltest.|12345|SOA||ttltest. root.ttltest. 1 2 3 4 5
2|1|ttltest.|ttltest.|12345|NS||ns.ttltest.
3|1|ttltest.|ttltest.|12345|A||1.2.3.4
4|1|ns.ttltest.|ttltest.ns.|12345|A||5.6.7.8

It appears to work fine for me.