Changeset 5079


Ignore:
Timestamp:
Jun 5, 2017, 2:49:28 PM (2 years ago)
Author:
hectorgh
Message:

using resolv.conf as a resolver instead of dns server ip

Location:
n4d-proxy/trunk/fuentes
Files:
3 edited

Legend:

Unmodified
Added
Removed
  • n4d-proxy/trunk/fuentes/debian/changelog

    r2358 r5079  
     1n4d-proxy (0.50) xenial; urgency=high
     2
     3  * Using resolv.conf as a dns resolver instead of IP
     4
     5 -- Hector Garcia Huerta <hectorgh@gmail.com>  Mon, 05 Jun 2017 14:48:38 +0200
     6
    17n4d-proxy (0.49) xenial; urgency=medium
    28
  • n4d-proxy/trunk/fuentes/debian/n4d-proxy.postinst

    r2358 r5079  
    7070                fi
    7171        fi
     72       
     73        if dpkg --compare-versions "$2" lt 0.50; then
     74                SQUID_FILE="/etc/squid/squid.conf"
     75               
     76                if [ -e  $SQUID_FILE ]; then
     77               
     78                        echo "Fixing dns_nameserver in squid conffile..."
     79                        sed -i -e "/^dns_nameservers 127.0.0.1/d" $SQUID_FILE
     80                        invoke-rc.d squid restart || true
     81                       
     82                fi
     83               
     84        fi
     85       
    7286
    7387        PKG="n4d-proxy"
  • n4d-proxy/trunk/fuentes/install.n4d-proxy/usr/share/n4d/templates/squid/squid.conf

    r1176 r5079  
    1111http_port 127.0.0.1:{{ PROXY_HTTP_PORT }}
    1212visible_hostname {{ PROXY_HOST }}
    13 dns_nameservers 127.0.0.1
     13
     14# Use /etc/resolv.conf instead
     15#dns_nameservers 127.0.0.1
     16
    1417# enabling single-word hostnames resolution
    1518dns_defnames on
Note: See TracChangeset for help on using the changeset viewer.