Hi.
Just to recap - at the moment I'm running dnsmasq on my local server.
My resolv.conf now looks like this:
domain mydomain.com.au
search mydomain.com.au
nameserver 127.0.0.1
nameserver 208.67.220.220 # OpenDNS
nameserver 208.67.222.222 # OpenDNS
Things have been working OK on this setup. This should always use my
local NS first. Dnsmasq reads its config from the two OpenDNS servers
in this file - here is the log message when it starts:
Jun 23 07:55:37 mydomain dnsmasq[25455]: ignoring nameserver 127.0.0.1
- local interface
Jun 23 07:55:37 mydomain dnsmasq[25455]: read /etc/hosts - 2 addresses
On Sun, Jun 23, 2013 at 7:44 AM, Karsten Bräckelmann
<guent...@rudersport.de> wrote:
> On Sat, 2013-06-22 at 22:34 +0100, RW wrote:
>> On Sat, 22 Jun 2013 23:18:24 +0200 Karsten Bräckelmann wrote:
>>
>> > > If these things are true then the last question is - is it safe to
>> > > use OpenDNS IP addresses in my resolv.conf (and hence the remainder
>> > > of my small network) or should I stick to the addresses provided by
>> > > my ISP?
>> >
>> > I'd argue the evidence provided in this thread suggests to stick to
>> > the first nameserver currently listed in your resolv.conf -- your own.
>>
>> Except that it shouldn't be dnsmasq, which is just a cache.
>
> True, preferably it shouldn't. It may be, though, if it forwards to a
> resolving DNS that easily flies below the radar and doesn't get blocked
> for abuse by a DNSxL.
>
> I don't recall if the OP is running dnsmasq on his local DNS.
>
> However, when he dropped his ISP's nameservers and his local one became
> the first listed, it started to work. So his local DNS seems not to
> forward to the same nameservers he originally showed.
>
>
> --
> char *t="\10pse\0r\0dtu\0.@ghno\x4e\xc8\x79\xf4\xab\x51\x8a\x10\xf4\xf4\xc4";
> main(){ char h,m=h=*t++,*x=t+2*h,c,i,l=*x,s=0; for (i=0;i<l;i++){ i%8? c<<=1:
> (c=*++x); c&128 && (s+=h); if (!(h>>=1)||!t[s+h]){ putchar(t[s]);h=m;s=0; }}}
>
