Technical data

8. Documentation for Developers
2. DNS configuration
• etc/resolv.conf
• etc/dnsmasq.conf
• etc/dnsmasq_dhcp.conf
• etc/resolv.dnsmasq
3. Hosts-File
• etc/hosts
4. imond-configuration
• etc/imond.conf
8.10.1. Provider Configuration
For the providers chosen User-ID and password are adapted in etc/ppp/pap-secrets.
Example for Provider Planet-Interkom:
# Secrets for authentication using PAP
# client server secret IP addresses
"anonymer" * "surfer" *
In this example “anonymer"’ is the USER-ID. As a remote server in principle anybody is
allowed (hence “*"’). “surfer"’ is the password for the Provider Planet-Interkom.
8.10.2. DNS Configuration
You can use fli4l as a DNS server. Why this is meaningful (and for Windows PCs in the LAN
even mandatory) is explained in the documentation of the “base"’ package.
The resolver file etc/resolv.conf contains the domain name and the name server to use.
It has the following contents (where “domain.de"’ only is a placeholder for the value of the
configuration variable DOMAIN_NAME):
search domain.de
nameserver 127.0.0.1
The DNS server dnsmasq is configured by the file etc/dnsmasq.conf. It is automatically
generated during boot by processing the scripts rc001.base and rc370.dnsmasq and might
look like this:
user=dns
group=dns
resolv-file=/etc/resolv.dnsmasq
no-poll
no-negcache
bogus-priv
log-queries
domain-suffix=lan.fli4l
local=/lan.fli4l/
domain-needed
338