Re: multiple dns zone advice

Tech-Archive recommends: Fix windows errors by optimizing your registry


"Andrew Story" <andrewDOTstoryATjameswalkerDOTbiz> wrote in message
news:Ocg277CMHHA.1044@xxxxxxxxxxxxxxxxxxxxxxx
Hello NG,

Win2k AD single domain.

I have my DNS AD integrated forward lookup zone. Lets call it
country.companyname.com

I have been asked to provide name resolution for my clients for an
internal
and external service on a web server to company.org DNS domain. If I make
an entry in a hosts file on a machine it works perfect, so x.x.x.x
webservice.company.org is the entry

If I add a DNS zone for company.org in AD, and add a host A record there
it
does not resolve nor can I access the service, I'd rather not have to
manage
hosts files and wondered what is the standard way around this situation
please?

Don't use host files -- as you note, they are impractically difficult to
maintain
and distribute reliably.

USUALLY a DNS server doesn't do this for a zone it doesn't hold
authoritatively (but there are work arounds if you must*).

The standard methods are:

1) Let the DNS server recurse or forward to find that other zone
just like it would for microsoft.com or google.com

2) Use conditional forwarding (Win2003 only, not 2000) to
send the queries directly to the server (set) that is
authoritative
for that 'other' zone.

3) Use a Stub (2003 only again) or Secondary for that zone to make
the local DNS (think it) know(s) about that zone directly.

4) * Create a zone for ONE specific record, e.g., a zone name:

www.company.org (with the WWW as part of the ZONE name)

Then add a blank (same as parent) A record to override JUST
that one record rather than the entire zone.

Please bear in mind that the 2nd domain company.org is also our internet
domain name aswell, and obviously when I done this I couldn't browse the
external website.

If adding it to DNS didn't work at all, then you made a mistake in the
creation of the zone, or the records for that server, or in how the clients
were configured to use that DNS server.

Check these kinds of problems with NSLookup and SPECIFY each
of the possible DNS servers until you locate the problem:

nslookup www.company.org. IP.Internal.DNS.Server

nslookup www.company.org. IP.Actual.DNS.Server

Both should work (and give same answer for the www server) or
you have misconfigured something. (And ignore the bogus error
from NSLookup when it cannot reverse your DNS SERVER name,
that doesn't matter.)

Any info would be great, TIA.




.

Relevant Pages

  • Re: Replication issues
    ... I wanted to say Zone Transfers not Zone Forwarding. ... AD-Integrated DNS does not do zone transfers between the ... your DNS server will bypass ...
    (microsoft.public.windows.server.active_directory)
  • Re: Windows 2003 DNS Setup for Sub-Domain off of Root
    ... > dns in any other zone than the one that is assigned to them. ... > delegating each sub-domains zone from the root domain. ... they are not needed on the root domain DNS servers as the actual ... > the root zone from the sub-domains dns server. ...
    (microsoft.public.windows.server.dns)
  • Re: DNS Redesign Issue
    ... set the new child domain DNS server as primary for the domain controllers? ... -If you are going to create a new AD Integrated Zone in each child domain, ...
    (microsoft.public.windows.server.dns)
  • Re: DHCP Clients getting DNS lookup failures
    ... It sounds to me like you had a DNS issue but you fixed it, ... The DNS server has encountered a critical error from the Active ... Check that the Active Directory is functioning properly. ... Active Directory for this zone and is unable to load the zone without ...
    (microsoft.public.windows.server.sbs)
  • RE: exchange server cannot mount mailbox store
    ... What's the exact detailed DNS Events ... Type desired internal IP address of your SBS server. ... it will delete the reverse lookup zone if the zone no longer ... Microsoft CSS Online Newsgroup Support ...
    (microsoft.public.windows.server.sbs)