Re: [Dnsmasq-discuss] Unable to resolve public/external hostnames

2013-07-24 Thread Koos Pol
Op 24-07-13 13:42, Weedy schreef: > I know I'm behind but FYI dnsmasq is installed and running[1] same as > any shitty SOHO router. In future look at TP-Link hardware, pretty much > everything they ship runs atheros radios (currently). Failing that just > try and buy stuff with atheros radios. >

Re: [Dnsmasq-discuss] Unable to resolve public/external hostnames

2013-07-24 Thread Weedy
On 09/06/13 03:31 AM, Koos Pol wrote: > Goodmorning all, > > > I've shot myself in the foot by purchasing a new router without a DNS *server* > aboard (Netgear WNDR4500). (For which I'm now in a lengthy, difficult > discussion with Netgear support. Why doesn't a consumer grade router doesn't > do

Re: [Dnsmasq-discuss] Unable to resolve public/external hostnames

2013-06-09 Thread Nick Warne
On Sun, Jun 09, 2013 at 04:58:21PM +0200, Koos Pol wrote: > Op 09-06-13 16:35, Nick Warne schreef: > > > OK, what does a: > > > > dig google.com > > > > return on the dns machine? > > > Quote of the day: "There is always someone smarter than you." > Thanks Nick, that was the right question: >

Re: [Dnsmasq-discuss] Unable to resolve public/external hostnames

2013-06-09 Thread Koos Pol
Op 09-06-13 16:35, Nick Warne schreef: > OK, what does a: > > dig google.com > > return on the dns machine? Quote of the day: "There is always someone smarter than you." Thanks Nick, that was the right question: dns1:/home/koos # dig google.com ; <<>> DiG 9.9.2-P2 <<>> google.com ;; global o

Re: [Dnsmasq-discuss] Unable to resolve public/external hostnames

2013-06-09 Thread Nick Warne
On Sun, Jun 09, 2013 at 04:30:13PM +0200, Koos Pol wrote: > Op 09-06-13 16:26, Koos Pol schreef: > > Op 09-06-13 16:13, Nick Warne schreef: > > > >> Well, dnsmasq is doing it's stuff, but nothing is found. Have you opened > >> port 53 on the router->dns box so answers get asked/given? > > > > We

Re: [Dnsmasq-discuss] Unable to resolve public/external hostnames

2013-06-09 Thread Koos Pol
Op 09-06-13 16:26, Koos Pol schreef: > Op 09-06-13 16:13, Nick Warne schreef: > >> Well, dnsmasq is doing it's stuff, but nothing is found. Have you opened >> port 53 on the router->dns box so answers get asked/given? > > Well, the router is at least listening on port 53: > > client1:/home/koos

Re: [Dnsmasq-discuss] Unable to resolve public/external hostnames

2013-06-09 Thread Koos Pol
Op 09-06-13 16:13, Nick Warne schreef: > Well, dnsmasq is doing it's stuff, but nothing is found. Have you opened > port 53 on the router->dns box so answers get asked/given? Well, the router is at least listening on port 53: client1:/home/koos # telnet 192.168.1.1 53 Trying 192.168.1.1... Conn

Re: [Dnsmasq-discuss] Unable to resolve public/external hostnames

2013-06-09 Thread Nick Warne
On Sun, Jun 09, 2013 at 04:06:30PM +0200, Koos Pol wrote: > Op 09-06-13 15:57, Nick Warne schreef: > > > On a client, do: > > > > dig google.com > > > > and post the output - you should see if dnsmasq is being used on the server > at the end of the output - like this: > > > client1: > ;google.co

Re: [Dnsmasq-discuss] Unable to resolve public/external hostnames

2013-06-09 Thread Koos Pol
Op 09-06-13 15:57, Nick Warne schreef: > On a client, do: > > dig google.com > > and post the output - you should see if dnsmasq is being used on the server at the end of the output - like this: client1: ;google.com.IN A ;; Query time: 6 msec ;; SERVER: 192.168.1.50#53(

Re: [Dnsmasq-discuss] Unable to resolve public/external hostnames

2013-06-09 Thread Nick Warne
On Sun, Jun 09, 2013 at 09:24:27AM -0400, Don Muller wrote: > I don't see that as part of the dhcp options. Add it to dhcp so it gets > passed to you clients. > > Obscuring private ip addresses in you messages makes no sense since only your > local LAN can access them. No one outside can access

Re: [Dnsmasq-discuss] Unable to resolve public/external hostnames

2013-06-09 Thread Don Muller
I don't see that as part of the dhcp options. Add it to dhcp so it gets passed to you clients. Obscuring private ip addresses in you messages makes no sense since only your local LAN can access them. No one outside can access them. Sent from my iPhone Don On Jun 9, 2013, at 9:18 AM, Koos Po

Re: [Dnsmasq-discuss] Unable to resolve public/external hostnames

2013-06-09 Thread Koos Pol
Op 09-06-13 15:16, Don Muller schreef: > What is the address of the server running DNSMASQ? Unless I missed it it > doesn't look like you include it in your DHCP options. > > Don Thanks Don. Perhaps a bit burried away: dns1 : x.x.x.50 > > On Jun 9, 2013, at 3:31 AM, Koos Pol wrote: >

Re: [Dnsmasq-discuss] Unable to resolve public/external hostnames

2013-06-09 Thread Don Muller
What is the address of the server running DNSMASQ? Unless I missed it it doesn't look like you include it in your DHCP options. Don On Jun 9, 2013, at 3:31 AM, Koos Pol wrote: > Goodmorning all, > > > I've shot myself in the foot by purchasing a new router without a DNS *server* > aboard (

Re: [Dnsmasq-discuss] Unable to resolve public/external hostnames

2013-06-09 Thread Chris Green
On Sun, Jun 09, 2013 at 09:31:46AM +0200, Koos Pol wrote: > Goodmorning all, > > > I've shot myself in the foot by purchasing a new router without a DNS *server* > aboard (Netgear WNDR4500). (For which I'm now in a lengthy, difficult > discussion with Netgear support. Why doesn't a consumer grade

[Dnsmasq-discuss] Unable to resolve public/external hostnames

2013-06-09 Thread Koos Pol
Goodmorning all, I've shot myself in the foot by purchasing a new router without a DNS *server* aboard (Netgear WNDR4500). (For which I'm now in a lengthy, difficult discussion with Netgear support. Why doesn't a consumer grade router doesn't do local name resolution? But that's an entire differe