DNS Question

[msteinblock]

I am trying to setup some DNS here and have a couple questions.

I have setup NS1.Domain.com and NS2.domain.com to point to my public ip address. I have also pointed domain.com to those two name servers.

I am running a local DNS server with that port being forwared thru the firewall. On my local DNS server, should I have the private IP of the site or the public? (I am assuming public). If is it public, is it possible for me to view the site locally? What DNS should I point the server to? Itself or the ISP's?

Thanks for the help!!!

 

[msteinblock]

I think everything is setup correctly and I am waiting for things to propogate. Is there anyway to test whether my DNS server is working in the outside world?

This is the domain I am working with: matthewsteinblock.com

Thanks!

~Matthew

 

[msteinblock]

Here is what I am getting:

Category Status Test Name Information
Parent PASS Missing Direct Parent check OK. Your direct parent zone exists, which is good. Some domains (usually third or fourth level domains, such as example.co.us) do not have a direct parent zone ('co.us' in this example), which is legal but can cause confusion.
INFO NS records at parent servers Your NS records at the parent servers are:

ns1.matthewsteinblock.com. [67.53.167.60] [TTL=172800] [US]
ns2.matthewsteinblock.com. [67.53.167.61] [TTL=172800] [US]

[These were obtained from e.gtld-servers.net]
PASS Parent nameservers have your nameservers listed OK. When someone uses DNS to look up your domain, the first step (if it doesn't already know about your domain) is to go to the parent servers. If you aren't listed there, you can't be found. But you are listed there.
PASS Glue at parent nameservers OK. The parent servers have glue for your nameservers. That means they send out the IP address of your nameservers, as well as their host names.
PASS DNS servers have A records OK. All your DNS servers either have A records at the zone parent servers, or do not need them (if the DNS servers are on other TLDs). A records are required for your hostnames to ensure that other DNS servers can reach your DNS servers. Note that there will be problems if your DNS servers do not have these same A records.


NS FAIL NS A timeout occurred getting the NS records from your nameservers! None of your nameservers responded fast enough. They are probably down or unreachable. I can't continue since your nameservers aren't responding. If you have a Watchguard Firebox, it's due to a bug in their DNS Proxy, which must be disabled (31 Jul 2006 UPDATE: several years after being informed of this, there is a rumor that there is a fix that allows the Watchguard DNS proxy to work).

Does this mean that the DNS server is not being seen outside of the firewall? How can I test that? I have TCP/UDP 53 allowed.

Thanks