Mydns-ng problem, port 53 already in use.

Discussion in 'Installation/Configuration' started by jerek, Mar 13, 2009.

  1. jerek

    jerek New Member

    Hi to all peeps around ,ive been fighting with this problem now around 20 hours and i cant manage this alone, coz i am linux newbie

    So i reinstalled vps 2 times in row coz this problem. i followed the installation instructions for ispconfig 3 etc. Problem is that i uninstalled bind9 + killed the process and then reboot. after that i installed mydns but still this problem exists. I would be nice if someone of you gurus would lookthis and give some hints. :p .


    It wont update nameserver records at all and dnscheck fails.



    edit:
    System is ubuntu 8.0.4.2

    mydns -v
    then ps -A

    Code:
    [QUOTE]ps -A
      PID TTY          TIME CMD
        1 ?        00:00:00 init
    12021 ?        00:00:00 syslogd
    12052 ?        00:00:00 sshd
    12090 ?        00:00:01 amavisd-new
    12123 ?        00:00:00 mysqld_safe
    12165 ?        00:00:00 mysqld
    12167 ?        00:00:00 logger
    12173 ?        00:00:00 amavisd-new
    12174 ?        00:00:00 amavisd-new
    12243 ?        00:00:02 spamd
    12270 ?        00:00:00 courierlogger
    12271 ?        00:00:00 authdaemond
    12272 ?        00:00:00 authdaemond
    12273 ?        00:00:00 authdaemond
    12274 ?        00:00:00 authdaemond
    13313 ?        00:00:00 courierlogger
    13314 ?        00:00:00 couriertcpd
    13334 ?        00:00:00 courierlogger
    13335 ?        00:00:00 couriertcpd
    13336 ?        00:00:00 authdaemond
    13337 ?        00:00:00 authdaemond
    13350 ?        00:00:00 courierlogger
    13351 ?        00:00:00 couriertcpd
    13370 ?        00:00:00 courierlogger
    13371 ?        00:00:00 couriertcpd
    13375 ?        00:00:00 mydns
    13388 ?        00:00:00 mydns
    13442 ?        00:00:00 master
    13444 ?        00:00:00 qmgr
    13445 ?        00:00:00 pickup
    13464 ?        00:00:00 spamd
    13465 ?        00:00:00 spamd
    13466 ?        00:00:00 nmbd
    13468 ?        00:00:00 smbd
    13490 ?        00:00:00 smbd
    13494 ?        00:00:00 saslauthd
    13495 ?        00:00:00 saslauthd
    13496 ?        00:00:00 saslauthd
    13497 ?        00:00:00 saslauthd
    13498 ?        00:00:00 saslauthd
    13513 ?        00:00:00 xinetd
    13648 ?        00:00:00 proftpd
    13662 ?        00:00:00 atd
    13673 ?        00:00:00 cron
    13697 ?        00:00:00 apache2
    13708 ?        00:00:00 sh
    13709 ?        00:00:00 vlogger
    13715 ?        00:00:01 fail2ban-server
    13717 ?        00:00:00 apache2
    13896 ?        00:00:00 tlsmgr
    14041 ?        00:00:00 sshd
    14115 pts/0    00:00:00 bash
    15516 ?        00:00:00 apache2
    19765 ?        00:00:00 smtpd
    19767 ?        00:00:00 anvil
    19799 pts/0    00:00:00 ps
    [/QUOTE]
    And for some netstat -tap &
     
    Last edited: Jul 24, 2010
  2. jerek

    jerek New Member

    Well into dns shows this kind of messages when trying to dnscheck :/

    Omg,i am so stupid...
    :)

    well problem was badly configured dns records,

    Remember peeps to use dig : dig @localhost NS example.org

    mine dig for ns was this:

    dig @localhost NS *.org

    and correct one is this :

     
    Last edited: Feb 12, 2010

Share This Page