|
|
 |  |
Re: Non-authoritative serverFrom: Matthew Fosberg Date: Thursday, May 13, 2004
Time: 8:44:05 pmHere's my results so far:
Checked all spelling and for any obvious errors of that sort, and found
none, of course it's still possible I'm just not seeing one that is
there.
I got DNS Expert Pro and queried the server from both the server itself
and from another computer on my local network. Both report as receiving
authoritative answers from mattcave.bohemianfreecorps.com.
I am in the process of having a friend check on what he sees when he
connects from his home, but I probably won't find out until tomorrow.
Meanwhile, DNSstuff.com still reports my server as being
non-authoritative.
A couple of things that might have relevance.
1. When I try to log on to the server from the machine itself with
QuickDNS manager it will only allow me to do so when I use the internal
IP address of the computer it is on 192.168.1.10. If I try the public
IP, or the server name I get an error stating I cannot log on to the
server.
2. I am not using this server for my own DNS purposes, (other than
providing DNS for one of my domains and a friends) I use my ISP's DNS
for my own computers, so nothing inside my personal network should be
querying the server. I also do not have the reverse zone configured to
point to my static IP, and I know that my ISP will not delegate that to
me.
Could either of these be related to my problem?
Matt Fosberg
On May 13, 2004, at 7:15 AM, Men & Mice Support wrote:
> Since there's nothing obviously wrong, check every detail. Here's an
> example of how you might approach this:
>
> Step 1: Check the spelling of the zone in QuickDNS Manager.
>
> Step 2: Download DNS Expert Pro from our FTP server and install it on
> the server. If you don't have a license, it will act in demo mode,
> which is fine for this testing. Use the DNS Query tool in DNS Expert
> Pro to query the server, non-recursively, for any record named
> bohemianfreecorps.com. If it doesn't return an authoritative answer,
> then the problem is on the server itself. Otherwise, continue to step
> 3.
>
> Step 3: Copy DNS Expert Pro to another machine on the same switch and
> repeat the test. If the test in step 2 succeeded, but the test in this
> step failed, then the problem is in the switch.
>
> Step 4: Repeat step 3, moving outward from the server each time. For
> example, the next test might be from outside the router (if you can
> manage this), or sent through the router to the public IP address.
|

Return to Digital Point Solutions' Home Page |