DNS same name as website, cannot view website

[danno74]

Greetings,

Currently our internal DNS servers are named "servername.website.com" and "exchange.website.com". So when I set our PCs DNS to the IP addresses of these two servers, we cannot view our webpage that is out on the Internet, I assume because when you put the "

http://www.website.com"

in a browser, it hits the DNS instead of the outside website.

If I change the PCs DNS settings to our ISPs outside DNS servers, then they can be viewed. But if I do that, then our Group Policy setup will not propagate to the PCs, which is paramount.

Is there something I can put in the forward lookups possibly to fix this? I'm afraid I'm new to DNS in's and out's, so I'm alittle confused.

Thanks.

 

[PeterHurst]

If I understand that correctly I think you should be able to create a static DNS on the servers to give out the external IP for

http://www.website.com

and override the one being generated.

Before doing that use nslookup on a client to check what exactly the

http://www.website.com

is giving you - it may be you can just allocate it to an internal address or it maybe the resolution is correct but because you are trying to connect to your own Internet IP the router is having a problem with NAT (cisco especially prone to this)

 

[WhoKilledKenny]

Sound like you are having this issue because your Internal name space is the same as your external. There is no rule to say how you should set your external/internal name space, but if they are the same you need to set up what is called a split brain DNS. This will allow name resolution to your Internet site from your internal network.

Read here from more info:

http://www.microsoft.com/serviceproviders/resources/techresarticlesdnssplit.mspx

Hope this helps...

 

[danno74]

This is what I get on an nslookup:

> mmri-ny.com
Server: ns1.netsitesys.com
Address: 12.27.88.34

Non-authoritative answer:
Name: mmri-ny.com
Address: 209.217.209.101

Beyond that I'm not sure what to do. I am reading that article now.

 

[rtenbroeke]

As far as I know the only thing you have to do is add the host

http://www with

the IP address of

http://www.website.com

to your local DNS table.

Good luck

 

[arsbargains]

What you need to do is in your internal DNS is put your internet DNS servers in the forwarders list. What this should do is when your users go to the internet they will hit your DNS server and then your DNS server will forward to your ISP's DNS server.


Check our our website

http://WWW.ARSBARGAINS.COM

 

[danno74]

Here's the exact solution:

In the DNS console, open the companyweb.com folder

Right click and choose New Host (A).

For name type in www
then type int he public IP of your website.

Thanks everyone for their posts.

 

[traydeezy]

I have been using the solution of using a host of

http://www to

point to the server running the website, but now users are complaining that they can't use

http://companyweb.com

to get to the website. They must use

http://www.companyweb.com.

Is there a way I can set it to be able to use

http://companyweb.com

to get to the website?

 

[Seaspray0]

In your DHCP scope options, make sure you are providing your domain name; make sure you have your record in DNS for www, then...

You can access it by typing in

http://www

or you can leave off the http:// and type

http://www and

you can get there. That's even shorter than

http://domainweb.com.

Start, Help. You'll be surprised what's there. A+/MCP/MCSE/MCDBA