[Dnsmasq-discuss] Can anyone suggest where I should be looking for what's causing this error?
My desktop/server runs as a web server, it serves the domain zbmc.eu. It's set up so that local client requests for web pages from zbmc.eu go 'out and back' as it were, this way I can be more certain that web pages that work locally also work when accessed from outside. However sometimes I notice long pauses when displaying web pages so, in an attempt to diagnose this I have turned on DNS logging in dnsmasq (which runs on another server on my LAN). Just now I saw this:- Apr 8 16:40:56 dps dnsmasq[22279]: query[] zbmc.eu from 192.168.1.4 Apr 8 16:40:56 dps dnsmasq[22279]: forwarded zbmc.eu to 195.74.113.58 Apr 8 16:40:56 dps dnsmasq[22279]: forwarded zbmc.eu to 194.72.0.114 Apr 8 16:41:01 dps dnsmasq[22279]: query[] zbmc.eu.zbmc.eu from 192.168.1.4 Apr 8 16:41:01 dps dnsmasq[22279]: forwarded zbmc.eu.zbmc.eu to 195.74.113.58 Apr 8 16:41:01 dps dnsmasq[22279]: forwarded zbmc.eu.zbmc.eu to 194.72.0.114 Apr 8 16:41:01 dps dnsmasq[22279]: reply zbmc.eu.zbmc.eu is NXDOMAIN-IPv6 Apr 8 16:41:01 dps dnsmasq[22279]: query[A] zbmc.eu from 192.168.1.4 Apr 8 16:41:01 dps dnsmasq[22279]: forwarded zbmc.eu to 195.74.113.58 Apr 8 16:41:02 dps dnsmasq[22279]: reply zbmc.eu is 84.45.228.40 Apr 8 16:41:17 dps dnsmasq[22279]: query[A] info.gigaset.net from 192.168.1.129 Apr 8 16:41:17 dps dnsmasq[22279]: cached info.gigaset.net is 217.67.103.237 Those requests for zbmc.eu.zbmc.eu look a bit worrying! :-) Can anyone suggest what I might have misconfigured such that it would do this? I *think* the particular request(s) that caused this were to display some DokuWiki pages, but I'm not absolutely certain. Is there any other sort of logging I can turn on (in apache2 for example) which might show me the cause? -- Chris Green
Re: [Dnsmasq-discuss] Can anyone suggest where I should be looking for what's causing this error?
On Fri, Apr 08, 2011 at 04:50:04PM +0100, Chris G wrote: My desktop/server runs as a web server, it serves the domain zbmc.eu. It's set up so that local client requests for web pages from zbmc.eu go 'out and back' as it were, this way I can be more certain that web pages that work locally also work when accessed from outside. However sometimes I notice long pauses when displaying web pages so, in an attempt to diagnose this I have turned on DNS logging in dnsmasq (which runs on another server on my LAN). Just now I saw this:- Apr 8 16:40:56 dps dnsmasq[22279]: query[] zbmc.eu from 192.168.1.4 Apr 8 16:40:56 dps dnsmasq[22279]: forwarded zbmc.eu to 195.74.113.58 Apr 8 16:40:56 dps dnsmasq[22279]: forwarded zbmc.eu to 194.72.0.114 Apr 8 16:41:01 dps dnsmasq[22279]: query[] zbmc.eu.zbmc.eu from 192.168.1.4 Apr 8 16:41:01 dps dnsmasq[22279]: forwarded zbmc.eu.zbmc.eu to 195.74.113.58 Apr 8 16:41:01 dps dnsmasq[22279]: forwarded zbmc.eu.zbmc.eu to 194.72.0.114 Apr 8 16:41:01 dps dnsmasq[22279]: reply zbmc.eu.zbmc.eu is NXDOMAIN-IPv6 Apr 8 16:41:01 dps dnsmasq[22279]: query[A] zbmc.eu from 192.168.1.4 Apr 8 16:41:01 dps dnsmasq[22279]: forwarded zbmc.eu to 195.74.113.58 Apr 8 16:41:02 dps dnsmasq[22279]: reply zbmc.eu is 84.45.228.40 Apr 8 16:41:17 dps dnsmasq[22279]: query[A] info.gigaset.net from 192.168.1.129 Apr 8 16:41:17 dps dnsmasq[22279]: cached info.gigaset.net is 217.67.103.237 Those requests for zbmc.eu.zbmc.eu look a bit worrying! :-) Can anyone suggest what I might have misconfigured such that it would do this? I *think* the particular request(s) that caused this were to display some DokuWiki pages, but I'm not absolutely certain. Is there any other sort of logging I can turn on (in apache2 for example) which might show me the cause? Or this sequence:- Apr 8 16:56:27 dps dnsmasq[22279]: query[] zbmc.eu from 192.168.1.4 Apr 8 16:56:27 dps dnsmasq[22279]: forwarded zbmc.eu to 195.74.113.58 Apr 8 16:56:27 dps dnsmasq[22279]: forwarded zbmc.eu to 194.72.0.114 Apr 8 16:56:27 dps dnsmasq[22279]: reply zbmc.eu is NODATA-IPv6 Apr 8 16:56:27 dps dnsmasq[22279]: query[] zbmc.eu.zbmc.eu from 192.168.1.4 Apr 8 16:56:27 dps dnsmasq[22279]: forwarded zbmc.eu.zbmc.eu to 195.74.113.58 Apr 8 16:56:27 dps dnsmasq[22279]: reply zbmc.eu.zbmc.eu is NXDOMAIN-IPv6 Apr 8 16:56:27 dps dnsmasq[22279]: query[A] zbmc.eu from 192.168.1.4 Apr 8 16:56:27 dps dnsmasq[22279]: forwarded zbmc.eu to 195.74.113.58 Apr 8 16:56:27 dps dnsmasq[22279]: reply zbmc.eu is 84.45.228.40 -- Chris Green
Re: [Dnsmasq-discuss] Weird issue when pinging FQDN
On Wed, Mar 30, 2011 at 04:18:27PM -0500, Frederick C. Damen wrote: I suspect you may find the cause of your issue to do with the fact that ping resolves names with resources, i.e. files etc, local to the machine before finding a DNS server to resolve the name. Dig I am lead to believe goes straight to the DNS server. I think this may well relate to my question a week or so ago. I had a problem arising from a machine that had a 'domain' or 'search' configuration statement in /etc/resolv.conf which did not exist on all the other machines on the LAN causing symptoms similar to what you describe. I have found that I need to remove a load of default junk that gets installed into /etc/hosts on the client machines in order that those machines pick up their FQDN from the dnsmasq server correctly. E.g. on this machine (which is a client machine) the /etc/hosts is simply:- 127.0.0.1 localhost # The following lines are desirable for IPv6 capable hosts ::1 localhost ip6-localhost ip6-loopback fe00::0 ip6-localnet ff00::0 ip6-mcastprefix ff02::1 ip6-allnodes ff02::2 ip6-allrouters If Network Manager is installed it will *change* /etc/hosts as follows:- 127.0.0.1 chris localhost.localdomain localhost ::1 chris localhost6.localdomain6 localhost6 # The following lines are desirable for IPv6 capable hosts ::1 localhost ip6-localhost ip6-loopback fe00::0 ip6-localnet ff00::0 ip6-mcastprefix ff02::1 ip6-allnodes ff02::2 ip6-allrouters The above screws up the client machines FQDN and various things complain about it. Oh, /etc/resolv.conf is:- nameserver 192.168.1.2 domain zbmc.eu search zbmc.eu -- Chris Green
Re: [Dnsmasq-discuss] Question about /etc/hosts and problem with Ubuntu 10.10
On Sun, Mar 20, 2011 at 07:19:22PM +, Chris G wrote: [snip] Well I've fixed the basic problem, I've uninstalled Network Manager and installed wicd instead, now my /etc/hosts is left alone and so the immediate problem is solved. However I'd still like an answer to the first question:- So, two questions:- 1 - Are my /etc/hosts files OK (without the Network Manager changes that is)? I.e. is what I have the correct way to get what I want? To be more complete/explicit. This is a small SoHo LAN behind a NAT router, it has a static IP and I have a domain (zbmc.eu) which points to it. The router allows incoming SMTP, HTTP and ssh connections. There are several machines in the LAN behind the router, the router is 192.168.1.1, the dnsmasq server runs on machine 'dps' which is 192.168.1.2 and its /etc/hosts is:- 127.0.0.1 localhost # The following lines are desirable for IPv6 capable hosts ::1 localhost ip6-localhost ip6-loopback fe00::0 ip6-localnet ff00::0 ip6-mcastprefix ff02::1 ip6-allnodes ff02::2 ip6-allrouters ff02::3 ip6-allhosts # # # Systems with static addresses, dnsmasq distributes these to the others # 192.168.1.1 vigor 2820n 192.168.1.2 dps dps.zbmc.eu 192.168.1.3 hp7310 HPEDDBB7 HP000D9D068F7D 192.168.1.4 chris mws boat info 192.168.13.254 2wire BT2700HGV gateway.2wire.net Incoming SMTP conenctions go to 192.168.1.2, HTTP and ssh go to 192.168.1.4 (done by firewall/routing tables in the router). Is the above correct/OK for what I want? There's virtually nothing non-default in /etc/dnsmasq.conf, just one dhcp-host= mapping for a NAS that doesn't give its name out when using dnsmasq's DHCP. All the other machines on the LAN (including the one that I had problems with until removing Network Manager) have an /etc/hosts file as follows:- 127.0.0.1 localhost # The following lines are desirable for IPv6 capable hosts ::1 localhost ip6-localhost ip6-loopback fe00::0 ip6-localnet ff00::0 ip6-mcastprefix ff02::1 ip6-allnodes ff02::2 ip6-allrouters The one important requirement is that the machine chris (192.168.1.4) can find its domain name correctly as both apache2 and leafnode complain otherwise. (This was what Network Manager was breaking by modifying /etc/hosts). Any/all feedback (within reason!) would be welcome. Oh, nearly all the machines are running xubuntu or ubuntu 10.04, except 'chris' which is now 10.10. -- Chris Green
[Dnsmasq-discuss] Question about /etc/hosts and problem with Ubuntu 10.10
I have a small SoHo LAN on which I run dnsmasq 2.52 on one of the machines (dps, 192.168.1.2) to provide DHCP and DNS. There are some static IP addresses on the LAN and thus the /etc/hosts on the machine where dnsmasq runs is as follows:- 127.0.0.1 localhost # The following lines are desirable for IPv6 capable hosts ::1 localhost ip6-localhost ip6-loopback fe00::0 ip6-localnet ff00::0 ip6-mcastprefix ff02::1 ip6-allnodes ff02::2 ip6-allrouters ff02::3 ip6-allhosts # # # Systems with static addresses, dnsmasq distributes these to the others # 192.168.1.1 vigor 2820n 192.168.1.2 dps dps.zbmc.eu 192.168.1.3 hp7310 HPEDDBB7 HP000D9D068F7D 192.168.1.4 chris mws boat info 192.168.13.254 2wire BT2700HGV gateway.2wire.net I'm having a problem with the machine 'chris', 192.168.1.4, since I upgraded it to xubuntu 10.10 (all other machines are still at 10.04). After the upgrade something (Network Manager I guess) insists on changing the /etc/hosts file to the following:- 127.0.0.1 chris localhost.localdomain localhost ::1 chris localhost6.localdomain6 localhost6 # The following lines are desirable for IPv6 capable hosts ::1 localhost ip6-localhost ip6-loopback fe00::0 ip6-localnet ff00::0 ip6-mcastprefix ff02::1 ip6-allnodes ff02::2 ip6-allrouters ... up until the 10.10 upgrade my /etc/hosts was:- 127.0.0.1 localhost # The following lines are desirable for IPv6 capable hosts ::1 localhost ip6-localhost ip6-loopback fe00::0 ip6-localnet ff00::0 ip6-mcastprefix ff02::1 ip6-allnodes ff02::2 ip6-allrouters which worked perfectly. However with the Network Manager changes the machine 'chris' doesn't think it has a proper domain and apache2 and leafnode complain about there not being a valid domain. So, two questions:- 1 - Are my /etc/hosts files OK (without the Network Manager changes that is)? I.e. is what I have the correct way to get what I want? 2 - Can anyone suggest a workaround to prevent Network Manager overwriting /etc/hosts or a way to change /etc/hosts so dnsmasq will still work correctly in spite of the Network Manager changes. -- Chris Green
[Dnsmasq-discuss] Odd result for one computer on my LAN
I get a very odd result in response to the 'host' command for just *one* computer on my LAN, see the result for 'oldchris' below:- chris$ host chris.zbmc.eu chris.zbmc.eu has address 192.168.1.4 chris$ host dps.zbmc.eu dps.zbmc.eu has address 192.168.1.2 chris$ host oldchris.zbmc.eu oldchris.zbmc.eu has address 192.168.1.140 Host oldchris.zbmc.eu not found: 3(NXDOMAIN) chris$ host backup.zbmc.eu backup.zbmc.eu has address 192.168.1.88 chris$ host laptop.zbmc.eu laptop.zbmc.eu has address 192.168.1.84 chris$ host dps dps.zbmc.eu has address 192.168.1.2 The machine dps.zbmc.eu is the one that is running dnsmasq. It's an Ubuntu server 10.04 running dnsmasq version 2.52. -- Chris Green
[Dnsmasq-discuss] How to provide a local abbreviation for an external web site?
I guess this isn't wholly a dnsmasq question but dnsmasq can probably provide what I need to do it. I'm running dnsmasq on a small server which provides DNS (and some other services) for our small (one user most of the time, sometimes two) SoHo LAN. I'm doing some development work which involves lots of git and ssh (and other) access to a (virtual) machine which has a horribly long domain name. So I'd like to be able to use an abbreviated name, what's the best way to do this? If I simply put something like:- myname 1.2.3.4 In /etc/hosts on the dnsmasq server machine then I can use just 'myname' and I get the right address but dnsmasq assumes (quite reasonably) that the full name is myname.zbmc.eu since the LAN's domain as seen from 'outside' is zbmc.eu. Is there a way of getting dnsmasq to allow me to use 'myname' as an abbreviation for 'averylongname.co.uk' rather than as as a short form of myname.zbmc.eu? -- Chris Green
Re: [Dnsmasq-discuss] Linksys routers, bridges, network appliances: host names
On Thu, Nov 18, 2010 at 03:15:08PM -0500, John R. Graham wrote: Most of these little Linksys devices are capable of getting an IP address via DHCP from dnsmasq but none of them (that I have tried) seem capable of delivering their host name to dnsmasq as all of my Linux and Windows boxen do. Is this a known limitation of these little boxes, or do I need to do something I haven't done in the dnsmasq.conf file? I can pull a Wireshark trace of the DHCP transaction if that would be helpful. It's quite a problem with various small devices, I have a Western Digital NAS which doesn't provide itself with a name when it gets its IP from dnsmasq. I have the following at the end of my dnsmasq.conf to deal with this:- dhcp-host=00:90:a9:70:06:ff,backup -- Chris Green
[Dnsmasq-discuss] A question about host names behind NAT
I run a small SoHo network behind a NAT router, all pretty conventional, nearly all the machines run either Ubuntu Server 10.04 or Xubuntu 10.04. I run dnsmasq on one of the server machines (called dps - for DNS and Print Server) to provide DNS and DHCP for the network. I recently had a problem with Postfix on one of the machines being unable to send E-Mail to the outside world (an old problem only recently noticed, it had always been like that) which I have now fixed but, in the opinion of the Postfix list, the fix is a bodge and contravenes some rules on zone files etc. OK, it's on my local network and doesn't affect anyone else but I'd like to do things right if I can - and it will probably minimise future problems. So, I have the following significant computers on the network:- Router - vigor 2820n - 192.168.1.1 DNS and Print server - dps - 192.168.1.2 Printer - hp7310 - 192.168.1.3 Mail and Web server - mws - 192.168.1.4 Remaining machines get their IP from dps when they start up /etc/host on dps is as follows:- 127.0.0.1 localhost # The following lines are desirable for IPv6 capable hosts ::1 localhost ip6-localhost ip6-loopback fe00::0 ip6-localnet ff00::0 ip6-mcastprefix ff02::1 ip6-allnodes ff02::2 ip6-allrouters ff02::3 ip6-allhosts # # # Systems with static addresses, dnsmasq distributes these to the others # 192.168.1.1 vigor 2820n 192.168.1.2 dps dps.zbmc.eu 192.168.1.3 hp7310 HPEDDBB7 HP000D9D068F7D 192.168.1.4 mws mws.zbmc.eu zbmc.eu dte dte-test dte-mine dte-live dte-orig 192.168.13.254 2wire BT2700HGV gateway.2wire.net The problem I had with postfix was that E-Mail sent from dps (which uses mws as its relayhost) was rejected because zbmc.eu was (at that time) an 'outside' address. So I added the zbmc.eu entry to 192.168.1.4 in /etc/hosts and then all was well. The domain zbmc.eu is mine and the domain is hosted at gandi.net (i.e. there's a zone file there), I can edit the zone file as needed. At present it is:- dte 10800 IN CNAME zbmc.eu. @ 10800 IN MX 10 zbmc.eu. mws 10800 IN CNAME zbmc.eu. imap 10800 IN CNAME access.mail.gandi.net. www 10800 IN CNAME zbmc.eu. smtp 10800 IN CNAME relay.mail.gandi.net. pop 10800 IN CNAME access.mail.gandi.net. blog 10800 IN CNAME blogs.vip.gandi.net. webmail 10800 IN CNAME agent.mail.gandi.net. @ 10800 IN A 84.45.228.40 dte-live 10800 IN CNAME zbmc.eu. dte-mine 10800 IN CNAME zbmc.eu. dte-orig 10800 IN CNAME zbmc.eu. dte-test 10800 IN CNAME zbmc.eu. All the dte- entries are for virtual hosted web servers. The real issue is around the mws entries. There isn't a virtual web server using 'mws' so it's not necessary from that point of view, in fact I'm not at all sure that I need it at all now - should I delete it? When I do a 'host mws' on one of my home machines I see:- chris$ host mws mws.zbmc.eu has address 192.168.1.4 mws.zbmc.eu is an alias for zbmc.eu. mws.zbmc.eu is an alias for zbmc.eu. zbmc.eu mail is handled by 10 zbmc.eu. I guess if I remove mws from the 'outside' zone file all those aliases and mail records will disappear (and they're what caused my original Postfix problem). Is that how things should be - no CNAME record in the outside zone file should be the same as the name of an actual machine on my LAN behind the NAT router? Sorry for such a long E-Mail but there's lots of information bears on the problem. -- Chris Green
Re: [Dnsmasq-discuss] Simple question how to give multiple names to one host?
On Mon, Feb 08, 2010 at 06:57:32PM -0600, richardvo...@gmail.com wrote: On Mon, Feb 8, 2010 at 3:59 PM, Simon Kelley si...@thekelleys.org.uk wrote: Chris G wrote: On Sun, Feb 07, 2010 at 08:16:42PM +, Simon Kelley wrote: Chris G wrote: I have a dnsmasq.conf file with the following at the end:- dhcp-host=chris,192.168.1.4 How do I get 192.168.1.4 to have some other names as well (for apache2 virtual hosting)? Equally simple answer: cname=some other name,chris You can have as many CNAMEs as you like for the primary name. Brilliant, thanks, it just wasn't very easy to find in the dnsmasq man page. I've added a pointer to --cname on the section on --dhcp-host. It might also be worthwhile using the word alias in the description of --cname, because that's one of the most common search terms (AFAICT). Yes, I tried searching for 'alias' in the man page when I was trying to work out how to do this. -- Chris Green
[Dnsmasq-discuss] Simple question how to give multiple names to one host?
I have a dnsmasq.conf file with the following at the end:- dhcp-host=chris,192.168.1.4 How do I get 192.168.1.4 to have some other names as well (for apache2 virtual hosting)? -- Chris Green
Re: [Dnsmasq-discuss] dnsmasq returns addresses for non-existent hosts - what have I mis-configured?
On Mon, Nov 09, 2009 at 01:58:25PM +, Chris G wrote: On Sun, Nov 08, 2009 at 10:25:11AM -0500, Perette Barella wrote: It looks like your provider has set up a wildcard A record, which is similar to DNS hijacking as a helpful feature to users who miskey a domain name. It's not isolated to you: mugenshi:etc x10$ host ghijk.isbd.net ghijk.isbd.net has address 195.74.61.93 ghijk.isbd.net mail is handled by 10 mail-in-1.lb.gradwell.net. You could check Gradwell's support pages, but I doubt there is an option to shut it off, since the DNS is published this way. It's a publication problem/feature, not a bug in dnsmasq. I do in fact have the ability to change my domain's zone files. ... and there is what you describe (N.B. this from a web form, not exact zone file syntax) :- * 195.74.61.9386400 A * 10 mail-in-1.lb.gradwell.net. 86400 MX So can I simply delete these two entries? (OK, people mis-typing domain names *might* be affected but that's mostly me so I don't see a big issue there) ... and the answer is yes. I've deleted the wild card lines from the form and now non-existent.isbd.net returns not found, excellent! Thanks for all the help here. -- Chris Green
Re: [Dnsmasq-discuss] dnsmasq returns addresses for non-existent hosts - what have I mis-configured?
On Sun, Nov 08, 2009 at 10:25:11AM -0500, Perette Barella wrote: It looks like your provider has set up a wildcard A record, which is similar to DNS hijacking as a helpful feature to users who miskey a domain name. It's not isolated to you: mugenshi:etc x10$ host ghijk.isbd.net ghijk.isbd.net has address 195.74.61.93 ghijk.isbd.net mail is handled by 10 mail-in-1.lb.gradwell.net. You could check Gradwell's support pages, but I doubt there is an option to shut it off, since the DNS is published this way. It's a publication problem/feature, not a bug in dnsmasq. I do in fact have the ability to change my domain's zone files. ... and there is what you describe (N.B. this from a web form, not exact zone file syntax) :- * 195.74.61.9386400 A * 10 mail-in-1.lb.gradwell.net. 86400 MX So can I simply delete these two entries? (OK, people mis-typing domain names *might* be affected but that's mostly me so I don't see a big issue there) -- Chris Green
[Dnsmasq-discuss] dnsmasq returns addresses for non-existent hosts - what have I mis-configured?
I have dnsmasq working quite happily on a Ubuntu Server 9.10 system providing dns for my small SoHo network. I have just noticed however that if I ask for the address of a non-existent name dnsmasq returns the name of one of my hosting service's machines. It always returns the same address for any non-existent name, e.g.:- chris$ host abcde.isbd.net abcde.isbd.net has address 195.74.61.93 abcde.isbd.net mail is handled by 10 mail-in-1.lb.gradwell.net. chris$ host xyz xyz.isbd.net has address 195.74.61.93 xyz.isbd.net mail is handled by 10 mail-in-1.lb.gradwell.net. chris$ host xyz.isbd.net xyz.isbd.net has address 195.74.61.93 xyz.isbd.net mail is handled by 10 mail-in-1.lb.gradwell.net. I have isbd.net and isbd.co.uk hosted at Gradwell so I do have a connection with them. In fact things are becoming clearer now, 195.74.61.93 is the (quite correct) address returned when you look up isbd.net. So, how can I prevent dnsmasq from returning the parent domain address when I look up anyOldRubbish.isbd.net ? Presumably it can't find the name locally and sends off the request to the upstream name server which (sort of correctly) returns 195.74.61.93. However it means that if I mis-type a name or if one of my machines dies then I may not notice immediately because DNS still succeeds. -- Chris Green
[Dnsmasq-discuss] Should I install resolvconf?
I just noticed that ubuntu says:- Suggested packages: resolvconf when I install dnsmasq. So, should I install resolvconf and will it do me any good? -- Chris Green
[Dnsmasq-discuss] Is it normal to need to edit /etc/hosts for dnsmasq
I have just moved my dnsmasq server from my desktop machine to a much lower powered machine so I can turn my desktop off and save some electricity. The new machine is called 'server' (original eh!) and has a static address of 192.168.1.2. It had a totally unmodified installation of Ubuntu Server 9.10 before I installed dnsmasq. Thus its /etc/hosts contained:- 127.0.0.1 localhost 127.0.1.1 server server.isbd.net # The following lines are desirable for IPv6 capable hosts ::1 localhost ip6-localhost ip6-loopback fe00::0 ip6-localnet ff00::0 ip6-mcastprefix ff02::1 ip6-allnodes ff02::2 ip6-allrouters ff02::3 ip6-allhosts Now this causes a problem - when asked for the address of 'server' it returns 127.0.1.1 which isn't correct as the client machine will think it itself is 'server'. I notice I fixed this before by changing the 127.0.1.1 to the actual IP address of the dnsmasq machine. Is this normally necessary? -- Chris Green
[Dnsmasq-discuss] Can dnsmasq 'alias' a host name?
Can dnsmasq provide an alternative name for a client? This is going on from my problem with a system that insists on calling itself garage.local when I want it to be called garage. Is there a way that I can tell dnsmasq that garage.local is also garage so that requests for the address of garage will get the address of garage.local? -- Chris Green
Re: [Dnsmasq-discuss] Can dnsmasq 'alias' a host name?
On Wed, Sep 02, 2009 at 05:51:15PM +0100, Simon Kelley wrote: Chris G wrote: Can dnsmasq provide an alternative name for a client? This is going on from my problem with a system that insists on calling itself garage.local when I want it to be called garage. Is there a way that I can tell dnsmasq that garage.local is also garage so that requests for the address of garage will get the address of garage.local? yes. cname=garage,garage.local should do it. It doesn't seem to work though. I have added the following to the end of /etc/dnsmasq.conf :- cname=garage,garage.local I have killed and restarted dnsmasq (it's still providing DNS OK). However I can't ping or ssh to garage, but I can ping and ssh to garage.local. -- Chris Green
Re: [Dnsmasq-discuss] Can dnsmasq 'alias' a host name?
On Wed, Sep 02, 2009 at 08:46:01PM +0100, Simon Kelley wrote: Chris G wrote: On Wed, Sep 02, 2009 at 05:51:15PM +0100, Simon Kelley wrote: Chris G wrote: Can dnsmasq provide an alternative name for a client? This is going on from my problem with a system that insists on calling itself garage.local when I want it to be called garage. Is there a way that I can tell dnsmasq that garage.local is also garage so that requests for the address of garage will get the address of garage.local? yes. cname=garage,garage.local should do it. It doesn't seem to work though. I have added the following to the end of /etc/dnsmasq.conf :- cname=garage,garage.local I have killed and restarted dnsmasq (it's still providing DNS OK). However I can't ping or ssh to garage, but I can ping and ssh to garage.local. The fact that this thing is putting .local on the end of its name suggests that is might be doing mDNS, and that the host you are testing it with is also configured to use mDNS as a name-resolution method. Since dnsmasq doesn't have anything to do with mDNS, it can't affect that. Some things to check: 1) /var/lib/misc/dnsmasq.leases. Does the garage.local name appear there, it will if the NAS is announcing that name in its DHCP requests. /var/lib/misc/dnsmasq.leases contains:- 1251924290 00:0b:5d:7f:56:e0 192.168.1.90 MAXLAPTOP 01:00:0b:5d:7f:56:e0 1251923804 00:01:e3:9d:8b:b5 192.168.1.129 C475IP * 1251923525 08:00:27:24:d0:9c 192.168.1.144 xp 01:08:00:27:24:d0:9c 1251922953 00:90:a9:70:06:ff 192.168.1.88 * 01:00:90:a9:70:06:ff 1251923251 00:e0:4c:c0:a9:60 192.168.1.89 lounge * 1251923827 00:50:8d:93:fd:09 192.168.1.83 maxine * That 192.168.1.88 is the garage system. 2) /etc/nsswitch.conf does mdns appear in the hosts: line? Yes:- hosts: files mdns4_minimal [NOTFOUND=return] dns mdns4 3) Try dig garage.local which just does a DNS query and doesn't try the other name-resolution methods. ; DiG 9.5.1-P2 garage.local ;; global options: printcmd ;; Got answer: ;; -HEADER- opcode: QUERY, status: NXDOMAIN, id: 10135 ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0 ;; QUESTION SECTION: ;garage.local. IN A ;; Query time: 0 msec ;; SERVER: 127.0.0.1#53(127.0.0.1) ;; WHEN: Wed Sep 2 20:49:35 2009 ;; MSG SIZE rcvd: 30 There are ways around this, but we need to know exactly what's going on first. Thanks for all the help so far. Yes, I think mDNS may be getting in the way. Turning it off is fine, especially if I can just persuade the garage system to be 'normal'! :-) The garage system has the following running:- 3817 root 1024 S /usr/bin/mDNSResponder -f /etc/mDNSResponder.conf 3818 root 1024 S /usr/bin/mDNSResponder -f /etc/mDNSResponder.conf 3819 root 1024 S /usr/bin/mDNSResponder -f /etc/mDNSResponder.conf -- Chris Green
Re: [Dnsmasq-discuss] Can dnsmasq 'alias' a host name?
On Wed, Sep 02, 2009 at 08:59:54PM +0100, Simon Kelley wrote: Chris G wrote: There are ways around this, but we need to know exactly what's going on first. Thanks for all the help so far. Yes, I think mDNS may be getting in the way. Turning it off is fine, especially if I can just persuade the garage system to be 'normal'! :-) The garage system has the following running:- 3817 root 1024 S /usr/bin/mDNSResponder -f /etc/mDNSResponder.conf 3818 root 1024 S /usr/bin/mDNSResponder -f /etc/mDNSResponder.conf 3819 root 1024 S /usr/bin/mDNSResponder -f /etc/mDNSResponder.conf Yes, that name is coming from mDNS, and not from the NAS announcing its name when it does DHCP. You need to stop using mDNS for name resolution (edit /etc/nsswitch.conf) and then, since the NAS doesn't tell dnsmasq its name, you need to tell dnsmasq that the host with MAC address 00:90:a9:70:06:ff is garage. It appears that just turning off mdns in the dnsmasq server system has done all I need! :-) I.e. I have changed:- hosts: files mdns4_minimal [NOTFOUND=return] dns mdns4 to:- hosts: files dns in /etc/nsswitch.conf and now the garage system is 'garage'. dhcp-host=00:90:a9:70:06:ff,garage you can remove the CNAME line too, it's not needed. Both currently commented out and, after a reboot, as I said garage is just garage. Brilliant, thank you! Will removing those mdns4_minimal and mdns4 entries from nsswitch.conf have done anything much, except making my system more unfriendly to Apple Macs and such? -- Chris Green
Re: [Dnsmasq-discuss] One client gets my domain name appended, another gets .local, why?
On Tue, Aug 25, 2009 at 05:44:33PM +0100, Chris G wrote: I have dnsmasq running with a fairly basic configuration but (among other things) it does have:- expand-hosts domain=isbd.net Two clients do as I expected and their host names have isbd.net appended:- maxine.isbd.net ether 00:50:8d:93:fd:09 Ceth0 C475IP.isbd.net ether 00:01:e3:9d:8b:b5 Ceth0 But one doesn't:- MyBookWorld.localether 00:90:a9:70:06:ff Ceth0 Can anyone explain why that one gets .local appended rather than .isbd.net and more to the point how can I fix it (apart from hard coding it somewhere)? MyBookWorld.local is a Western Digital NAS running some sort of Linux, I have command line root access to it but would prefer not to modify it if there's a better way to make it get the domain name. The MyBookWorld.local system does know it's on isbd.net because it's resolv.conf file has:- search isbd.net nameserver 192.168.1.4 No ideas anyone? I'm still stuck, I have changed the system's name to 'garage' now and have even managed to add a domain line to resolv.conf so it now has:- domain isbd.net search isbd.net nameserver 192.168.1.4 but the system *still* gets called garage.local by dnsmasq. Is there any way I can tell dnsmasq to simply force the name to 'garage' regardless of what it tells dnsmasq? I've just tried 'uname -a' on the system and that reports its name as garage.isbd.net so why dnsmasq thinks it's garage.local I don't know. In addition for some reason all the other systems on the network can be addressed as name.local as well as name.isbd.net, it's just the garage system that only works as .local. Help! -- Chris Green
[Dnsmasq-discuss] DHCP options, in particular setting default route
I'm pretty sure dnsmasq can do what I want but I'd just like to confirm the details of how to do it. I want dnsmasq to set default routes for DHCP clients, so I need to use --dhcp-option, so far so good. However the extra bit I'm not quite clear about is that I want to set different default routes for different clients. So I need something like:- --dhcp-option = network id,option:router, 192.168.1.1 for each client (or list of clients given by the network id) that needs to use default route 192.168.1.1. What I'm not quite clear about is what the network id looks like and/or if I need to set it myself using other dnsmasq arguments. Can someone elucidate this for me a little please. -- Chris Green
Re: [Dnsmasq-discuss] Strange (well, I can't udnerstand it) /etc/hosts effect
On Thu, Aug 13, 2009 at 04:17:17PM +0930, Karl Goetz wrote: On Wed, 12 Aug 2009 15:58:05 +0100 Chris G c...@isbd.net wrote: I run a fairly default version of dnsmasq on my xubuntu 9.04 Linux box so that I don't have to maintain losts of network (or hosts) configurations around our network. I have just added:- 127.0.0.1 www.google-analytics.com ssl.www.google-analytics.com to my /etc/hosts file. I'm not paranoid about snooping but I am fed up with having to wait for www.google-analytics.com to respond, it's often quite slow taking several seconds with the address displayed at the bottom of Firefox. Have you considered using address= in the configuration file? I have a short list of addresses I poison in that way, and some time ago (2-3 months?) on this list someone included instructions on an automatically updating list + apache rewrite to avoid nasty messages. Would that actually work any differently? I.e. does dnsmasq do anything different with an address= compared with an entry in /etc/hosts? So, it appears to work, but why does 'host' respond as follows:- chris$ host www.google-analytics.com www.google-analytics.com has address 127.0.0.1 www.google-analytics.com is an alias for www-google-analytics.l.google.com. www.google-analytics.com is an alias for www-google-analytics.l.google.com. Why don't the aliases disappear as well? -- Karl Goetz, (Kamping_Kaiser / VK5FOSS) Debian contributor / gNewSense Maintainer http://www.kgoetz.id.au No, I won't join your social networking group ___ Dnsmasq-discuss mailing list Dnsmasq-discuss@lists.thekelleys.org.uk http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss -- Chris Green
Re: [Dnsmasq-discuss] Strange (well, I can't udnerstand it) /etc/hosts effect
On Thu, Aug 13, 2009 at 04:17:17PM +0930, Karl Goetz wrote: On Wed, 12 Aug 2009 15:58:05 +0100 Chris G c...@isbd.net wrote: I run a fairly default version of dnsmasq on my xubuntu 9.04 Linux box so that I don't have to maintain losts of network (or hosts) configurations around our network. I have just added:- 127.0.0.1 www.google-analytics.com ssl.www.google-analytics.com to my /etc/hosts file. I'm not paranoid about snooping but I am fed up with having to wait for www.google-analytics.com to respond, it's often quite slow taking several seconds with the address displayed at the bottom of Firefox. Have you considered using address= in the configuration file? I have a short list of addresses I poison in that way, and some time ago (2-3 months?) on this list someone included instructions on an automatically updating list + apache rewrite to avoid nasty messages. I have added:- address=/www.google-analytics.com/127.0.0.1 to the end of /etc/dnsmasq.conf and done 'kill -SIGHUP ', no change, I still get the aliases appearing. -- Chris Green
Re: [Dnsmasq-discuss] Strange (well, I can't udnerstand it) /etc/hosts effect
On Thu, Aug 13, 2009 at 06:55:42AM -0400, richardvo...@gmail.com wrote: I have added:- address=/www.google-analytics.com/127.0.0.1 to the end of /etc/dnsmasq.conf and done 'kill -SIGHUP ', no change, I still get the aliases appearing. JD posted the appropriate excerpt from the man page, which includes the sentence: SIGHUP does NOT re-read the configuration file. Ah, I missed that, sorry! I have killed and re-started dnsmasq, now I *don't* get those aliases. Phew! :-) -- Chris Green
[Dnsmasq-discuss] Strange (well, I can't udnerstand it) /etc/hosts effect
I run a fairly default version of dnsmasq on my xubuntu 9.04 Linux box so that I don't have to maintain losts of network (or hosts) configurations around our network. I have just added:- 127.0.0.1 www.google-analytics.com ssl.www.google-analytics.com to my /etc/hosts file. I'm not paranoid about snooping but I am fed up with having to wait for www.google-analytics.com to respond, it's often quite slow taking several seconds with the address displayed at the bottom of Firefox. So, it appears to work, but why does 'host' respond as follows:- chris$ host www.google-analytics.com www.google-analytics.com has address 127.0.0.1 www.google-analytics.com is an alias for www-google-analytics.l.google.com. www.google-analytics.com is an alias for www-google-analytics.l.google.com. Why don't the aliases disappear as well? -- Chris Green
Re: [Dnsmasq-discuss] Strange (well, I can't udnerstand it) /etc/hosts effect
On Wed, Aug 12, 2009 at 01:30:20PM -0400, richardvo...@gmail.com wrote: On Wed, Aug 12, 2009 at 10:58 AM, Chris Gc...@isbd.net wrote: I run a fairly default version of dnsmasq on my xubuntu 9.04 Linux box so that I don't have to maintain losts of network (or hosts) configurations around our network. I have just added:- 127.0.0.1 www.google-analytics.com ssl.www.google-analytics.com to my /etc/hosts file. I'm not paranoid about snooping but I am fed up with having to wait for www.google-analytics.com to respond, it's often quite slow taking several seconds with the address displayed at the bottom of Firefox. So, it appears to work, but why does 'host' respond as follows:- chris$ host www.google-analytics.com www.google-analytics.com has address 127.0.0.1 www.google-analytics.com is an alias for www-google-analytics.l.google.com. www.google-analytics.com is an alias for www-google-analytics.l.google.com. Why don't the aliases disappear as well? Did you clear your cache? Whose cache? I restarted dnsmasq with a kill -1, is there anything else? -- Chris Green
[Dnsmasq-discuss] Re: can't resolve irc.freenode.org
On Thu, Apr 16, 2009 at 09:42:00AM -0500, Jon Nelson wrote: I ran into a wacky problem today, and it *seems* to be dnsmasq's fault. Assume (at least) 2 machines: a firewall (running dnsmasq) and any other machine in the network (pointed at the firewall for name resolution). On the firewall, 'host -v irc.freenode.org' results thusly: [snip result data from two machines] I just tried the same here on the machine that runs dnsmasq and then on another machine that uses the first machine as its DNS server. Both machines gave the same (correct) result. -- Chris Green
Re: [Dnsmasq-discuss] dnsmasq host being dhcp server to itself [WAS: Web hang ups after repeated access to one site - dnsmasq related?]
On Thu, Feb 19, 2009 at 01:53:46AM +, richardvo...@gmail.com wrote: Please keep replies on the list. On Wed, Feb 18, 2009 at 10:15 AM, Chris Green ch...@isbd.co.uk wrote: On Wed, Feb 18, 2009 at 01:50:08AM +, richardvo...@gmail.com wrote: [snip] No other configuration files needed -- on any host -- just let everybody use dhcp. Super easy. But will this work? No. dnsmasq determines which dhcp-range to use when giving out addresses from the IP address configured on the interface where the DHCP-REQUEST packet is received (or the interface address passed along by a dhcp-relay agent). As you can see this cannot possibly work to assign addresses to the dnsmasq box. There's no way around this because in general dnsmasq runs on your gateway which by definition has multiple interfaces. While I'm not sure about having a 'server' assign an IP to itself it's surely not true that in general dnsmasq runs on your gateway which by definition has multiple interfaces - in fact it's very often *not* true. I didn't say running on the gateway was an absolute necessity, I said it's the general (i.e. usual, common) case. Actually it is probably only the common case for configurations using dnsmasq for DHCP. I'm unconvinced! :-) It would be interesting to know how people here on the list use dnsmasq, is it on a Linux box that is the router (hence the default route) for the rest of the LAN or do they have a hardware ADSL (usually) router that does that. I'm quite willing to be wrong but I'd be surprised as I would expect a lot of people come to use dnsmasq the same way as me. I'd venture to guess that multiple dhcp-ranges (including dhcp-relay) is actually more common that your scenario. My situation is fairly typical I would have thought:- 192.168.1.1 - Draytek Vigor 2820n router, statically assigned IP 192.168.1.4 - Linux 'server' running dnsmasq, currently static 192.168.1.xxx - other systems/devices, DHCP from 192.16.1.4 The system running dnsmasq (192.168.1.4) has only one interface, on the local subnet, default route is set to 192.168.1.1 and it's *that* which has the multiple interfaces (two more going to the outside world in my case). Surely this is pretty common, a proprietary router which doesn't do DHCP as one wants it to, so put dnsmasq on an always on Linux box on the local LAN. I think more people use the always on Linux box as the router in that scenario, since if you want better DHCP than comes in the router you probably also want netfilter instead of what firewall comes in the router. As I said I'm quite happy to be wrong, but surprised. :-) In my case it's certainly true that there are No other configuration files needed, I just have /etc/hosts on 192.168.1.4 with the static addresses in it, /etc/resolv.conf with:- nameserver 127.0.0.1 nameserver 195.74.113.58 nameserver 195.74.113.62 ... and a pretty straightforward dsnmasq.conf file. Yes and now you have the additional problems of how to get dnsmasq to know its own host needs an address (broadcast packets usually aren't delivered to processes on the sender). Assigning the address directly via the kernel interfaces isn't feasible because (a) dnsmasq runs on many different OSes (b) dnsmasq drops root privilege that would be necessary to make an address assignment and (b2) interfaces can come up and down as media events are processed, tunnels are created, etc. In addition, allowing the IP address of the DHCP server to change is extremely bad because it breaks the renewal process. At some point Simon, the author, is going to wade into this discussion with about a dozen more reasons I haven't thought of. I wasn't suggesting that having dnsmasq assign the IP address to the system it's running on was either sensible or feasible, I certainly haven't attempted it and can't really see any good reason for doing so. As it is dnsmasq provides me with an easy to configure system (nearly everything is done in the 'server' system) and that's what I wanted. -- Chris Green
Re: [Dnsmasq-discuss] How to get name of DHCP'ed system?
On Fri, Jan 23, 2009 at 02:52:08PM -0800, Paul Chambers wrote: Fedora RPMs have located dnsmasq.leases in /var/lib/dnsmasq/ in the past. Don't know if they still are, more recently I've been building from Simon's tarballs to help test the latest releases. As to needing to write a script, don't most boxes have 'locate' available? (apart from embedded devices) Locate only works after the overnight update though, not much use after you've just installed dnsmasq. -- Paul -Original Message- From: dnsmasq-discuss-boun...@lists.thekelleys.org.uk [mailto:dnsmasq-discuss-boun...@lists.thekelleys.org.uk] On Behalf Of richardvo...@gmail.com Sent: Friday, January 23, 2009 9:55 AM To: psm...@gnu.org Cc: dnsmasq-discuss@lists.thekelleys.org.uk Subject: Re: [Dnsmasq-discuss] How to get name of DHCP'ed system? On Fri, Jan 23, 2009 at 11:23 AM, Paul Smith psm...@gnu.org wrote: On Fri, 2009-01-23 at 16:29 +, Chris G wrote: Where is dhcp.leases? I've looked in the obvious places and can't see it, a quick Google suggests it should be /var/dhcp.leases but I haven't got that. The file is actually called dnsmasq.leases (at least on the systems I have) and it's in /var/lib/misc. Sorry about that. I use the scripted external database so I don't have a leasefile at all, and didn't check before providing the information. The man page mentions two possible paths: /var/lib/misc/dnsmasq.leases /var/db/dnsmasq.leases Of course the path can be changed with the dhcp-leasefile option. Simon, the man entry for dhcp-leasefile is awfully confusing. Is that always a ISC dhcpd-compatible file, or only when old behavior is triggered by the lack of dhcp-range options? It does seem that there's a need for a simple utility to get these names though. You can write a little script to query the dnsmasq.leases file :-) ___ Dnsmasq-discuss mailing list Dnsmasq-discuss@lists.thekelleys.org.uk http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss -- Chris Green
Re: [Dnsmasq-discuss] How to get name of DHCP'ed system?
On Fri, Jan 23, 2009 at 08:27:00PM -0500, Cristóbal Palmer wrote: On Fri, Jan 23, 2009 at 7:09 PM, Chris G c...@isbd.net wrote: Locate only works after the overnight update though, not much use after you've just installed dnsmasq. See updatedb(1) [updatedb.slocate] - update the slocate database Surely that will take as long as 'find / -n name' anyway. -- Chris Green
Re: [Dnsmasq-discuss] How to get name of DHCP'ed system?
On Fri, Jan 23, 2009 at 12:18:48PM -0500, Paul Smith wrote: On Fri, 2009-01-23 at 16:29 +, Chris G wrote: Where is dhcp.leases? I've looked in the obvious places and can't see it, a quick Google suggests it should be /var/dhcp.leases but I haven't got that. The file is actually called dnsmasq.leases (at least on the systems I have) and it's in /var/lib/misc. Yes, thenk you, just exactly what I was after. :-) It does seem that there's a need for a simple utility to get these names though. You can write a little script to query the dnsmasq.leases file :-) Most definitely, though just knowing where the file is and what it's called is enough really. more /var/lib/misc/dnsmasq.leases does all I need. I need to add the above information to my little database of really useful notes. Thanks all. -- Chris Green
