Facebook
TwitterI have an instance set up on AWS everything is working fine except my DNS server. All domains work with external DNS servers pointing an A record at the AWS server. When telling a client domain to use our private nameservers the nameservers don't respond. testing client domains with intodns I get ERROR: One or more of your nameservers did not respond. Trying to do an NSLOOKUP for the client domains it never resolves an A record.
Not sure what im missing in my setup. What I think is happening is when a nameserver is being looked up for the client domain the DNS server can't be reached from the outside. Any help or suggestions or test to check would be appreciated.
Here is my setup
myhost.com registered at google domains
my custom nameservers
my glue records / registered host
My Route 53 DNS setup
AWS inbound rules
Client domain setup
Nameservers for clientdomain.com on registar
DNS on Plesk hosting
Here are a few checks I did
my named.conf settings
Not sure what im missing in my setup. What I think is happening is when a nameserver is being looked up for the client domain the DNS server can't be reached from the outside. Any help or suggestions or test to check would be appreciated.
Here is my setup
myhost.com registered at google domains
my custom nameservers
Code:
ns1.myhost.com
ns2.myhost.com
ns3.myhost.com
ns4.myhost.commy glue records / registered host
Code:
]ns1.myhost.com > xxx.xxx.xxx.119
ns2.myhost.com > xxx.xxx.xxx.107
ns3.myhost.com > xxx.xxx.xxx.55
ns4.myhost.com > xxx.xxx.xxx.252
Code:
myhost.com NS ns1.myhost.com
myhost.com NS ns2.myhost.com
myhost.com NS ns3.myhost.com
myhost.com NS ns4.myhost.com
ns1.myhost.com A xxx.xxx.xxx.119
ns2.myhost.com A xxx.xxx.xxx.107
ns3.myhost.com A xxx.xxx.xxx.55
ns4.myhost.com A xxx.xxx.xxx.252
myhost.com A xxx.xxx.xxx.151AWS inbound rules
Code:
Ports Protocol Source maw-pro
80 tcp 0.0.0.0/0, ::/0 ✔
8447 tcp 0.0.0.0/0, ::/0 ✔
995 tcp 0.0.0.0/0, ::/0 ✔
49152-65535 tcp 0.0.0.0/0, ::/0 ✔
8443 tcp 0.0.0.0/0, ::/0 ✔
143 tcp 0.0.0.0/0, ::/0 ✔
53 udp 0.0.0.0/0, ::/0 ✔
8880 tcp 0.0.0.0/0, ::/0 ✔
443 tcp 0.0.0.0/0, ::/0 ✔
110 tcp 0.0.0.0/0, ::/0 ✔
993 tcp 0.0.0.0/0, ::/0 ✔
22 tcp 0.0.0.0/0 ✔
21 tcp 0.0.0.0/0, ::/0 ✔
25 tcp 0.0.0.0/0, ::/0 ✔
53 tcp 0.0.0.0/0, ::/0 ✔
587 tcp 0.0.0.0/0, ::/0 ✔Client domain setup
Nameservers for clientdomain.com on registar
Code:
ns1.myhost.com
ns2.myhost.com
ns3.myhost.com
ns4.myhost.com
Code:
clientdomain.com A xxx.xxx.xxx.151
clientdomain.com NS ns1.myhost.com
clientdomain.com NS ns2.myhost.com
clientdomain.com NS ns3.myhost.com
clientdomain.com NS ns4.myhost.comHere are a few checks I did
Code:
[root@aws1 centos]# netstat -lnp | grep named
tcp 0 0 127.0.0.1:953 0.0.0.0:* LISTEN 3443/named
tcp 0 0 172.31.28.211:53 0.0.0.0:* LISTEN 3443/named
tcp 0 0 127.0.0.1:53 0.0.0.0:* LISTEN 3443/named
tcp6 0 0 :::53 :::* LISTEN 3443/named
udp 0 0 172.31.28.211:53 0.0.0.0:* 3443/named
udp 0 0 127.0.0.1:53 0.0.0.0:* 3443/named
udp6 0 0 :::53 :::* 3443/named
Code:
netstat -an | grep :53
tcp 0 0 172.31.28.211:53 0.0.0.0:* LISTEN
tcp 0 0 127.0.0.1:53 0.0.0.0:* LISTEN
tcp6 0 0 :::53 :::* LISTEN
udp 0 0 172.31.28.211:53 0.0.0.0:*
udp 0 0 127.0.0.1:53 0.0.0.0:*
udp6 0 0 :::53 :::*my named.conf settings
Code:
controls {
inet 127.0.0.1 port 953
allow { 127.0.0.1; } keys { "rndc-key"; };
};
zone "." {
type hint;
file "named.root";
};
zone "0.0.127.IN-ADDR.ARPA" {
type master;
file "localhost.rev";
};
