SRV records are an industry standard that were NOT created by Microsoft, but
used by their services and applications. You will see them used more and
more in the future by other companies. Microsoft was pretty much one of the
first, if not the first to use them.
Apparently your internal websites not being to be resolved periodically is
due to your DNS config on your machines, based on your posted ipconfig /all.
The DNS resolver service works in such a manner that it will use the first
in the list, if it doesn't provide an answer, it will go to the second one,
but it will remove the first one from the eligible resolver list and won't
go back to it unless the system is restarted, or the DNS client service is
restarted on the client machine. Hence your whole issue.
I don't follow your reasoning, if there is in fact any behind your statement. Why in the world would
the DNS server running on the PDC >>ever<< not be able to resolve a request? It's never crashed, and
the DNS has never died (well, except when I restarted it trying to solve the problem).
Cardinal rule: USE ONLY YOUR INTERNAL DNS SERVER THAT HOSTS YOUR AD ZONE.
Using any others, such as your ISP's or your firewall/router, *WILL* cause
undesirable and unpredicatable results and *MAY/WILL* cause AD to not
function properly.
Gee, am I allowed to define fowarders in this so-called DNS server? Or must it interface directly to
the internet? I sure hope not; I have little enough time to babysit cranky Windows servers as it is
without dealing with all the security flaws and challenges of one connected directly to the outside
world.
Regarding your snide comments about my lack of research...fascinating that my online research, after
the fact as it may hav been, failed to turn up that information until now, nor was it included in
either of the two tech manuals on Win2K server administration I purchased and read.
Since you seem to like quoting rules, here's one you shoudl study, as you apparently don't
understand it, and would definitely benefit from pondering it:
Cardinal rule: MAKE PRODUCTS THAT ACTUALLY WORK WHEN PEOPLE TRY TO USE THEM.
If AD cannot function properly when it interacts with DNS systems that CAN BE CONFIGURED TO USE
MULTIPLE DNS SERVERS (or have you forgotten that that is the case, sir, under Windows?) THEN THE
FAULT IS IN THE DESIGN OF HOW AD WORKS WITH DNS. Any company that would design client software that
allows for, in fact encourages, multiple DNS servers to be specified for network connections, and
then also makes (according to your statements) server software that won't work when their very own
client software is configured that way is guilty of plain and simple lousy architecting, if not
gross stupidity.
Sheesh, it's absolutely STUNNING to me how MS has managed to convince so many people that poor
design decisions, sloppy architecture, and inadequate testing are somehow the fault of the customer!
- Mark
