>Read inline please.
>
[quoted text clipped - 40 lines]
>Of course Active Directory is not Proxy-abled, so the client needs DNS
>servers for AD, but not for web browsing.
>>Read inline please.
>>
[quoted text clipped - 14 lines]
>Thanks for all your comments by the way it has helped me no end and giving me
>a much better understanding of what the DNS servers are capable of.
I also need to mention that we have a secondary DNS server at HQ on our mail
server, do i need to create the new zone\zones on this also or will the
primary do all the work needed? And do I need to transfer the zone data of
this server to the remote domain servers? - it should have pretty much all
the same data as the primary.
Thanks again!!
Read inline please.
In news:7419521adda19@uwe,
knsljo via WinServerKB.com <u35220@uwe> typed:
> I created a test zone on the HQ DNS server and allowed zone transfers
> from one of the remote DNS servers only but it failed again i got
> "The DNS server encountered an error while attempting to load the
> zone. The transfer of zone data from the Master server failed."
When allowing zone transfers, you allow zone transfers to the IP that the
Primary sees when the transfer is requested.
> I created a test zone on one of our remote domains to transfer zone
> data from the HQ DNS server, but allowed from all addresses which
> worked it transferd the zone data. I will try this on the HQ server
> on wednesday when i'm back in the office and let you know if it
> works!!
> Can i transfer from data from all our remote domains into thisnew
> single zone or do i need to create a new zone for each?
Single Zone?
In your original post you stated each of the Remote domains had their own
domain name. If this is true then you need a secondary of each domain name,
they will not be in a single zone.
> Thanks for all your comments by the way it has helped me no end and
> giving me a much better understanding of what the DNS servers are
> capable of.
Don't let DNS intimidate you, DNS is no more difficult than using a
Telephone book.
The Root Zone, (Which you don't usually see) is the publisher of the Book,
the TLD is like the City the book covers, and the second level domain
compares to the last name of the person you are looking for, and the host is
like the person's first name.
All DNS queries actually start at the Root, usually the ICANN Root, there
are 13 servers at the root, and they give you the IP of the DNS servers for
a particular TLD, for instance "com", there are another 13 servers servicing
the com TLD, and they give the IP address of the DNS servers for a domain,
e.g. microsoft.com. Once you have the IP addresses of the microsoft.com DNS
servers, you server can go to those servers and get the IP of a host in
microsoft.com, e.g. www.microsoft.com, or get the location of where
www.microsoft.com can be found.

Signature
Best regards,
Kevin D. Goodknecht Sr. [MVP]
Hope This Helps
===================================
When responding to posts, please "Reply to Group"
via your newsreader so that others may learn and
benefit from your issue, to respond directly to
me remove the nospam. from my email address.
===================================
http://www.lonestaramerica.com/
http://support.wftx.us/
http://message.wftx.us/
===================================
Use Outlook Express?... Get OE_Quotefix:
It will strip signature out and more
http://home.in.tum.de/~jain/software/oe-quotefix/
===================================
Keep a back up of your OE settings and folders
with OEBackup:
http://www.oehelp.com/OEBackup/Default.aspx
===================================
knsljo - 28 Jun 2007 17:51 GMT
>Read inline please.
>
[quoted text clipped - 38 lines]
>microsoft.com, e.g. www.microsoft.com, or get the location of where
>www.microsoft.com can be found.
Hi there
I have managed to now implement your sugestions and it is all now working
like a charm!!
I created secondary forward/reverse lookup zone for each of the remote
domains on the on the HQ primary and secondary DNS servers, and i also
created a secondary forward/reverse lookup zone for the HQ DNS server on each
of the remote domains.
The whole aim of this was to allow our Servicedesk to perform automated
scheduled scans of remote servers and clients to keep our inventory up to
date and to monitor software changes etc. I have tested this and it is now
able to do everything we require.
I knew what the cause of the problem was, but i don't i would have been able
to figure this out, this will save me so much time and effort. Thanks alot!!