ISPC3 on port 8080

Discussion in 'ISPConfig 3 Priority Support' started by mrbronz, Dec 28, 2020.

  1. mrbronz

    mrbronz Member HowtoForge Supporter

    And this is from my registrars CP
    upload_2021-1-5_12-50-9.png
     
  2. Th0m

    Th0m ISPConfig Developer Staff Member ISPConfig Developer

    Then the nameserver change is still propagating.
     
  3. mrbronz

    mrbronz Member HowtoForge Supporter

    I have tried "dig @123.123.123.123 mydomain.com
    but it seems to time out, which suggests my external IP address cannot see my Nameservers
    I have an "A" record listed at my registrars CP for both my ns1 and ns2.
    Like I pointed out earlier (See above ^) that my registrars have put my name servers ns1.mydomain.com and ns2.mydomain.com as the main name servers.
    Could this be that my records are still not being resolved?
     
  4. mrbronz

    mrbronz Member HowtoForge Supporter

    After more than 3 days?
     
  5. Taleman

    Taleman Well-Known Member HowtoForge Supporter

    Use my DNS tutorial to test each name server you have separately, to see which of them have the A record and which do not.
    Then check what your domain registrar shows as authoritative name servers for you domain.
    It should not take longer than 48 hours to propagate the name service changes all around the world. Use Google name server, IP-address 8.8.8.8 to check, that usually takes less than an hour to update.
     
  6. Th0m

    Th0m ISPConfig Developer Staff Member ISPConfig Developer

    You shared your domain name before through PM. On query, I see the nameservers are still your providers nameservers and not your own.
     
  7. mrbronz

    mrbronz Member HowtoForge Supporter

    No I have changed them, as the image above shows
     
  8. Th0m

    Th0m ISPConfig Developer Staff Member ISPConfig Developer

    When looking up the nameservers, this is the output:
    Code:
    [email protected] ~ % dig ns example.com   
    
    ; <<>> DiG 9.10.6 <<>> ns example.com
    ;; global options: +cmd
    ;; Got answer:
    ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 38410
    ;; flags: qr rd ra; QUERY: 1, ANSWER: 3, AUTHORITY: 0, ADDITIONAL: 1
    
    ;; OPT PSEUDOSECTION:
    ; EDNS: version: 0, flags:; udp: 512
    ;; QUESTION SECTION:
    ;example.com.           IN   NS
    
    ;; ANSWER SECTION:
    example.com.       299   IN   NS   ns2.meganameservers.eu.
    example.com.       299   IN   NS   ns1.meganameservers.eu.
    example.com.       299   IN   NS   ns3.meganameservers.eu.
    
    ;; Query time: 174 msec
    ;; SERVER: 192.168.1.1#53(192.168.1.1)
    ;; WHEN: Tue Jan 05 16:10:02 CET 2021
    ;; MSG SIZE  rcvd: 114
     
  9. mrbronz

    mrbronz Member HowtoForge Supporter

    Yes, I've seen that and I cannot explain it or understand it?
     
  10. Th0m

    Th0m ISPConfig Developer Staff Member ISPConfig Developer

    So it is not changed. Contact your registrar to find out why.
     
    mrbronz likes this.
  11. mrbronz

    mrbronz Member HowtoForge Supporter

    Thank you that's what I was trying to understand
     
  12. mrbronz

    mrbronz Member HowtoForge Supporter

    I think I'm getting there...

    Two problems one problem wich was an absolutely stupid mistake on my behalf was that I had my routers firewall turned on.
    The second problem was that the Domain registrar was not correctly propagating my A records.
    Now when I do a dig command:-
    I guess I just need to be brave enough to replace my registrar Nameservers with my own.

    So the question is...
    When I switch nameservers at my registrar should I remove my "A" records with my registrar or leave them in place.
    My thoughts are to leave them as they are not going any harm (Will they be being used)?
     
  13. Th0m

    Th0m ISPConfig Developer Staff Member ISPConfig Developer

    I just did some tests and I can't reach your nameserver on the hostname/IP you sent earlier. Are you sure the firewall issue is fixed?
     
  14. mrbronz

    mrbronz Member HowtoForge Supporter

    Yes I did an external ping to ns1.mydomain.com and also managed an external "dig @123.123.123.123 mydomain.com any" all seems fine
    but also did a "dig @ns1.mydomain.com mydomain.com any" and get the following
    However, for ns2.mydomain.com I'm getting:-
    What have I missed or got wrong?

    [EDIT]
    After running
    Code:
    systemctl status bind9.service
    I'm getting...

     
  15. Taleman

    Taleman Well-Known Member HowtoForge Supporter

    You could start by examining that.
     
  16. Th0m

    Th0m ISPConfig Developer Staff Member ISPConfig Developer

    Which IP are you using for your queries?
     
  17. mrbronz

    mrbronz Member HowtoForge Supporter

    Thanks, Taleman
    I deleted the zone and recreated it and that solved that problem :)
     
  18. mrbronz

    mrbronz Member HowtoForge Supporter

    Using a phone app that is not connected to my local wifi (Termux)
    I can use either dig using my external IP 123.123.123.123 or ns1.mydomain.com or ns2.mydomain.com
    and it correctly gives me similar results
     
    Last edited: Jan 7, 2021
  19. mrbronz

    mrbronz Member HowtoForge Supporter

    Why is it when I do a dig from within my local network I get
     
  20. Th0m

    Th0m ISPConfig Developer Staff Member ISPConfig Developer

    Still not working here. I do see that ns1.example.com and ns2.example.com (example.com being your domain) are the same IP address, so it is not redundant at all. If your connection goes out, your DNS server(s) will be offline.
     

Share This Page