OpenWrt Forum Archive

Topic: dnsmasq: forwarding table overflow: check for server loops

The content of this topic has been archived on 8 Apr 2018. There are no obvious gaps in this topic, but there may still be some posts missing at the end.

in my logread i often find this record:

Mar 12 17:35:10 (none) kern.warn dnsmasq[719]: forwarding table overflow: check for server loops.
Mar 12 17:38:00 (none) kern.warn dnsmasq[719]: forwarding table overflow: check for server loops.
Mar 12 17:58:56 (none) kern.warn dnsmasq[719]: forwarding table overflow: check for server loops.
Mar 12 18:17:37 (none) kern.warn dnsmasq[719]: forwarding table overflow: check for server loops.
Mar 12 18:43:12 (none) kern.warn dnsmasq[719]: forwarding table overflow: check for server loops.
Mar 12 18:53:06 (none) kern.warn dnsmasq[719]: forwarding table overflow: check for server loops.
Mar 12 18:55:16 (none) kern.warn dnsmasq[719]: forwarding table overflow: check for server loops.

i can't find anything to fix it...

this is my dnsmasq.conf:

root@OpenWrt:~# cat /etc/dnsmasq.conf
# filter what we send upstream
domain-needed
bogus-priv
filterwin2k
localise-queries

# allow /etc/hosts and dhcp lookups via *.lan
#local=/lan/
#domain=lan

# enable dhcp (start,end,netmask,leasetime)
dhcp-authoritative
#dhcp-range=192.168.1.100,192.168.1.250,255.255.255.0,12h
#dhcp-leasefile=/tmp/dhcp.leases

# use /etc/ethers for static hosts; same format as --dhcp-host
# <hwaddr> [<hostname>] <ipaddr>
read-ethers

# other useful options:
# default route(s): dhcp-option=3,192.168.1.1,192.168.1.2
#    dns server(s): dhcp-option=6,192.168.1.1,192.168.1.2

except-interface=vlan1

dhcp-range=vlan0,192.168.254.100,192.168.254.150,255.255.255.0,6h
dhcp-range=eth1,192.168.254.200,192.168.254.250,255.255.255.0,2h

dhcp-leasefile=/tmp/dhcp.leases

dhcp-option=vlan0,3,192.168.254.1
dhcp-option=vlan0,6,192.168.254.1
dhcp-option=eth1,3,192.168.254.1
dhcp-option=eth1,6,192.168.254.1

Someone can help me?

I guess that the message is about the DNS forwarding. If this is the case then let the DNSmasq to advertise real DNS addresses and not itself to the DHCP clients.

The discussion might have continued from here.