[Dnsmasq-discuss] dnsmasq / dns server / iptables config glitch?

Adam Hardy adam.ant at cyberspaceroad.com
Tue Nov 24 11:31:44 GMT 2009


You're right. The result from netstat was:


tcp   0   0 127.0.0.1:3306   0.0.0.0:*  LISTEN 2557/mysqld

after changing the bindaddress config in the mysql config as per the docs to 
free up networking, it then gives this result:

adam at isengard:~$ sudo netstat -napt | grep 3306
tcp   0   0 127.0.1.1:3306    0.0.0.0:*       LISTEN      16473/mysqld
tcp   0   0 127.0.1.1:53067   127.0.1.1:3306  TIME_WAIT   -

which looks weird. But then it's probably just because I don't have much 
experience in this area. Why has it switched over to 127.0.1.1 ?

Thanks
Adam


Mark Beierl on 23/11/09 19:00, wrote:
> Silly thought but - is mysql configured to listen to 127.0.0.1 only? 
> Something like
> 
> sudo netstat -napt | grep 3306
> 
> ought to show if mysql is listening on 127.0.0.1:3306 or 0.0.0.0:3306.
> 
> Regards,
> Mark
> 
> Adam Hardy wrote:
>> Thought I had a simple problem but I don't really find anything 
>> relevant on the web and I'm not getting any responses to my questions 
>> here.
>>
>> Just a pointer in the right direction would be helpful - something to 
>> put me back on the scent?
>>
>> Thanks
>> Adam
>>
>> Adam Hardy on 20/11/09 20:38, wrote:
>>  
>>> I have a lan with a gateway machine running an ADSL modem and two 
>>> NICs with iptables and dnsmasq.
>>>
>>> It also runs mysql and tomcat but is currently just a simple gateway, 
>>> I'm not trying to configure any DMZ or fancier stuff like that.
>>>
>>> My problem is that I can access mysql using 'localhost:3306' but I 
>>> can't access it on the same box when using the machine name e.g. 
>>> 'isengard:3306' and my guess is that I have mis-configured either 
>>> dnsmasq or iptables.
>>>
>>> I figure that my command "mysql --host=isengard" is probably being 
>>> resolved as external and then getting blocked by the firewall.
>>>
>>> My dnsmasq config file, based on the example config but with comments 
>>> removed, is:
>>>
>>> domain-needed
>>> bogus-priv
>>> filterwin2k
>>> local=/localdomain/
>>> domain=localdomain
>>> dhcp-range=192.168.0.3,192.168.0.254
>>> dhcp-option=option:router,192.168.0.2
>>> dhcp-option=option:mtu,1500
>>>
>>> and my resolv.conf file is:
>>>
>>> nameserver 194.74.65.68
>>>
>>> and I think this is getting continually rewritten by dhcp with the 
>>> nameserver info from the dhcp server on the modem which gives the 
>>> outside NIC its internet ip address.
>>>
>>> Does this make any sense? Or rather does anyone see where my 
>>> situation is foobarred?
>>>     
>>
>>
>> _______________________________________________
>> Dnsmasq-discuss mailing list
>> Dnsmasq-discuss at lists.thekelleys.org.uk
>> http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss
>>   
> 




More information about the Dnsmasq-discuss mailing list