Bind not running on all interfaces

Discussion in 'Installation/Configuration' started by Jim Locke, Oct 24, 2025.

  1. Jim Locke

    Jim Locke Member

    Fresh multiserver setup on 24.04
    When I changed firewall nat rule to send 53 (tcp/udp) to new ns2 server I get no responses, ns1 responds properly
    set firewall nat rule back to old ns2, all good
    ssh into panel and use dig & nslookups for tests against both ns1 & ns2 all good
    ssh into ns2 ping outside sites, all good, checked network/gateways etc not seeing an issue
    Lots of digging and found a command that is on the right track (ss -lptn > bind.log 2>&1) output of ns1 and ns2 attached:

    The question is how to I fix it?
    Jim..
     

    Attached Files:

  2. pyte

    pyte Well-Known Member HowtoForge Supporter

    It is very confusing that in out output both systems are called ns2.
    Anyways on the 2nd run of the command, there is no bind service running at all on the system.
    Check the service itself with "systemctl status bind".
     
  3. Jim Locke

    Jim Locke Member

    the 1st was ns1 i must have not clipped the prompt, i did manage to get ns2 running but still having issues. systemctl status bind9 giving different results, tried resync and that didn't fix it.Tempted to redo ns2 from scratch but not sure if ispc will like that. Thinking that if i put both old ns's back into prod, clear out all dns records in the new (thru ispc), rebuild ns2, add records, then switch back new into prod.
     

Share This Page