Hi everyone,

For hosting purpose, I have set up for my company a private DNS with its backup.
It's working great.
Now I'm working on the possibility for a remote script to update some parts of the configuration, so that hosted websites would be resolved with their local IP adresses instead of their public IP, because it's rejected by our Cisco firewalls as a "land attack". The path I have chosen for this is creating a dedicated zone that is going to be updatable by the remote script via nsupdate.
Once again, it's working great !
The servers (Fedora) are configured in their /etc/resolv.conf to search this dedicated updatable zone first, then the administration one.
The problem now ... Although the complete chain is working for a false domain like www.testestest.fr, I can't seem to make the servers resolve some real domains (ex : www.google.com) using the entries set in my dedicated updatable zone.

My question is, is there specific way to configure either the dns client or the named so that it will first try to search my local zones instead of immediately forward it to the public root servers ?

Thanks for your help.

For information, I resolved my problem by adding the option "ndots:3" to resolv.conf files. Not sure if this is a very standard configuration.