13 Feb
2004
13 Feb
'04
2 p.m.
Hi Brent,
Found in /etc/named.conf:
# The forwarders record contains a list of servers to which
queries
# should be forwarded. Enable this line and modify the IP
address to
# your provider's name server. Up to three servers may be
listed.
forwarders { 192.0.2.1; 192.0.2.2; };
I think what you need to configure is forwarders.
Tried, didn't work out as I wanted (was quite the same result as
with forward first).
My problem: for some subdomains, I delegate DNS to their respective
servers, on the internal network.
Example:
External: domain.lu is handled on my external servers. The MX points
to the external mail servers.
Internal: My internal DNS servers handle domain.lu, with more and
different data than what's seen externally.
sub1.domain.lu gets delegated to dns.sub1.domain.lu.
Now, without forwarders, when I do a
dig mx @dns1.admin.domain.lu sub1.domain.lu
I'll get the answer as returned by the dns.sub1.domain.lu server,
say mail.sub1.domain.lu.
If I add forwarders, pointing to the external DNS servers, for the
same query I get an answer from the external servers, i.e. giving the
external mail servers (say, mail.domain.lu) - so instead of internal
mail for sub1 going thus to mail.sub1.domain.lu, they'll go to the
external mailserver mail.domain.lu (catching everything for domain.lu
and routing it to the internal network), creating a mail loop.
I tried this also on bind9 by now, the effect remains the same as
on bind8.
I guess I'll just have to add my external servers to the root hints
file (no worry, I'll test before actually putting it in production).
Anyway, if VeriSlime goes through with putting Sitefinder back up,
we'll all have to fiddle around with our DNS servers more...
Since the "new" servers are of a more respectable power than the
current ones, I guess the current problems might just go away as
soon as we switch... but we'll see.
I love playing with Linux/Alpha ;-)
Greets Eric