DNS configuration with bind
 

Hey folks,

I've recently switched from shared hosting for my website to dedicated hosting. Its kinda a big step and i'm quite excited about it. I have a pimary domain, burningwind.com, up and going through godaddy. I've gone through godaddy and changed the host setup to register my dns hosts, ns1.burningwind.com and ns2.burningwind.com, to use the ip addresses assigned to me by my hosting provider. A whois on burningwind.com shows that it has recognized the configuration change and is ready to go.

On the server side I'musing bind 9 and have the following configuration for the master zone setup of burningwind.com:
Its been several days and the domain still doesn't resolve. Can anyone see anything obviously wrong with my configuration? I also have a second domain that I would like to setup as well, but I'd like to get this resolved before I venture deeper. Any help or advise would be greatly appreciated.

~ Nick (snipersock@gmail.com)

A few side notes
 

A few notes to keep in mind.

My host provides me up to 5 ip addresses. The primary, .24, is the main ip of the machine. The other two, .168 and .169, are just pointers for the dns. While looking at this remember that all of this is taking place on the same machine. Sooner or later i'll have real secondary name servers, but for now its not critical to have the loss of uptime in case something happens.

Sooner or later I'll be putting up another domain, socklabs.com. When I go to configure that should I just use the burningwind.com nameserver pointers or setup an entire new zone for it?

~ Nick (snipersock@gmail.com)

There's no IN NS record for the root domain. When you created ns1.... IN NS what you're doing is saying "for the sub-domain ns1..., it's DNS server is ..."

You need to remove the ns1. and ns2. from in front of burningwind.com. and change the values from the IP address of the name server to the actual name. i.e. you need to switch the ns1... and ns2... to the right side of IN NS and have only burningwind.com. on the left side. Typically NS records are first in a zone file and as such you don't even need to put anything on the left side, since they'll automatically refer to the root domain in that case.

Thanks very much for that. Its working, sort of. I've got the mx record in place but can't connect to the mail server.
As you can see by http://www.dnsreport.com/tools/dnsre...urningwind.com , I get a 'Reverse DNS entries for MX records' error. Any ideas?

~ Nick (snipersock@gmail.com)

you need not be very concerned about it. If you do encounter a mailserver that dows reverse-dns checking ... your mails may be rejected by that domain.

The problem I have is that there are no PTS entries. What format do i use to create one?

~ Nick

I can connect to your mail server just fine.

Here's the DNS:
Here's connecting to the actual mail server:
In order to fix the reverse DNS error, you need to contact your ISP and ask them to change the PTR record for 198.87.87.24 like this: