Unable to use DirectAdmin servers name servers

M

meisamsadraei

New member
Joined
Feb 5, 2021
Messages
3
Hi

MY namservers aren't working. I configured the domains NameServers to the IP address of the server DirectAdmin has the IP of but its just not working
This domain is entekhabekala.ir
Capture.PNG
named.jpg
 
You need to add the IP's to the (nsX.) nameservers at your domain registrar eg. normally called child nameservers
 
The records at your registrar seem to work, that part is fine. It looks like a local problem.
Port 53 is open and reachable.
Check this:

intoDNS: entekhabekala.ir - check DNS server and mail server health

intoDNS: Checking health and configurtion of DNS server and mail server for domainentekhabekala.ir.
intodns.com intodns.com

At this moment I don't know why it's giving this failure. Port 53 is reachable. Try this.
In /etc/resolv.conf change
Code: 
        listen-on port 53 { 127.0.0.1; };
        listen-on-v6 port 53 { ::1; };
to this:
Code: 
        //listen-on port 53 { 127.0.0.1; };
        //listen-on-v6 port 53 { ::1; };

Do the same with the "allow-query". The bind default is fine.
and restart named.
It should still be listening to port 53.

This is what I use on all my servers, created by DA itself. You can also use this.
Code: 
options {
        allow-transfer {"none";};
        //listen-on port 53 { 127.0.0.1; };
        //listen-on-v6 port 53 { ::1; };
        directory       "/var/named";
        dump-file       "/var/named/data/cache_dump.db";
        statistics-file "/var/named/data/named_stats.txt";
        memstatistics-file "/var/named/data/named_mem_stats.txt";
        secroots-file   "/var/named/data/named.secroots";
        recursing-file  "/var/named/data/named.recursing";
        //allow-query     { localhost; };
        allow-recursion { localnets; };
Don't forget to restart named.

Anyway, it's not really good to only use 1 ip for nameservers. It's best to use 2 different ip's and even like should be, on different servers or vps systems.
 
Richard G said:
The records at your registrar seem to work, that part is fine. It looks like a local problem.
Port 53 is open and reachable.
Check this:

intoDNS: entekhabekala.ir - check DNS server and mail server health

intoDNS: Checking health and configurtion of DNS server and mail server for domainentekhabekala.ir.
intodns.com intodns.com

At this moment I don't know why it's giving this failure. Port 53 is reachable. Try this.
In /etc/resolv.conf change
Code: 
        listen-on port 53 { 127.0.0.1; };
        listen-on-v6 port 53 { ::1; };
to this:
Code: 
        //listen-on port 53 { 127.0.0.1; };
        //listen-on-v6 port 53 { ::1; };

Do the same with the "allow-query". The bind default is fine.
and restart named.
It should still be listening to port 53.

This is what I use on all my servers, created by DA itself. You can also use this.
Code: 
options {
        allow-transfer {"none";};
        //listen-on port 53 { 127.0.0.1; };
        //listen-on-v6 port 53 { ::1; };
        directory       "/var/named";
        dump-file       "/var/named/data/cache_dump.db";
        statistics-file "/var/named/data/named_stats.txt";
        memstatistics-file "/var/named/data/named_mem_stats.txt";
        secroots-file   "/var/named/data/named.secroots";
        recursing-file  "/var/named/data/named.recursing";
        //allow-query     { localhost; };
        allow-recursion { localnets; };
Don't forget to restart named.

Anyway, it's not really good to only use 1 ip for nameservers. It's best to use 2 different ip's and even like should be, on different servers or vps systems.
Click to expand...
I think isp tried to configured NAT-based network for VPS or bridged-network to give a real IP and it failed.
 
Richard G said:
The records at your registrar seem to work, that part is fine. It looks like a local problem.
Port 53 is open and reachable.
Check this:

intoDNS: entekhabekala.ir - check DNS server and mail server health

intoDNS: Checking health and configurtion of DNS server and mail server for domainentekhabekala.ir.
intodns.com intodns.com

At this moment I don't know why it's giving this failure. Port 53 is reachable. Try this.
In /etc/resolv.conf change
Code: 
        listen-on port 53 { 127.0.0.1; };
        listen-on-v6 port 53 { ::1; };
to this:
Code: 
        //listen-on port 53 { 127.0.0.1; };
        //listen-on-v6 port 53 { ::1; };

Do the same with the "allow-query". The bind default is fine.
and restart named.
It should still be listening to port 53.

This is what I use on all my servers, created by DA itself. You can also use this.
Code: 
options {
        allow-transfer {"none";};
        //listen-on port 53 { 127.0.0.1; };
        //listen-on-v6 port 53 { ::1; };
        directory       "/var/named";
        dump-file       "/var/named/data/cache_dump.db";
        statistics-file "/var/named/data/named_stats.txt";
        memstatistics-file "/var/named/data/named_mem_stats.txt";
        secroots-file   "/var/named/data/named.secroots";
        recursing-file  "/var/named/data/named.recursing";
        //allow-query     { localhost; };
        allow-recursion { localnets; };
Don't forget to restart named.

Anyway, it's not really good to only use 1 ip for nameservers. It's best to use 2 different ip's and even like should be, on different servers or vps systems.
Click to expand...
i tried this but doesnt work for me :(

//
// named.conf
//
// Provided by Red Hat bind package to configure the ISC BIND named(8) DNS
// server as a caching only nameserver (as a localhost DNS resolver only).
//
// See /usr/share/doc/bind*/sample/ for example named configuration files.
//
//acl trusted { 127.0.0.1; }; //-added
options {
allow-transfer { none; };
//listen-on port 53 { any; };
//listen-on port 53 { 192.168.1.193; }; //-added
//listen-on port 53 { 192.168.1.140; }; //-added
//listen-on-v6 port 53 { ::1; };
directory "/var/named";
dump-file "/var/named/data/cache_dump.db";
statistics-file "/var/named/data/named_stats.txt";
memstatistics-file "/var/named/data/named_mem_stats.txt";
secroots-file "/var/named/data/named.secroots";
recursing-file "/var/named/data/named.recursing";
//allow-notify { trusted; }; //-added
//allow-query { any; };
allow-recursion { localnets; };
/*
Click to expand...

but still having issues with letsencrypt

+ echo 'Challenge pre-checks for http://mydomain.com/.well-known/acme-challenge/letsencrypt_1617087548_a80890b63fda0d2a failed... Command:'
Challenge pre-checks for http://mydomain.com/.well-known/acme-challenge/letsencrypt_1617087548_a80890b63fda0d2a failed... Command:
+ echo '/usr/bin/curl --connect-timeout 40 -k --silent --resolve mydomain.com:80:108.170.38.197 --resolve cht1077.com:443:mainserverip -I -L -X GET http://cht1077.com/.well-known/acme-challenge/letsencrypt_1617087548_a80890b63fda0d2a'
/usr/bin/curl --connect-timeout 40 -k --silent --resolve cht1077.com:80:mainserverip --resolve cht1077.com:443:mainserverip -I -L -X GET http://cht1077.com/.well-known/acme-challenge/letsencrypt_1617087548_a80890b63fda0d2a
+ echo Exiting.
Exiting.
+ rm -f /var/www/html/.well-known/acme-challenge/letsencrypt_1617087548_a80890b63fda0d2a
Click to expand...
 
You must log in or register to reply here.
Back
Top