Re: Frustrating

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

Well, I had this thought before you wrote it, but its good to hear it again. I did something similar

Added a cname for www that points to the FQDN of the DNS server that has the entry for www
and a A record for just the http://site.com entry that points to the IP of the DNS server....

Seems to work fine....

Thanks!!

"Phillip Windell" <philwindell@xxxxxxxxxxx> wrote in message news:OVrAZvJVJHA.3912@xxxxxxxxxxxxxxxxxxxxxxx
"Steve Grosz" <boise_bound@xxxxxxxxxxx> wrote in message news:7473F167-4E18-4114-A262-79244F0B2F46@xxxxxxxxxxxxxxxx

We run 2 DNS servers on our Win2003 AD network. We were hosting our website internally, and recently moved our site to someone else. I work for the a state agency, so our DNS is forwarded onto the main state DNS servers, and each of my 2 DNS servers have 4 IP for forwarding DNS requests.

We had several cname records, www being one of them, that pointed to the webserver. I removed the cname record for www yesterday (12/1). The minimum TTL is set to 1 hour, and scavange is 1 day.

Since deleting that cname record, if I try to ping/tracert www.site.com, I get: "could not find host www.site.com. Please check the name and try again".

Assuming your AD Domain Name and the Public Domain Name are spelled the same (sounds like they probably are),.....You have to replace CNAME with an A Record that uses the new IP# of the Site. You DNS is *not* going to bounce to a Forwarder when it already possesses a Zone of the same name within its own Database.

So you DNS has to maintain *all* records for any Public Sites that use the Domain that is spelled the same as your AD Domain Name. However the ISP or whoever is hosting the Public DNS Records still has to keep thier own records maintainsed as well.

Remember:

Your users will use your own AD/DNS to resolve this,...the Public will not.

The Public will use the ISP (or DNS Hoster) to resolve this,...your users will not.

--
Phillip Windell
www.wandtv.com

The views expressed, are my own and not those of my employer, or Microsoft,
or anyone else associated with me, including my cats.
-----------------------------------------------------



.

Relevant Pages

  • Re: To use or not to use Root Hints
    ... >> Root hints vs forwarding is a toss-up for an Internet-connected DC. ... >> circumstances either will work fine but you should start by forwarding. ... >> possible point of failure (your ISP's DNS servers). ...
    (microsoft.public.windows.server.dns)
  • Re: Correct DNS configuration
    ... Can anyone tell me the correct configuration of dns servers in a active ... DC1 has a forwarder and a root hint to DC3 ... DNS server automatically DISABLES forwarding.] ...
    (microsoft.public.win2000.dns)
  • Re: Beating the spam filter ...
    ... I'm not too sure about the PTR records though. ... Maybe a MTA will banner and HELO with its nodename, but pointing MX ... The typical uses I'm aware of for using DNS ... One general problem with CNAME records is that there isn't a solid ...
    (comp.mail.sendmail)
  • Re: Can not resolve ecx.images-amazon.com.
    ... Could you please explain the steps to resolve this issue? ... Windows 2003 DNS servers and I cannot load images form amazon.com. ... An Alias (cname) record can not be added to this DNS name. ... I have no problem resolving these names with my Win2k3 or Win2k DNS servers. ...
    (microsoft.public.windows.server.dns)
  • Re: Beating the spam filter ...
    ... touch on the matter agree that pointing an MX at a name that has a CNAME ... of abstraction for the host name of mx.hosting-company.tld such that they ... to a pool with out the need to update all the client DNS zones. ... It is dead wrong to have multiple CNAME records for one name. ...
    (comp.mail.sendmail)