Re: Setting up DNS records for internal web sites
- From: "Herb Martin" <news@xxxxxxxxxxxxxx>
- Date: Mon, 18 Sep 2006 14:02:45 -0500
users will have a simple name to put in their browsers. Our external
In past incarnations, Internet Explorer would use NetBIOS
names (single names) like this automatically with no extra
work but the machine would generally need to be names
something like MyWeb for this and I haven't tested IE lately.
Also the client machines are likely supplying their "suffix"
automatically so as long as the domain name of the server
is the same as the machine your CNAME (or another A)
record will work which explains how you got it working.
This would not work in the general case but sounds like all
that you need IF all of your clients use the same domain/zone
name as the web server (you didn't mention that originally)
OR you are will to give any "foreign domain clients" an
additional "search suffix".
--
Herb Martin, MCSE, MVP
Accelerated MCSE
http://www.LearnQuick.Com
[phone number on web site]
"vseven" <vseven@xxxxxxxxx> wrote in message
news:1158605173.965896.87820@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Herb Martin wrote:
BTW, what are you really trying to do as this is so non-standard
as to make almost no sense.
First off I was using example names as to not expose our internal
names. Secondly it makes perfect sense as I only want this website
accessable to the internal network and I would never want its contents
seen by the outside world. I want it to act as a top level so our
users will have a simple name to put in their browsers. Our external
domain (www.domain.com) is already forwarded correctly through our
hosting companies dns through our ISA server to its webserver and works
fine but this is not going to be externally accessible. I know this
can be done, I've seen it done on other site, I just can't seem to get
it working correctly
Lanwench [MVP - Exchange] wrote:
For internal use only, right?
Yes, only internal use by uses whose primary DNS server will be
"ServerA" (or its backup).
I make a site on the IIS6 box and set the headers to
"MyWeb". I then tried adding a new forward lookup zone called "MyWeb"
with a single blank A record pointing to ServerB's IP address. This
is not working. When I try to access it I get no response and trying
to ping it does not resolve. What am I doing wrong?
-Allan
I think you'd just need to create a CNAME called MyWeb that pointed to
serverb.mydomain.local, wouldn't you?
Thats what I started with but it wasn't resolving. Out of despiration
I tried adding another host entry of MyWeb.domain.local and pointed to
the web servers IP address just to see if that would work and that
didn't either. So thats where the extra forward lookup domain came
into place as I saw someone else doing something similiar and that was
thier solution.
After reading your reply however I decided to try again and did get it
working. It was just a CName as you suspected in the existing
domain.local forward lookup zone. I added in the CName of MyWeb and
pointed it to ServerB.domain.local like I did before but this time I
rebooted the DNS server then renewed my laptops ip info. A ping to
MyWeb now gives a reply of "Pinging ServerB.domain.local" as it should.
The web sides not finished but thats no longer a DNS issue. Thanks
for the suggestion.
-Allan
.
- References:
- Setting up DNS records for internal web sites
- From: vseven
- Re: Setting up DNS records for internal web sites
- From: Lanwench [MVP - Exchange]
- Re: Setting up DNS records for internal web sites
- From: vseven
- Setting up DNS records for internal web sites
- Prev by Date: Re: Setting up DNS records for internal web sites
- Next by Date: Re: Setting up DNS records for internal web sites
- Previous by thread: Re: Setting up DNS records for internal web sites
- Next by thread: Re: Setting up DNS records for internal web sites
- Index(es):
Relevant Pages
|
