Error: 500 Can't connect to bartruff.net:80 (Bad hostname 'bartruff.net')

I am a beginner at system administration and am trying to set up my dns server on MS Windows Server 2003.

If I enter the ip address: http://66.134.64.146/ in the wtc.org link checker, I get a page.

If I use the urls http://www.bartruff.net/ or http://bartruff.net/ in the wtc.org link checker, I get the error "Error: 500 Can't connect to bartruff.net:80 (Bad hostname 'bartruff.net')"

But if I use the urls http://www.bartruff.net/ or http://bartruff.net on my network, I get a page.

So esentially, I can reach the web site from the internet by ip, but not by name.

I am using a firewall and have opened http in the options and am using tcp/ip filtering with udp permitting all incoming/outgoing.

My DNS server is named NS1
My Primary zone is named bartruff.net

I have these records in the forward looking zone bartruff.net:

Name Type Data
(same as parent folder) Start of Authority (SOA [9], ns1.bartruff.net., hostmaster.bartruff.net.

(same as parent folder) Name Server (NS) ns1.bartruff.net.
ns1 Host (A) 66.134.64.146

www Alias (CNAME) ns1.bartruff.net.
web1 Alias (CNAME) ns1.bartruff.net.

I have these records in the reverse looking zone 64.134.66.in-addr.arpa:

Name Type Data
(same as parent folder) Start of Authority (SOA) [2], ns1.bartruff.net., hostmaster.bartruff.net.
146 Pointer (PTR) ns1.bartruff.net.
(same as parent folder) Name Server (NS) ns1.bartruff.net.

I have registered bartruff.net at network solutions and the name servers are ns1.bartruff.net and ns2.bartruff.net with ip's of 66.134.64.146 and 147 respectively.

I am using Covad for synchonous dsl and they have assigned 5 ip numbers in the range 66.134.64.146-150. I have asked them to put a pointer to 66.134.64.146 and 147 with ns1.bartruff.net and ns2.bartruff.net which they have done.

One last point, I am using a domino server to dish up the web page, but I think the fact I can reach it by number but not by name points to a dns issue. I just can't think where the issue lies and I've just about gone crazy trying to debug it (although I've also learned a lot in the last few weeks!).

Any help would be greatly appreciated....

It turned out the firewall was not allowing udp traffic into the system so the dns server was not able to respond.

I opened udp port 53 in the network connection settings and all is well.

Doh!