Bug #1861
closed
false log filterdns: host_dns: failed looking up "88.192.1250.131"
0%
Description
Hello,
I made a typo while entering an IP in a alias object.
1250 instead of 250
I validated the alias (5 IP list) and used it in a firewall rule (let out port 80 toward the alias IPs).
Then I fixed the typo,
and the initial warning still displays after some days....
filterdns: host_dns: failed looking up "88.192.1250.131": hostname nor servname provided, or not known
Editing the alias (moving from network type to hosts type), reapplying it do not remove the 'false log'.
Franck
Updated by Franck Bourdonnec about 13 years ago
(fyi, searching '1250' in a fresh backup gives nothing of course)
Updated by Franck Bourdonnec about 13 years ago
Sep 15 21:48:05 filterdns: host_dns: failed looking up "a184": hostname nor servname provided, or not known
Sep 15 21:48:05 filterdns: host_dns: failed looking up "file": hostname nor servname provided, or not known
Sep 15 21:43:05 filterdns: host_dns: failed looking up "a184": hostname nor servname provided, or not known
Sep 15 21:43:05 filterdns: host_dns: failed looking up "file": hostname nor servname provided, or not known
Hello,
frequence is 5 minutes
I think it is related to the regular updating of 'host alias' returning a list of ip (say google.com foor example)
uncorrectly handled
host google.com
google.com has address 209.85.148.99
google.com has address 209.85.148.103
google.com has address 209.85.148.106
google.com has address 209.85.148.104
google.com has address 209.85.148.147
google.com has address 209.85.148.105
google.com mail is handled by 40 alt3.aspmx.l.google.com.
google.com mail is handled by 50 alt4.aspmx.l.google.com.
google.com mail is handled by 20 alt1.aspmx.l.google.com.
google.com mail is handled by 10 aspmx.l.google.com.
google.com mail is handled by 30 alt2.aspmx.l.google.com.
Updated by Franck Bourdonnec about 13 years ago
Found your bug !
<alias>
<name>files2_zimbra_com</name>
<type>network</type>
<address>files2.zimbra.com.edgesuite.net./32 a1843.g.akamai.net./32</address>
<descr><![CDATA[Created from Diagnostics-> DNS Lookup]]></descr>
</alias>
The tool creating this alias wrongly use network/32 type instead of host !
host files2.zimbra.com.edgesuite.net
files2.zimbra.com.edgesuite.net is an alias for a1843.g.akamai.net.
a1843.g.akamai.net has address 80.239.224.27
a1843.g.akamai.net has address 80.239.224.8
Updated by Chris Buechler about 13 years ago
FQDNs in as network with a /32 are equivalent to hosts, that works fine, it's how all ours are setup.
Updated by Jim Pingle almost 12 years ago
- Status changed from New to Closed
This has been cleaned up a bit since then but some is expected behavior. Anything that's supposed to be an IP but isn't an IP is used as a hostname for filterdns. A typo can easily cause that, but there's no way around that really. If a typo or some other input ends up looking like a valid hostname, then it'll be passed on to filterdns.