DNS server Test Queries Monitoring Fails

[Mike]

Folks,

In my new DNS server setup (Windows 2003), a migration from my old NT
4.0 DNS server setup, it all appears to be working - at least from a
query standpoint from internal machines and from the outside world. I
don't see a problem.

However, under the DNS manager properties there is a property tab
called "Monitoring" that has two check boxes and a Test Now button.

... [ Monitoring ] ...

To Verify the configuratio of the server, you can perform manual
or automatic testing:

Select a test type:

[_] A simple query against the DNS server
[_] A recursive query to other DNS Servers

To perform the test immediately, click Test Now. [ Test Now ]

Well, when I check these test types, I am getting in the test results
window "fail" results for both simple and recursive.

The help was not all that clear (to me) as to what actual test (what
is being looked up) is being done. It just describes what simple
and recursivemeans, not what it is actually doing. So its hard to see
why these fail.

Less helpful, it doesn't record these in the events log or in the
debugging dns.log.

Any tips or clues to check out.

Again, other than this, it (the primary DNS server) all appears to be
working for queries internally or externally.

Thanks

--

[Ace Fekay [Microsoft Certified Trainer]]

In news:uA6Fxopq...@TK2MSFTNGP02.phx.gbl,
Mike <unk...@unknown.tv>, posted the following:

Hi Mike,

Do you have a forwarder configured?
Is the DNS server multihomed?
Any settings disabled?
Root hints exist?

--
Ace

This posting is provided "AS-IS" with no warranties or guarantees and
confers no rights.

Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSA Messaging, MCT
Microsoft Certified Trainer
ace...@mvps.RemoveThisPart.org

For urgent issues, you may want to contact Microsoft PSS directly. Please
check http://support.microsoft.com for regional support phone numbers.

[Mike]

Ace Fekay [Microsoft Certified Trainer] wrote:
> In news:uA6Fxopq...@TK2MSFTNGP02.phx.gbl,
> Mike <unk...@unknown.tv>, posted the following:
>> Folks,
>>

>> Well, when I check these test types, I am getting in the test results
>> window "fail" results for both simple and recursive.
>

> Hi Mike,
>
> Do you have a forwarder configured?
> Is the DNS server multihomed?
> Any settings disabled?
> Root hints exist?

- Forwarder is configured to my T1 provider cache servers (two of
them). The only difference in setup I see between the NT 4.0 and 2K3
DNS manager is a extra list box to define which queried domain names
the forwarders apply. It is at the default "All Other DNS Domains"

- Yes, this machine is multi-homed, .22 and 2 others for specific
service application binding and I added .210 for a single IP binding
for the DNS seerver. So the DNS server is only bound to .210 on port
53 UPD/TCP. Verified with NETSTAT.EXE. Netstat shows it also bound
to 127.0.0.1, I guess for internal management.

- Which settings specifically? Let me see whats disabled... well, the
only thing I turned off was

[X] Do not use recursion for this DNS server

for the forwarder list. Which means that if the uplink fails to
resolve the query, do not recurse - return a failure (NXDOMAIN)

Under Advanced, I left the defaults which are:

[_] Disable recursion (also disables forwarders)
[X] Bind Secondaries
[_] Fail on load if bad zone data
[X] Enable round robin
[X] Enable netmask ordering
[X] Secure cache against pollution

- Root Hints do exist, cache.dns.

If it only logged the querie in the DNS.LOG it would help. :-)

But every expected query I do internally and externally (from my home
machine where I am at right now) all seems to work, including expected
failures.

Maybe my network provider cache servers are not recursing and its
looking for this?

Let me try something.... switch it to opendns.com forwarders...

Nope, didn't make a difference here with the Monitoring test types.

Again, if it only logged the freaking packets :-)

--

[Ace Fekay [Microsoft Certified Trainer]]

In news:O2h%23RuqqJ...@TK2MSFTNGP03.phx.gbl,

Do not use recursion under the Forwarder tab says to not use the Root.
Uncheck that setting and try it agian.

Keep in mind, multihoming will surely cause this. Why is it bound to the
loopback? In the DNS interface tab, is it just listening to .210? In the
machine's IP properties, is 127.0.0.1 listed? If so, change it to only .210.

Also to keep in mind with internal Windows queries, it also uses the
empheral ports (1024-5000 UDP) another reason why the test may be failing.

Ace