Page 2 - Unable to resolve DNS server name

I think we might be onto something here.....The first block is from my firewall logs and even tho its not enabled its logging and this is what I've found this time:

2004-01-12 22:38:38 OPEN-INBOUND TCP 68.51.39.58 65.60.176.37 4776 53 - - - - - - - -
2004-01-12 22:38:41 DROP TCP 65.60.176.37 68.51.39.58 53 4776 40 A 4095290865 1367087743 17520 - - -
2004-01-12 22:38:46 OPEN-INBOUND TCP 68.51.39.58 65.60.176.37 4781 53 - - - - - - - -
2004-01-12 22:38:47 DROP TCP 65.60.176.37 68.51.39.58 53 4776 40 A 4095290865 1367087743 17520 - - -
2004-01-12 22:38:49 DROP TCP 65.60.176.37 68.51.39.58 53 4781 40 A 296597809 1369421173 17520 - - -
2004-01-12 22:38:55 DROP TCP 65.60.176.37 68.51.39.58 53 4781 40 A 296597809 1369421173 17520 - - -
2004-01-12 22:39:17 OPEN-INBOUND TCP 68.51.39.58 65.60.176.37 4801 53 - - - - - - - -
2004-01-12 22:39:20 CLOSE TCP 65.60.230.68 65.60.176.37 1564 1138 - - - - - - - -
2004-01-12 22:39:20 DROP TCP 65.60.176.37 68.51.39.58 53 4801 40 A 930566696 1378067615 17520 - - -
2004-01-12 22:39:26 DROP TCP 65.60.176.37 68.51.39.58 53 4801 40 A 930566696 1378067615 17520 - - -
2004-01-12 22:39:45 OPEN-INBOUND UDP 68.51.39.58 65.60.176.37 4823 53 - - - - - - - -
2004-01-12 22:40:20 CLOSE TCP 68.51.39.58 65.60.176.37 4776 53 - - - - - - - -
2004-01-12 22:40:20 CLOSE TCP 68.51.39.58 65.60.176.37 4781 53 - - - - - - - -
2004-01-12 22:41:20 CLOSE TCP 68.51.39.58 65.60.176.37 4801 53 - - - - - - - -
2004-01-12 22:41:20 CLOSE UDP 68.51.39.58 65.60.176.37 4823 53 - - - - - - - -

Seems packets I'm supposed to be sending back to you are being dropped? Perhaps the ICF even though not enabled is still working?

For SilentRage:

After numerous discussions with my ISP and formatting my hard drive and re-installing everthing I've finally figured out that my ISP doesn't have their own dns - someone else does it for them and the port 53 is BLOCKED. I've setup bind to listen on port 48 and when I tested on a site that let me choose the port number I got an authoritive answer with all my info. However, testing on say dnsreports.com it times out due to the blocking. Is there any way setup my server to answer on port 48 when a request comes in and have my dns stay on the port 53...does that make any sense?

oh man, that totally sucks dude. Sorry, but you can't host a dns server that is good for anything on a port other than 53. It is absolutely impossible. You need to use alternative hosting. Here's a list of services which provide free or partially free domain hosting.

http://www.dollardns.org/compare.html

OK at least it's solved...thanks for trying to help me out though and I'll look through those links you provided