At 10:35 AM 12/30/2005, you wrote:
I can't resolve the fully qualified name of the DNS server (the server
I'm doing this from).
"can't resolve" using which resolver?
What ever the resolver is in the MMC of the Windows Server 2003 DNS
interface. I'm not sure what it's using.
I'm able to resolve my secondary name server, which this server holds
it's primary zone. From NSLOOKUP it resolves just fine.
pixel8.com and pixelfarm.com zones have no DNS problems.
> "An IP address associated with the given name server NS record cannot
be found."
The .com NS servers have the correct glue records for both your NS.
and both your NS have the matching A records for your NS domain names.
For your 2 NS and those two zones, everything DNS checks out perfectly.
Len
That's why I think it's a bug when using the DNS MMC. Len, I do want to
thank you for the "heads up" on my PTR records and to everyone else who
responded to my question. From now on I don't think I'll rely on the error
messages the Microsoft DNS interface is giving me without checking it out
with other tools first.
Michael Graveen
---
[This E-mail scanned for viruses by Declude Virus]
To Unsubscribe: http://www.ipswitch.com/support/mailing-lists.html
List Archive: http://www.mail-archive.com/imail_forum%40list.ipswitch.com/
Knowledge Base/FAQ: http://www.ipswitch.com/support/IMail/
