dnsmasq not starting from NetworkManager with SELinux enabled.

Some time back I posted on dnsmasq starting from Network Manager and how to setup dnsmasq.

Now, couple of days back , I setup dnsmasq in NetworkManager but was astonished to see that there was no dnsmasq running. I checked with dig and saw that there was no response from localhost for dns queries. Checked “ps -eaf|grep dns” and found that there was no dnsmasq running. I knew that once you mention “dns=dnsmasq” in the NetworkManager then it should start up but that was not happening. And then I checked audit log, found that some permissions were denied by SELinux.

dnsmasq – use with Network Manager.

Well if you have not heard about dnsmasq:

Dnsmasq is lightweight, easy to configure DNS forwarder and DHCP server.
It is designed to provide DNS and, optionally, DHCP, to a small network.
It can serve the names of local machines which are not in the global
DNS. The DHCP server integrates with the DNS server and allows machines
with DHCP-allocated addresses to appear in the DNS with names configured
either in each host or in a central configuration file. Dnsmasq supports
static and dynamic DHCP leases and BOOTP for network booting of diskless
machines.

Continue reading

dnstop – top like utility for Fedora and other *nix

For installation :

sudo yum install dnstop

And now some description:

dnstop is a libpcap application (ala tcpdump) that displays various
tables of DNS traffic on your network.

dnstop supports both IPv4 and IPv6 addresses.

To help find especially undesirable DNS queries, dnstop provides a
number of filters.

dnstop can either read packets from the live capture device, or from a
tcpdump savefile.

Couple of days back, I realized there was too much network activity on my
system, although I was not doing anything. Fired up wireshark and to my
astonishment, there was too much of DNS traffic on the network. But the
problem was analyzing the data in wireshark and this is where dnstop came
into light. It helped me narrow down the issue within minutes and problems
resolved.

\[Solution\] Solaris issue with wget not resolving Domain name (DNS name lookup failure)

Today I was working with <a class="zem_slink" title="Solaris (operating system)" rel="homepage" href="http://oracle.com/solaris">Solaris and after I had set up the <a class="zem_slink" title="NIS+" rel="wikipedia" href="http://en.wikipedia.org/wiki/NIS%2B">NIS+, <a class="zem_slink" title="Name server" rel="wikipedia" href="http://en.wikipedia.org/wiki/Name_server">DNS server, IP Address and completing the basic setting. I was using the pkg-get util from the freesunware.com

The utility was using wget and it was failing constantly. From the looks of it, it was very clear that the wget utility was unable to find the <a class="zem_slink" title="IP address" rel="wikipedia" href="http://en.wikipedia.org/wiki/IP_address">IP address from the name. <a class="zem_slink" title="Name resolution" rel="wikipedia" href="http://en.wikipedia.org/wiki/Name_resolution">Name resolution was not happening, while dig and <a class="zem_slink" title="Nslookup" rel="wikipedia" href="http://en.wikipedia.org/wiki/Nslookup">nslookup was able to do the DNS lookup.

Afraid Dynamic DNS client in Fedora with Email indicating the changed to original IP.

If you have your domain in the Dynamic DNS located at : <a href="http://freedns.afraid.org">Freedns then you know how difficult it is to get the Dynamic DNS client to work with Fedora. Not that it does not work, but you need to configure it properly and there are lot of parameters. But not any more. Now you can install the afraid Dynamic DNS client and just put your Account Hash in the config file and you are ready with the setup to update the DNS entry whenever your IP changes. So lets get started: