Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations bkrike on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

SDDD (Same DNS, DIFFERENT DAY)

Status
Not open for further replies.

BFClem

IS-IT--Management
Sep 17, 2001
62
US
Cisco router to web is IP 192.168.0.1 and

W2K server, DC, AD, static IP is 192.168.0.6, uses .1 as default gateway and itself (.6) as preferred DNS.

Client uses .1 as gateway and .6 as DNS.

DNS set up as (domain.com), AD, with FLZ, having a that points to outside IP for our external website (
Cannot see our website from inside the network. I know this question has come up may times, but I think we are following the directions to make this work, and it will not.

Thanks
 
what directions did you follow? You need to manually create an A record for your FLZ that points to the web server's internal IP address...
 
Directions like these, but the IP of the web service is the DNS of the company hosting our website:

To create a host or "A" record:
Start the DNS snap-in. To do this, click Start, point to Programs, point to Administrative Tools, and then click DNS.


Under DNS, expand Host name (where Host name is the host name of the DNS server).


Expand Forward Lookup Zones.


Under Forward Lookup Zones, right-click the zone that you want (for example, example.com), and then click New Host.


In the Name (uses parent domain name if blank) box, type the name of the host that you want to add. For example, if you want to add a host record for a Web server, type www.


In the IP address box, type the IP address of the host that you want to add. For example, type 192.168.0.100.


Select the Create associated pointer (PTR) record check box, and then click Add Host. A message similar to the following message appea The host record was successfully created.
Click OK.


When you are finished adding hosts, click Done.
 
"the IP of the web service is the DNS of the company hosting our website" - do you mean that you don't have an internal IP for the webserver? You've built a site using your ISP's servers?
Is the forward lookup zone's domain name the same as the website's domain name?
 
Yes, correct.
internally our domain is xxx.com; our web address is and a web hosting company outside our domain hosts our website.
We have no internal web server. We just cannot see our own website from inside the company.

The FLZ domain name is the same as the website but without the front.

Thanks for your patience.
 
I bet your on the money bronto. DNS set up as (domain.com), AD, with FLZ, having a that points to outside IP for our external website
Can you see the site from outside your network? Glen A. Johnson
Johnson Computer Consulting
MCP W2K
glen@johnsoncomputers.us

[americanflag]

"Imagination is more important than knowledge."
Albert Einstein (1879 - 1955) Physicist and mathematician.
 
Hi Glen,
Yes, when at home or outside this domain, I can hit our website fine, and if it helps to say what it is, I will.

Brad
 
I guess we'll see....eh, Glen?
I'm assuming external clients are fine...
Can you get to other websites from inside?
 
B,
I'm getting to you now from in here, so yes.

B
 
OK, I didn't know you were working from there right now :)

Now, can you ping the website by name? When you try the ping, do you get an "unknown host" error, or a "request timed out"?
 
We certainly will bronto.
[pipe]
BFClem, good point about getting to the forum, but we didn't know where you were. Now, onto the show. Can you ping the site by name? Do you have any firewalls set up? Have you ever been able to get at the site? Glen A. Johnson
Johnson Computer Consulting
MCP W2K
glen@johnsoncomputers.us

[americanflag]

"Imagination is more important than knowledge."
Albert Einstein (1879 - 1955) Physicist and mathematician.

 
The ping test just passed ok,
saw the round trip with the webhosting company's IP

Brad
 
[lol] Bronto, we do think along the same vein. Curious to see what the response will be. Also curious about the firewall. Glen A. Johnson
Johnson Computer Consulting
MCP W2K
glen@johnsoncomputers.us

[americanflag]

"Imagination is more important than knowledge."
Albert Einstein (1879 - 1955) Physicist and mathematician.

 
So you CAN ping the website by name? But if you put the site into your browser it doesn't come up? What if you put the IP address of your website directly into your browser, does it come up?
 
I'm not sure what it is you would like me to try.
I can ping the website by name in the command windowand it makes the round trip.
I put the web address in the address window of the browser, but I get a nothing page.
What do I try next?
 
Do you have a firewall? This almost sounds like rites issues, except then I would expect a access denied error message. Glen A. Johnson
Johnson Computer Consulting
MCP W2K
glen@johnsoncomputers.us

[americanflag]

"Imagination is more important than knowledge."
Albert Einstein (1879 - 1955) Physicist and mathematician.

 
Correct, both the name and the number after the Http:// produce the "page cannot be displayed" screen.
I have a call into the people who manage our router to pick up on the suggestion that perhaps something is not right.

Our router (.1) points out to our ISP, but that ISP does not host our website; the site is hosted at a different ISP.

Perhaps that is where the issue is, so as soon as the tech guy modems into our router, I'll know more.

If that was the culprit, I'll let you know.

Thanks



 
CLEM Try this.
Open a Command window
type in nslookup and hit enter.
type in server followed by the ip address of your Web hosts DNS server and hit enter.
Type in your that you are trying to reach.
Does the IP addy match the number that you have listed in your FLZ If not, then type in the ip addy into your web browser.
If it shows your website, then change your DNS entry.
 
wbg34, that's a good point, thanks, I was of course working under the assumption they were the same.

BFClem, I think you're headed in the right direction. One thing to check for with the tech guys as well, is whether or not port 80 is being blocked somewhere along the route from your website back to you.

Let us know.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top