Technical data

4. Packages

ISDN_CIRC_1_ROUTE='0.0.0.0'

ISDN_CIRC_2_ROUTE='0.0.0.0'

We set a default route on both circuits and switch the route with the imond-client then - as

desired. Also in this case set DNS_ZONE_DELEGATION_N and DNS_ZONE_DELEGATION_x_DOMAIN_x

as described above.

If you want the reverse DNS resolution for such a network (e.g. an mail server will need

this) you can provide the optional variable DNS_ZONE_DELEGATION_x_NETWORK_x, which lists

the networks for active Reverse-Lookup. The following example illustrates this:

DNS_ZONE_DELEGATION_N='2'

DNS_ZONE_DELEGATION_1_UPSTREAM_SERVER_N='1'

DNS_ZONE_DELEGATION_1_UPSTREAM_SERVER_1_IP='192.168.1.12'

DNS_ZONE_DELEGATION_1_DOMAIN_N='1'

DNS_ZONE_DELEGATION_1_DOMAIN_1='firma.de'

DNS_ZONE_DELEGATION_1_NETWORK_N='1'

DNS_ZONE_DELEGATION_1_NETWORK_1='192.168.1.0/24'

DNS_ZONE_DELEGATION_2_UPSTREAM_SERVER_N='1'

DNS_ZONE_DELEGATION_2_UPSTREAM_SERVER_1_IP='192.168.2.12'

DNS_ZONE_DELEGATION_2_DOMAIN_N='1'

DNS_ZONE_DELEGATION_2_DOMAIN_1='bspfirma.de'

DNS_ZONE_DELEGATION_2_NETWORK_N='2'

DNS_ZONE_DELEGATION_2_NETWORK_1='192.168.2.0/24'

DNS_ZONE_DELEGATION_2_NETWORK_2='192.168.3.0/24'

with the conﬁg option DNS_ZONE_DELEGATION_x_UPTREAM_SERVER_x_QUERYSOURCEIP you can

deﬁne the source IP-address for outgoing DNS requests to upstream servers. This is

useful i.e. if you reach the upstream DNS server via a VPN and and don’t want the local

VPN address of ﬂi4l to appear as the source IP at the upstream server. Another usecase

is an IP address not routable for the Upstream DNS server (could happen in a VPN). In

this case it is as well necessary to set the IP address used by the dnsmasq to an IP used

by ﬂi4l to be accessible by the Upstream DNS Server.

DNS_ZONE_DELEGATION_N='1'

DNS_ZONE_DELEGATION_1_UPSTREAM_SERVER_N='1'

DNS_ZONE_DELEGATION_1_UPSTREAM_SERVER_1_IP='192.168.1.12'

DNS_ZONE_DELEGATION_1_UPSTREAM_SERVER_1_QUERYSOURCEIP='192.168.0.254'

DNS_ZONE_DELEGATION_1_DOMAIN_N='1'

DNS_ZONE_DELEGATION_1_DOMAIN_1='firma.de'

DNS_ZONE_DELEGATION_1_NETWORK_N='1'

DNS_ZONE_DELEGATION_1_NETWORK_1='192.168.1.0/24'

DNS_REBINDOK_N DNS_REBINDOK_x_DOMAIN The nameserver dnsmasq normally

declines responses from other name servers containing IP addresses from private networks.

It prevents a certain class of network attacks. But if you have a domain with private

IP addresses and a separate name server that is responsible for this network, exactly

the answers which would be rejected from dnsmasq are needed. List theese domains in

DNS_REBINDOK_x, to accept answers from this domain.

Another example for nameservers delivering private IP-Addresses as an answer are so

called “Real-Time Blacklist Server”. An example based on these might look like this: