Nick Hoffman wrote:
Originally, they were using the exact same data and data.cdb files: I'd
create data.cdb on ns1, copy it over to ns2, and restart tinydns on both
machines.
How do you copy it? How do you check if something has gone wrong? You
don't need to restart tinydns.
When I ran the following commands, ns1 would respond properly, but ns2
would say that it's not authoritative:
dig @202.168.41.222 www.voxpak.com
dig @202.168.41.238 www.voxpak.com
Given the same data file, tinydns would respond the same. It does not
compare the content of the data file with the IP address it is actually
answering from, so ns2 doesn't know it is ns2, it just says what you've
told it to say.
Here's a snippet from my original data file:
.voxpak.com:202.168.41.222:ns1.voxpak.com:259200
This line alone would make ns2 answer authoritatively.
When I switched the order of the NS records on ns2 and re-made data.cdb ,
ns2 responded to the dig command I listed above. What did I do wrong?
Most likely something else has gone wrong, perhaps an earlier update.
When you made the change and updated ns2 again, the complete and correct
data.cdb file was put in place and your data worked again. If you want,
you can switch the order of the NS records back to the original order
and try again.
Ketil Froyn
ketil@froyn.name
http://ketil.froyn.name/
|