This is the deal

  • Thread starter Thread starter dst
  • Start date Start date
D

dst

company 1 host our company domain name and web page.
Company 2 is our ISP.
After the Active directory upgrade I am unable to view our
web page. Internally(from within the company), outside the
company it works fine. I contacted company 1(my ISP) and
made them aware of the situation. Their response was that
it was not a problem on thier end it was an Active
Directory/DNS problem on my end. I brought in a
consultant to look at the settings and he vcould not
figure out why we could view all pages but our company
webpage. Prior to the active diectory upgrade we could
view the page fine. I am a liitle confused about this
issue because if I put the DNS number in the client
machine's DNS it works fine, but if I put the same
onfiguration in the server it does not work. What can I do
to check, verify and view our web page?
 
In
dst said:
company 1 host our company domain name and web page.
Company 2 is our ISP.
After the Active directory upgrade I am unable to view our
web page. Internally(from within the company), outside the
company it works fine. I contacted company 1(my ISP) and
made them aware of the situation. Their response was that
it was not a problem on thier end it was an Active
Directory/DNS problem on my end. I brought in a
consultant to look at the settings and he vcould not
figure out why we could view all pages but our company
webpage. Prior to the active diectory upgrade we could
view the page fine. I am a liitle confused about this
issue because if I put the DNS number in the client
machine's DNS it works fine, but if I put the same
onfiguration in the server it does not work. What can I do
to check, verify and view our web page?
Click to expand...

Your ISP is right, the consultant obviously knows nothing about DNS I hope
you did not pay him.

In the Foward lookup zone for your domain name ( I assume you have the same
name internally as your public domain) create a new host named www and give
it the IP address of the website hosted on your ISP.

If you want to access the site by only the domain name (domain.com) that
requires a blank record. But, all DCs create blank records for all IPs on
them so adding the blank record won't work but once in a while due to round
robin. You can stop the blank records but then group policies won't work
right. You can run IIS on all DCs and use web site redirection in IIS to
redirect to www.domain.com.
 
-----Original Message-----
In

Your ISP is right, the consultant obviously knows nothing about DNS I hope
you did not pay him.

In the Foward lookup zone for your domain name ( I assume you have the same
name internally as your public domain) create a new host named www and give
it the IP address of the website hosted on your ISP.

If you want to access the site by only the domain name (domain.com) that
requires a blank record. But, all DCs create blank records for all IPs on
them so adding the blank record won't work but once in a while due to round
robin. You can stop the blank records but then group policies won't work
right. You can run IIS on all DCs and use web site redirection in IIS to
redirect to www.domain.com.




.
I do have a www with the IP of the address of the website
Click to expand...
host. with this in place I still can not access the web
site(our company) all other sites work fine. What else can
I check??
 
In (e-mail address removed) <[email protected]>
posted a question
Then Kevin replied below:
host. with this in place I still can not access the web
site(our company) all other sites work fine. What else can
I check??
Click to expand...

That is it, if you have the www record (as a host not a CNAME) it will work.
Try running nslookup against the DNS server to see if it resolves to the
correct IP address. If it does then run ipconfig /displaydns to see if the
record is cached with the correct IP address. Maybe someone put in a hosts
file with the wrong address, if that is the case it will show in the
displaydns command.
Post back your results
 
You should never set your internal DNS host name the same
as your company url, especially if it is hosted
externally.

Send that consultant home next time!!!! hehe

SAL
 
-----Original Message-----
In (e-mail address removed)
Click to expand...
posted a question
Then Kevin replied below:

That is it, if you have the www record (as a host not a CNAME) it will work.
Try running nslookup against the DNS server to see if it resolves to the
correct IP address. If it does then run
Click to expand...
ipconfig /displaydns to see if the
record is cached with the correct IP address. Maybe someone put in a hosts
file with the wrong address, if that is the case it will show in the
displaydns command.
Post back your results




.
I ran nslookup and had these reults:
Click to expand...
server:our server name was listed
address: the IP of our server

name: the company that hosts our domain/webpage
address: the IP address of the server

I also ran ipconfig/displaydns, I found our server was
listed but I did not see the name of the hosting comapany.
 
In
dst said:
I ran nslookup and had these reults:
server:our server name was listed
address: the IP of our server

name: the company that hosts our domain/webpage
address: the IP address of the server

I also ran ipconfig/displaydns, I found our server was
listed but I did not see the name of the hosting comapany.
Click to expand...
Are you using a host record or a CNAME for the www record?
You cannot use a CNAME you must use a host record.
The www record must point to an IP address.

As I also stated accessing by a only the domain name is not recommended
unless you have IIS running on your DCs redirecting to www.domain.com. This
is because domain controllers require the blank record for several AD
operations.
 
-----Original Message-----
In comapany.
Are you using a host record or a CNAME for the www record?
You cannot use a CNAME you must use a host record.
The www record must point to an IP address.

As I also stated accessing by a only the domain name is not recommended
unless you have IIS running on your DCs redirecting to
Click to expand...
www.domain.com. This
is because domain controllers require the blank record for several AD
operations.






.
I am using it as a host record which points to the
Click to expand...
hosting company. IIS is not running currently.What do you
mean about only accessing by domain name?
 
In
I am using it as a host record which points to the
hosting company. IIS is not running currently.What do you
mean about only accessing by domain name?
Click to expand...

