BIND DNS SERVFAIL ERROR

binddomain-name-systemwindows-vista

I am attempting to setup a bind DNS server for use with a domain I recently registered using No-IP. I registered my DNS server with No-IP using ns1.mydomain.net and ns2.mydomain.net pointing to the exact same IP because I only have one IP to point it to. Then in my db.mydomain.net.txt zone file I put this

$TTL 6h
$ORIGIN mydomain.net.
@   IN SOA  ns1.mydomain.net.   hostmaster.mydomain.net. (
        2014062101
        10800
        3600
        604800
        86400 )

@   IN SOA  ns2.mydomain.net.   hostmaster.mydomain.net. (
        2014062102
        10800
        3600
        604800
        86400 )         
IN  NS  ns1.mydomain.net.
IN  NS  ns2.mydomain.net.
ns1 IN  A   1.2.3.4
ns2 IN  A   1.2.3.4
@   IN  A       1.2.3.4
scoopta   IN  A 1.2.3.4
files     IN  A     1.2.3.4

My goal is to setup two subdomains not including ns1 and ns2. Those being scoopta.mydomain.net and files.mydomain.net. However it doesn't work and whenever I do

nslookup mydomain.net

I get a SERVERROR and it doesn't work. I've never used bind before so I honestly have no clue what I'm doing. Thanks. As a disclaimer I do have port 53 TCP and UDP open on my router and I have used http://canyouseeme.org to check if the server is accessible and it is. It's something with my configuration I'm sure.

Best Answer

You can only have one SOA record in a zone file. Remove the second SOA record.

$TTL 6h
$ORIGIN mydomain.net.
@   IN SOA  ns1.mydomain.net.   hostmaster.mydomain.net. (
        2014062101
        10800
        3600
        604800
        86400 )        
IN  NS  ns1.mydomain.net.
IN  NS  ns2.mydomain.net.
ns1 IN  A   1.2.3.4
ns2 IN  A   1.2.3.4
@   IN  A       1.2.3.4
scoopta   IN  A 1.2.3.4
files     IN  A     1.2.3.4
Related Topic