I put the dns servers in a separate file /etc/dns.conf to decouple
dnsmasq from resolv.conf. This file only has the IPs of my ISPs DNS servers.
resolve.conf only has 127.0.0.1
Hi, Victor,
I have the same setup as yours, a separate file /etc/ppp/resolv.conf:
nameserver 206.248.a.b
nameserver
On 7/8/2012 4:42 AM, n22e113 wrote:
I put the dns servers in a separate file /etc/dns.conf to decouple
dnsmasq from resolv.conf. This file only has the IPs of my ISPs DNS servers.
resolve.conf only has 127.0.0.1
Hi, Victor,
I have the same setup as yours, a separate file
If this happens fairly regularly you could also just setup a ping from
your host to the ISP dns server (or whatever dns server you have dnsmasq
pointing to) and pipe the output to a file. When the dns fails check
the pinglog to see if connectivity upstream was broken. Hope this
helps,
On Sun,
Hi Victor
on 06.07.2012 22:35, Victor McAllister wrote:
I changed resolv.conf to only list 127.0.0.1 and my isps DNS machines.
AFAIK the resolver library goes through the namservers sequentially.
This improved the workings of dnsmasq. It has only lost its bearings to
the outside
On 7/3/2012 11:24 PM, Erich Titl wrote:
Hi Victor
at 03.07.2012 19:37, Victor McAllister wrote:
I am running LEAF 4.2.1
Every once in a while i run into long pauses trying to resolve an a DNS
address. I have 3 internal networks (one wireless) all of which look to
the router for DNS.
My
Hi Victor
at 03.07.2012 19:37, Victor McAllister wrote:
I am running LEAF 4.2.1
Every once in a while i run into long pauses trying to resolve an a DNS
address. I have 3 internal networks (one wireless) all of which look to
the router for DNS.
My /etc/reslov.conf
nameserver
I am running LEAF 4.2.1
Every once in a while i run into long pauses trying to resolve an a DNS
address. I have 3 internal networks (one wireless) all of which look to
the router for DNS.
My /etc/reslov.conf
nameserver 127.0.0.1
nameserver isps dns numbers
nameserver 192.168.1.254
