Fedora – dnsmasq with NetworkManager

I have been thinking of writing about this for long time but someone else did and it is nice write-up so here is the link – https://fedoramagazine.org/using-the-networkmanagers-dnsmasq-plugin/

DNS – simple and effective guide with history

Here is link to a very nice and definitive guide to DNS. Very detailed and useful. There is a pdf version as well to download 🙂

https://webhostinggeeks.com/guides/dns/

Thanks to Andrijana Nikolic for providing a valuable resource to share with you all.

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

\[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.

Solved -- Errors with afraid-dyndns in Goddard (Fedora 13)

Since I updated to the <a class="zem_slink freebase/en/fedora" title="Fedora" rel="homepage" href="http://fedoraproject.org/">Fedora 13, I was getting error from the <a class="zem_slink freebase/en/dynamic_dns" title="Dynamic DNS" rel="wikipedia" href="http://en.wikipedia.org/wiki/Dynamic_DNS">Dynamic DNS client for afraid. I was not getting enough time to fix this, so finally I decided to fix this in the night itself 🙂

Problem:
On running

afraid-dyndns

I was getting the error:

Entity: line 100: <a class="zem_slink freebase/en/parsing" title="Parsing" rel="wikipedia" href="http://en.wikipedia.org/wiki/Parsing">parser error : Opening and ending tag mismatch: br line 99 and div

Continue reading

Local DNS Server for faster DNS response time

Here&#8217;s a quick tip for faster DNS response time. I installed a local DNS server which can contact the remote DNS server and enabled caching for the local DNS server. This ensures that the response time for the DNS queries is much faster.

I am on Fedora 10, so here&#8217;s what I was required to do:

yum install dnsmasq

After this I created a file called /etc/resolve.dns with the nameserver address&#8217;s and heres what it looks like: