Re: [PATCH] Fix configure with --disable-internal-dns compile error
On 6/06/2013 4:24 p.m., lowstz wrote: Hi, I try to build squid3.3.5 with ./configure --disable-internal-dns on Ubuntu Server 12.04 and Fedora 18, it throw the same error: dns.cc: In function ‘variable_list* snmp_netDnsFn(variable_list*, snint*)’: dns.cc:150:5: error: ‘snmpDebugOid’ was not declared in this scope The snmpDebugOid fucntion is defined in snmp_core.h, but it is not included in src/dns.cc. Zhanpeng Chen Thank you. This has been applied to squid-3. For the record: what reason are you still building or using the deprecated external DNS helper for? Amos
[PATCH] Fix configure with --disable-internal-dns compile error
Hi, I try to build squid3.3.5 with ./configure --disable-internal-dns on Ubuntu Server 12.04 and Fedora 18, it throw the same error: dns.cc: In function ‘variable_list* snmp_netDnsFn(variable_list*, snint*)’: dns.cc:150:5: error: ‘snmpDebugOid’ was not declared in this scope The snmpDebugOid fucntion is defined in snmp_core.h, but it is not included in src/dns.cc. Zhanpeng Chen === modified file 'src/dns.cc' --- src/dns.cc 2012-11-27 21:19:46 + +++ src/dns.cc 2013-06-04 13:41:22 + @@ -40,6 +40,10 @@ #include "Store.h" #include "wordlist.h" +#if SQUID_SNMP +#include "snmp_core.h" +#endif + /* MS VisualStudio Projects are monolitich, so we need the following #if to include the external DNS code in compile process when using external DNS.
Re: Bug 3.1 won't compile with --disable-internal-dns
On 21/02/11 16:51, Alex Rousskov wrote: Forwarding from info@ to squid-dev@. Mateuš, if you have a chance, please consider filing a bug report with bugzilla instead. Thank you, Alex. Original Message Subject: Bug 3.1 won't compile with --disable-internal-dns Date: Fri, 18 Feb 2011 20:59:41 + From: Mateuš Latusek Compiled with: ./configure --prefix=/usr/local/squid --disable-wccp --disable-wccpv2 --disable-snmp --disable-htcp --disable-http-violations --disable-ident-lookups --disable-internal-dns Logs attached. Cheers, M. Please do the bug report. Though check that it is not already reported. The obsolete dns helper is not really getting much interest any more. In the bug report we will also need details of what OS, compiler and build environment you are using to hit a problem. Along with a quote of the compiler complaint. Amos -- Please be using Current Stable Squid 2.7.STABLE9 or 3.1.11 Beta testers wanted for 3.2.0.5
Bug 3.1 won't compile with --disable-internal-dns
Forwarding from info@ to squid-dev@. Mateuš, if you have a chance, please consider filing a bug report with bugzilla instead. Thank you, Alex. Original Message Subject: Bug 3.1 won't compile with --disable-internal-dns Date: Fri, 18 Feb 2011 20:59:41 + From: Mateuš Latusek To: i...@squid-cache.org Compiled with: ./configure --prefix=/usr/local/squid --disable-wccp --disable-wccpv2 --disable-snmp --disable-htcp --disable-http-violations --disable-ident-lookups --disable-internal-dns Logs attached. Cheers, M. configure_log.gz Description: application/gzip make_log.gz Description: application/gzip
Re: --disable-internal-dns
On Sat, 14 Jan 2006, Rafael Martinez Torres wrote: Hi: I need transiently to bypass squid3's own dns subsystem, so I compiled with ./configure --disable-internal-dns... Things use to go well, unless you get an alias address, i.e. http://www.google.es bash-2.04$ host www.google.es www.google.es is an alias for www.google.com. www.google.com is an alias for www.l.google.com. www.l.google.com has address 64.233.183.104 www.l.google.com has address 64.233.183.147 www.l.google.com has address 64.233.183.99 Things go well if you type http://www.l.google.com but in case you type http://www.google.es you will get the attached error You've disabled internal DNS so Squid should be using the 'dnsserver' binary to do lookups. You can test it like this: echo www.google.es | ./dnsserver $addr 226 66.102.7.99 66.102.7.147 66.102.7.104 Thats what I get, which looks like it works. If you look at dnsserver.cc you'll see a for-loop where Squid does try up to three times to resolve the IP address. If you have a repeatable case where dnsserver cannot resolve www.google.es then its time to open a bug report I guess. Duane W.
Re: --disable-internal-dns
Yes, but note how "ping" react to an alias like www.google.es. bash-2.04$ ping www.google.es PING www.l.google.com (64.233.183.147) 56(84) bytes of data. 64 bytes from 64.233.183.147: icmp_seq=1 ttl=237 time=39.5 ms It is "intelligent" to ask again... Maybe the patch to apply is to fix with a loop "while (recoverable error) do (search for returned alias)" I type in pseudo-code because I don't know where to patch... Note that (recoverable error) is different from (host not found) recoverable error : " www.google.es" host not found: "www.google.ku" ok: "www.l.google.com" On Saturday 14 January 2006 14:28, Henrik Nordstrom wrote: > On Sat, 14 Jan 2006, Rafael Martinez Torres wrote: > > ./configure --disable-internal-dns... > > > > Things use to go well, unless you get an alias address, i.e. > > http://www.google.es > > Can you ping that address from the Squid box? > > Regards > Henrik
Re: --disable-internal-dns
Yes, but note how "ping" react to an alias like www.google.es. bash-2.04$ ping www.google.es PING www.l.google.com (64.233.183.147) 56(84) bytes of data. 64 bytes from 64.233.183.147: icmp_seq=1 ttl=237 time=39.5 ms It is "intelligent" to ask again... Maybe the patch to apply is to fix with a loop "while (recoverable error) do (search for returned alias)" I type in pseudo-code because I don't know where to patch... Note that (recoverable error) is different from (host not found) recoverable error : " www.google.es" host not found: "www.google.ku" host ok: "www.l.google.com" On Saturday 14 January 2006 14:28, Henrik Nordstrom wrote: > On Sat, 14 Jan 2006, Rafael Martinez Torres wrote: > > ./configure --disable-internal-dns... > > > > Things use to go well, unless you get an alias address, i.e. > > http://www.google.es > > Can you ping that address from the Squid box? > > Regards > Henrik On Saturday 14 January 2006 14:28, Henrik Nordstrom wrote: > On Sat, 14 Jan 2006, Rafael Martinez Torres wrote: > > ./configure --disable-internal-dns... > > > > Things use to go well, unless you get an alias address, i.e. > > http://www.google.es > > Can you ping that address from the Squid box? > > Regards > Henrik
Re: --disable-internal-dns
On Sat, 14 Jan 2006, Rafael Martinez Torres wrote: ./configure --disable-internal-dns... Things use to go well, unless you get an alias address, i.e. http://www.google.es Can you ping that address from the Squid box? Regards Henrik
--disable-internal-dns
Hi: I need transiently to bypass squid3's own dns subsystem, so I compiled with ./configure --disable-internal-dns... Things use to go well, unless you get an alias address, i.e. http://www.google.es bash-2.04$ host www.google.es www.google.es is an alias for www.google.com. www.google.com is an alias for www.l.google.com. www.l.google.com has address 64.233.183.104 www.l.google.com has address 64.233.183.147 www.l.google.com has address 64.233.183.99 Things go well if you type http://www.l.google.com but in case you type http://www.google.es you will get the attached error Any suggestion, any solution fix this problem ? The requested URL could not be retrieved While trying to retrieve the URL: http://www.google.es/ The following error was encountered: Unable to determine IP address from host name for www.google.es The dnsserver returned: DNS Domain 'www.google.es' is invalid: Non recoverable errors. This means that: The cache was not able to resolve the hostname presented in the URL. Check if the address is correct.
