On 8/1/2014 7:48 PM, /dev/rob0 wrote:
On Fri, Aug 01, 2014 at 07:01:09PM +0430, Mahmood Naderan wrote:
However, I get error when trying to start the dnsmasq service

|     [root@localhost mahmood]# /etc/init.d/dnsmasq status
     dnsmasq is stopped
     [root@localhost mahmood]# /etc/init.d/dnsmasq start
     Starting dnsmasq:
     dnsmasq: failed to create listening socket: Address already in use
                                                        [FAILED]
|

netstat command shows the following information

|     [root@localhost mahmood]# netstat -anlp | grep -w LISTEN
"LISTEN" in netstat terms only includes TCP, as you can see.  DHCP
servers need to bind UDP port 68.  Nameservers need to bind UDP 53.
More of interest here would be to see UDP sockets (-u).

     tcp        0      0 0.0.0.0:111                 0.0.0.0:*                  
 LISTEN      1252/rpcbind
     tcp        0      0 127.0.0.1:631               0.0.0.0:*                  
 LISTEN      1445/cupsd
     tcp        0      0 127.0.0.1:25                0.0.0.0:*                  
 LISTEN      1685/master
     tcp        0      0 0.0.0.0:46556               0.0.0.0:*                  
 LISTEN      1348/rpc.statd
     tcp        0      0 :::111                      :::*                       
 LISTEN      1252/rpcbind
     tcp        0      0 :::80                       :::*                       
 LISTEN      4884/httpd
     tcp        0      0 ::1:631                     :::*                       
 LISTEN      1445/cupsd
     tcp        0      0 :::51096                    :::*                       
 LISTEN      1348/rpc.statd
|

What missconfiguration causes such error and how can I fix that?
I don't know.  Maybe you have enabled another DHCP server, or perhaps
another nameserver?


Yes, seems that I enabled the tftp in xinet.conf.
I now disable it and it works.

Regards,
Mahmood


_______________________________________________
Dnsmasq-discuss mailing list
[email protected]
http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss

Reply via email to