Microsoft DNS issue resolving our external website

We had our 3rd website redesign in 2 years.  Usually, I go to our network solutions account and change the www A record to point to a new DNS (always new hosting).  I than change the @ record to the same IP.  And then I go to our internal DNS server (Windows 2000) and change the HOST record for www to the same IP.

THIS time, they told me to REMOVE the www A record.  Then create a CNAME for www that points to @.
Then I put the new IP in for the @ record.

But I am not at all sure what to do with our internal DNS then.  Any pointers would be greatly appreciated.
Who is Participating?
Hypercat (Deb)Commented:
Assuming, as David Piniella suggested, that you have an internal AD domain with the same domain name (i.e., as your external domain, you should put the www record back on your internal DNS server and point it to the external IP address of your website.  This will allow internal users to get to the website AS LONG AS they type "" on the address line in the browser.  If you have an AD domain, there is no way to get it to resolve just "" to the external website because that name is controlled by Active Directory and any queries looking for that SRV record will be resolved internally.
Kash2nd Line EngineerCommented:
You don't need to put any records on your internal DNS server.
I would just clear DNS cache and it should then query the internet DNS servers for the A record for your website.

What they might have said is as below:
A record                       the external IP << Current

They want you to create
www        CNAME
then    A Record     the IP

It is technically the same and your current setup should still work

If you put your website address there and search for A record, do you see the new IP.
hydraziAuthor Commented:
It's not working.  We have some servers internally related to our domain.  Such as points to an internal server.  But points to this outside hosting.

I tried not making the change and it kept going to our old hosting.

Removing the www record yesterday has just made it refuse to resolve at all.

Everywhere else, it resolves fine.
Protect Your Employees from Wi-Fi Threats

As Wi-Fi growth and popularity continues to climb, not everyone understands the risks that come with connecting to public Wi-Fi or even offering Wi-Fi to employees, visitors and guests. Download the resource kit to make sure your safe wherever business takes you!

Kash2nd Line EngineerCommented:
what to you get when you ping internally ?
Kash2nd Line EngineerCommented:
where did you remove www record from, online DNS or internal DNS?
Kash2nd Line EngineerCommented:
on the DNS you should something in those lines below:      A      External IP Address      CNAME
hydraziAuthor Commented:
I have removed the www Host (or A) record from both internal and external DNS.

The site works great for anyone outside of our network.
It does not resolve at all from inside of our network.

Whn I try to ping it internally now, It says it cannot find host name.
Which tells me that it is asking the internal DNS about it, getting no answer, then going no further.
So, I assume that your internal domain name is the same as what you have externally?

If so, you're pretty much at an impasse.  You can't have the @ record (blank) point at the external site, because it points to your domain controllers.  Your website designer should adjust your site to always use and not just (keep this is mind for any future redesigns).  The only other way around this (not recommended) is to set up IIS on all your DCs and have them do redirects.  The way to avoid this is to make sure your internal and external name is not the same.  MS's recommendation (and the method I espouse) is to make your internal domain a subdomain of your external, i.e. something like "".
David PiniellaCommented:
Are you running Active Directory on that DNS server? Is your AD Domain the same name as your AD will make the @domain.tld records to point to your DCs, so unless the website is hosted on those DCs, it'll break. If this is the case -- and you can verify by opening a command line and do nslookup your domain name against your DNS server -- the easy fix is to setup IIS on the DC and make it redirect any http/https queries to your external website IP.
hydraziAuthor Commented:
Our internal AD domain is not the same as our external domain name, however, there is a whole lot of external domain entries in our DNS.

So, we have and then  Some othe addresses are for our internal servers to be accessed for intranet and also from the outside.
hydraziAuthor Commented:
Adding it back in as you suggested did work.  many thanks.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.