Robert Singer said: > Hello everybody, Phew.. I *think* I can answer most of this. Please slap me around a bit if I get something wrong. :)
> I have installed Vegadns (Version 0.9.9) successful and added a local > Test Zone. > TLD: test.org Assumption #1. You don't "own" test.org. > When I ask tinydns with the dig command I get the correct results. Since > it is a local domain, I want my internal dnscache to query this domain. > The internal dnscache is also used by people to surf the internet. Assumption #2, you did a dig, specifying the name server to ask... > So I have to put test.org manually in the dnscache /root/servers with the > IP Address of tinydns. Since you do not own test.org, yes. If you owned it, that would be another story. In that case, you'd have to tell dnscache that the 192.168.10.0 subnet is being handled by your tinydns instance. > My question is now, is it possible when I create a TLD with Vegadns that > the program also write the TLD entry to the DNSCACHE, Sure. Anything's possible. Of course, you'll need to add some code to vega... Could it be done? Sure. Will it? Not so sure.. That's really up to Bill... OR.. you could write a patch to add it, submit the patch, and Bill could either integrate the patch, or make it available via his website.. Both, of course, are at his discretion.. > I tried the following thing... > > I want to teach the dnscache that he should first query the internal DNS > for all queries. So I put 192.168.10.3 into the @ file under the > dnscache /root/servers. But when I use my dnscache to query the test.org > domain I get not my internal IP address. I get the official IP Address > of it. This is not good. It seems that my internal dnscache do not ask > my internal dns server for the ip and go directly outside to the TLD > root DNS servers.... Ahh.. you fell prey to the "random root server" ... :) Just because you add your IP to the top of the root servers file doesn't mean it will be asked first. I'm not sure if the servers are used sequentially, storing the last server used in memory, or randomly. It does not, however, walk through the list. So, you have a chance of it being right each time the ttl expires and the cache looks the entry up again via the root server. > So is there a possibility to tell dnscache to always query the internal > dns server and if this zone is not present, try to reach another DNS > Cache (i.e. my Provider's one). Hrm... Honestly, I'm not sure.. However, you are kind of breaking the rules here.. See, you don't own test.org.. So, why are you trying to serve dns for it? I can think of a number of reasons for this myself, and many of them are valid. However, I can't see this being a common practice. So, yes. You'll need to add this manually to each dnscache. But you shouldn't have to do it often since there are only a few instances where you'd want to do this sort of domain hijacking anyways... > Can I do that by modifying the update-data.sh? (I am not so good at > scripting so I tried it with the forward DNS Cache) Hrm.. Yes.. and no.. You'd have to have a list somewhere of the domains you want to add this way. Ultimately, it'd be nice to have vega store that in its database, but that would take some code changes... > Is this assumption right?... Many many questions... I know.... :-) Semi-right, yeah.. :) Questions are good.. They make ya think and show that you are thinking.. :) > Best, and thanks for reading this long posting No problem.. Did I answer everything? :) > Robert --------------------------- Jason 'XenoPhage' Frisvold Engine / Technology Programmer [EMAIL PROTECTED] RedHat Certified - RHCE # 803004140609871 MySQL Pro Certified - ID# 207171862 MySQL Core Certified - ID# 205982910 --------------------------- "Something mysterious is formed, born in the silent void. Waiting alone and unmoving, it is at once still and yet in constant motion. It is the source of all programs. I do not know its name, so I will call it the Tao of Programming."
