Re: multiple dns zone advice

Thanks Herb

In your opinion, what is the most straightforward, practical and simple way
of achieving this name resolution out of the methods you advised below?

I'm all up for simple, straighforward and reliable without much change or
potential bad-heads.

Thanks again.



"Herb Martin" <news@xxxxxxxxxxxxxx> wrote in message
news:OOwPPPDMHHA.3424@xxxxxxxxxxxxxxxxxxxxxxx

"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: NetBios and DNS
    ... I have the PC's configured with the internal DNS server and I have internet ... How I did this NSLookup was like this. ... If you have a zone for your "domain name" and you add the computer records ...
    (microsoft.public.windows.server.dns)
  • Re: Some DNS server names will not resolve using internal servers
    ... DNAME do in fact redirect queries from zone A to zone ... Until you can show the actual NSLookup responses ... DNS server (to prove that there is not some weird interaction ... We have not rebooted the DNS server yet. ...
    (microsoft.public.windows.server.dns)
  • Re: FQDN cannot be managed because it is not running Windows NT
    ... The DNS server was unable to open zone 18.35.10.in-addr.arpa in the Active ... that the Active Directory is functioning properly and reload the zone. ... event data is the error code. ...
    (microsoft.public.windows.server.active_directory)
  • Re: Local Delivery is not sending to one recipient in Exchange Ser
    ... The DNS server was unable to open zone rickkochoil in the Active Directory ... Errors in File Replication Service: ... Running partition tests on: ForestDnsZones ...
    (microsoft.public.exchange.admin)
  • Re: Error 4515 on reboot of DC/DNS Svr - normal?
    ... switch back to AD with Forest wide, and then put the DNS service ... I do believe you are correct that the "old" zone is still there. ... (replication is for all DNS servers in the forest) ... The key is that your clients have to be able to go to ANY DNS server ...
    (microsoft.public.windows.server.dns)