Dnsmasq and Named in Ubuntu10.10 may conflict

Ubuntu10.10 of my server version. A dnsmasq is installed. You cannot get up. After sudo/etc/init. d/dnsmasqrestart, the system prompts dnsmasq: failedtocreatelisteningsocket: Addressalreadyinuse [fail]. Later, we checked the English article. dnsmasq and other dns resolution services use port 53. Sudonetstat

I use the server version of Ubuntu 10.10.

A dnsmasq is installed. You cannot get up. Sudo/etc/init. d/dnsmasq restart
After
Prompt dnsmasq: failed to create listening socket: Address already in use [fail]

Later I checked the article in English. dnsmasq and other dns resolution services use port 53.

Sudo netstat-anlp | grep-w LISTEN

Check that port 53 is occupied by named. However, I want to use dnsmasq on my own machine and start another dns resolution service program. [LINUX community www.LinuxIDC.com]

You can use port binding. The/etc/dnsmasq. conf file is described in.

# On systems which support it, dnsmasq binds the wildcard address,
# Even when it is listening on only some interfaces. It then discards
# Requests that it shouldn't reply to. This has the advantage
# Working even when interfaces come and go and change address. If you
# Want dnsmasq to really bind only the interfaces it is listening on,
# Uncomment this option. About the only time you may need this is when
# Running another nameserver on the same machine.
Bind-interfaces

This line of bind-interfaces had a well number before, and the well number was saved. Restart dnsmasq. I added a 127.0.0.2 address to the lo port of my local machine. The listening address is bound to 127.0.0.2. He always prompts me that port 127.0.0.1 is occupied.
Listen-address = 127.0.0.2
In this way, the resolv. conf and dhclient. conf are also relatively changed, and then it will be okay.