Self DNS server, SERVFAIL

[neyder]

I just installed VestaCP on AWS instance with VirtualPrivateCloud, when i follow the guide to setup own nameserver http://vestacp.com/docs/#how-to-setup-v ... ameservers it doesn't work, I followed all steps, wait for propagation, but even when I test with nslookup in the aws instance allways got SERVFAIL.

Code: Select all

ubuntu@maya:~⟫ nslookup neyder.com
Server:         172.30.0.2
Address:        172.30.0.2#53

Non-authoritative answer:
Name:   neyder.com
Address: 52.32.175.25

ubuntu@maya:~⟫ nslookup neyder.net
Server:         172.30.0.2
Address:        172.30.0.2#53

Non-authoritative answer:
Name:   neyder.net
Address: 104.168.169.164

ubuntu@maya:~⟫ nslookup lainmaculada.edu.pe
Server:         172.30.0.2
Address:        172.30.0.2#53

Non-authoritative answer:
Name:   lainmaculada.edu.pe
Address: 162.221.184.28

ubuntu@maya:~⟫ nslookup vicentinos.edu.pe
Server:         172.30.0.2
Address:        172.30.0.2#53

** server can't find vicentinos.edu.pe: SERVFAIL

1 ubuntu@maya:~⟫ nslookup neyder.com 52.32.175.25
Server:         52.32.175.25
Address:        52.32.175.25#53

** server can't find neyder.com: SERVFAIL

1 ubuntu@maya:~⟫ 

this is ipconfig:

Code: Select all

1 ubuntu@maya:~⟫ ifconfig 
eth0      Link encap:Ethernet  HWaddr 02:b2:90:8c:19:5f  
          inet addr:172.30.1.243  Bcast:172.30.1.255  Mask:255.255.255.0
          inet6 addr: fe80::b2:90ff:fe8c:195f/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:9001  Metric:1
          RX packets:8079 errors:0 dropped:0 overruns:0 frame:0
          TX packets:7697 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:611679 (611.6 KB)  TX bytes:2302262 (2.3 MB)

lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:65536  Metric:1
          RX packets:110 errors:0 dropped:0 overruns:0 frame:0
          TX packets:110 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:46590 (46.5 KB)  TX bytes:46590 (46.5 KB)

I got Elastic IP from AWS which is 52.32.175.25, as shown here:


hosting imagenes

Hope this more help you to help me:

Code: Select all

ubuntu@maya:~⟫ sudo ps -ef| grep named                                          
ubuntu    3049  2628  0 04:48 pts/2    00:00:00 grep --color=auto named
bind     21681     1  0 04:12 ?        00:00:00 /usr/sbin/named -u bind
ubuntu@maya:~⟫ sudo named-checkconf -z
zone localhost/IN: loaded serial 2
zone 127.in-addr.arpa/IN: loaded serial 1
zone 0.in-addr.arpa/IN: loaded serial 1
zone 255.in-addr.arpa/IN: loaded serial 1
zone neyder.com/IN: 'neyder.com' found SPF/TXT record but no SPF/SPF record found, add matching type SPF record
zone neyder.com/IN: loaded serial 2016042907
zone vicentinos.edu.pe/IN: 'vicentinos.edu.pe' found SPF/TXT record but no SPF/SPF record found, add matching type SPF record
zone vicentinos.edu.pe/IN: loaded serial 2016042903

[ttcttctw]

I have the same problem too, still not found any solution yet.

[SS88]

What is your name.conf file?

Looking up the domain, right now I get:

WARNING: Couldn't connect using TCP protocol:
tcp4:52.32.175.25
Check your name server's configurations and firewall rules. When response to a DNS query exceeds 512 bytes, TCP is negotiated and used, all name servers should allow TCP connections (port 53).