What do you mean by pointing to the hosting company?
The record must point to the IP address of the website.
If you will give me your website name I can tell you exactly what IP this
record must point to.

domain.com vs. www.domain.com
accessing by domain.com requires a blank host, for which domain controllers
will create one for each IP on the machine, this record is required to point
to all IP on all DCs. If you add a blank record that points to an external
IP address, DNS will give out the private record anyway due to netblock
priority.(it will give out the record with the closest IP to the originating
request IP).
 
-----Original Message-----
In

What do you mean by pointing to the hosting company?
The record must point to the IP address of the website.
If you will give me your website name I can tell you exactly what IP this
record must point to.

domain.com vs. www.domain.com
accessing by domain.com requires a blank host, for which domain controllers
will create one for each IP on the machine, this record is required to point
to all IP on all DCs. If you add a blank record that points to an external
IP address, DNS will give out the private record anyway due to netblock
priority.(it will give out the record with the closest IP to the originating
request IP).





.
I looked it up on networksoulutions.com. I do not want
Click to expand...
to post that info. I am very stuck here. If I ping the
IP it times out, tracert times out. If I put the number on
the client machine it works. crazy! I followed all the
suggestions:
removed TCP/IP settings, verified IP's in the forwarders,
the www which points to the IP of the hosting comany is in
place. n I am just missing something>if indeed this has
nothing to do with the ISP.
 
In
dst said:
to post that info. I am very stuck here. If I ping the
IP it times out, tracert times out. If I put the number on
the client machine it works. crazy! I followed all the
suggestions:
removed TCP/IP settings, verified IP's in the forwarders,
the www which points to the IP of the hosting comany is in
place. n I am just missing something>if indeed this has
nothing to do with the ISP.
Click to expand...
Why would you not want to post your website address?
That is all I'm asking for, network solutions has nothing to do with it. It
is not like I am asking for any personal information it is a public website.
I think that what you are doing wrong is you are not pointing the record to
the IP of the website, this may not be the same address as the hosting
company. Did you run ipconfig /flushdns?
You may not be able to ping the address if they have ICMP disabled, which is
a pretty standard practice now.
 
-----Original Message-----
In
Why would you not want to post your website address?
That is all I'm asking for, network solutions has nothing to do with it. It
is not like I am asking for any personal information it is a public website.
I think that what you are doing wrong is you are not pointing the record to
the IP of the website, this may not be the same address as the hosting
company. Did you run ipconfig /flushdns?
You may not be able to ping the address if they have ICMP disabled, which is
a pretty standard practice now.






.
alright, www.rizzoassoc.com is our page.
Click to expand...
I did run ipconfig /flushdns.
 
In
dst said:
I did run ipconfig /flushdns.
Click to expand...

Ok thanks for the post, that name resolves to a CNAME record in this
situation I suppose you should use a CNAME in case the change their IP on
the web site.
Fix this one this way in your "rizzoassoc.com" Forward lookup zone create a
new alias named "www" (without quotes) and point it to this FQDN
"wunpgh01.web.pitdc1.stargate.net" (without the quotes) flush your cache and
it should work so long as you don't have a zone for that name
(stargate.net), if you do you should delete the zone.
 
-----Original Message-----
In

Ok thanks for the post, that name resolves to a CNAME record in this
situation I suppose you should use a CNAME in case the change their IP on
the web site.
Fix this one this way in your "rizzoassoc.com" Forward lookup zone create a
new alias named "www" (without quotes) and point it to this FQDN
"wunpgh01.web.pitdc1.stargate.net" (without the quotes) flush your cache and
it should work so long as you don't have a zone for that name
(stargate.net), if you do you should delete the zone.




.
AAHHHHH, what a relief, this worked! Thank You for your
Click to expand...
patients and assistance.
 
-----Original Message-----
In

Ok thanks for the post, that name resolves to a CNAME record in this
situation I suppose you should use a CNAME in case the change their IP on
the web site.
Fix this one this way in your "rizzoassoc.com" Forward lookup zone create a
new alias named "www" (without quotes) and point it to this FQDN
"wunpgh01.web.pitdc1.stargate.net" (without the quotes) flush your cache and
it should work so long as you don't have a zone for that name
(stargate.net), if you do you should delete the zone.



Thanks fo rhte help! where did the
Click to expand...
wunpgh01.web.pitdc1.stargate.net come from. It works!!
 
In
dst said:
wunpgh01.web.pitdc1.stargate.net come from. It works!!
Click to expand...
Your public DNS uses a www CNAME record pointing to that FQDN. Usually they
use CNAMES so that if they need to change the IP address of the web server,
they only need to change the IP on one record, instead of maybe hundreds. So
if you create a www CNAME record pointing to their web server FQDN, you will
always be in sync with the website address. You could have just used an "A"
host pointing to 209.114.150.64 and it would have worked until the IP of
your website changed.

W:\>nslookup
Default Server: kjweb.lsaol.com
Address: 192.168.0.2
www.rizzoassoc.com
Click to expand...
Server: kjweb.lsaol.com
Address: 192.168.0.2

Non-authoritative answer:
Name: wunpgh01.web.pitdc1.stargate.net
Address: 209.114.150.64
Aliases: www.rizzoassoc.com
 
Back
Top