When you include the external zone file in the internal view, you can't have the same hostname pointing to different IP addresses..
I would like to have mail.example.com point to 193.194.195.1 externally and mail.example.com point to 10.0.0.1 internally ...
Why don't you let it point to 193.194.195.1 and then let your router forward all requests to 10.0.0.1?
Because I want to keep internal traffic internal (and accounted only once, as internal) and not travel out-and-in again between two routers (internet-dmz and internal-lan)..
Or you set up an internal DNS server that resolves mail.example.com to your internal IP address and forwards all other requests to the "real" nameservers, and then you let the client PCs use that nameserver as the primary.
I ended up using two independent files (I did not include the external zone file in the internal).. The gotcha is the opposite of what is stated in the howto..
Quote:
But we are a small, smart start up, we can do better than copy-paste each modification to the zone file, furthermore, that is very error prone (will you always remember to modify the internal zone file when you modify the external one, or will you forget and spend some days debugging network problems ?).
Recent comments
5 hours 53 min ago
15 hours 21 min ago
16 hours 10 min ago
19 hours 44 min ago
1 day 8 min ago
1 day 30 min ago
1 day 2 hours ago
1 day 12 hours ago
1 day 17 hours ago
1 day 19 hours ago