[fredreload]

I'm new to using bind and trying to get it to run in windows XP. For some reason named.exe crashes when I start the service giving me a 1067 error. The bind version I have is BIND9.9.0a3. The following occurs when executing the named -g command and named.exe crashes right after listening on ipv4 interface. The same thing happened when I try to run bind on a different windows 7 machine. Is there a way to stop named.exe from crashing?

C:\WINDOWS\system32\dns\bin>named -g
2011 07:40:36.140 starting BIND 9.9.0a3 -g
2011 07:40:36.140 built with default
2011 07:40:36.140 found 8 CPUs, using 8 worker threads
2011 07:40:36.140 loading configuration from 'C:\WINDOWS\system32\dns\et
c\named.conf'
2011 07:40:36.140 using default UDP/IPv4 port range: [1024, 65535]
2011 07:40:36.140 using default UDP/IPv6 port range: [1024, 65535]
2011 07:40:36.140 no IPv6 interfaces found
2011 07:40:36.140 listening on IPv4 interface PPP Interface 1, 114.25.14
9.168#53

[fredreload]

I switched to Ubuntu with the following files.

File: named.conf.local

zone "fredreload.com"
{
        type master;
        file "/etc/bind/zones/fredreload.com.db";
};

zone "0.0.127.in-addr.arpa"
{
        type master;
        file "rev.0.0.127.in-addr.arpa";
};

File: fredreload.com.db

$TTL 3D
@ IN SOA fred.fredreload.com. admin.fredreload.com. (
2011102601;
28800;
3600;
604800;
38400
);

fredreload.com. IN      A       127.0.0.1
www             IN      A       127.0.0.1

File: rev.0.0.127.in-addr.arpa

TTL 3D
@ IN SOA fredreload.com. admin.fredreload.com. (
2011102601;
28800;
604800;
604800;
86400
);

@                IN      NS      fredreload.com.

File: resolv.conf

search fredreload.com.
nameserver 127.0.0.1

Started Bind and did "nslookup fredreload.com" but received a servfail.

Server: 127.0.0.1
Address: 127.0.0.1#53

server can't find fredreload.com.fredreload.com: SERVFAIL

What changes should I make?

[CaptPikel]

Try "nslookup fredreload.com." for the query. Nslookup uses the Search feature and appends the domain suffix to the end by default. Use dig if you can to test. But the main issue is that you have no NS records for the fredreload.com zone. Add those and you should be ok.

[fredreload]

Thanks for the reply, but I still received SERVFAIL from "nslookup fredreload.com."

Server: 127.0.0.1
Address: 127.0.0.1#53

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

Is there other changes I should make? I'll check for other examples over the weekend.

[CaptPikel]

Did you add those NS records and reload the domain? If those are missing, you will get SERVFAIL's. If a zone has no NS records, it will fail to even load. You can see that in the logs (usually /var/log/messages).

[fredreload]

I set the NS record to 127.0.0.1 and did "nslookup" but received no answer.

nslookup fredreload.com.

Server: 127.0.0.1
Address: 127.0.0.1#53

*** Can't find fredreload.com.: No answer

[CaptPikel]

What does the fredreload.com.db file look like now?

[fredreload]

My bad, I think I'll take some time to look over it first.