Publishing to IP Address - not Domain Name

M

Mark

I have been having problems lately with my web server not
updating to the domain servers - meaning that I can always
access my website by its IP address, but not always by its
www. domain name. Until I can get the script corrected, I
would like to see if I can work around the problem.

My question is: can you publish to the IP address instead
of the domain name? When I put in the IP address number
for the location to publish to, I receive the
error "Cannot open "we80.cnf": no such file or folder."

I am using FrontPage 2000 on Win98SE.

Thanks for any help!
- Mark
 
S

Steve Easton

This is little confusing, because unless you are changing your domain name,
once it is registered with the name servers it *should* always be there
until it is changed or you change the IP address/server location for your
web.

What is your domain name??


--
Steve Easton
Microsoft MVP FrontPage
95isalive
This site is best viewed............
........................with a computer
 
K

kawipoo

Have you tried no-ip.com which allows a domain name to be directed to an IP
address. You simply direct your domain to no-ip.com's name servers and
then their servers will direct to your IP address even if your IP address
changes.
It is great because once the redirect is in place you can direct to any
server within a few minutes and don't have to wait the normal 24-48 hours
for domain name redirections.
 
M

Mark

Steve -

I don't completely understand it, but the way it was
explained to me, the host server has to keep updating the
IP number with the domain name and send that out to the
big ISP's. This is somehow done with a clock expiration
setting with their script which determines how often it
gets updated. Some of the bigger ISP's will cache the
domain name/IP address while others don't. So currently my
website will come up though AOL and Roadrunner since they
cache whereas it won't come up through Earthlink since
they don't and the script update setting has expired.

My website is www.hydrostream.org. The IP address is
216.16.122.80

Thanks,
Mark
 
T

Thomas A. Rowe

It can take up to 72 for all DNS server to updated around the world, however this should only effect
you when you first register a domain name or if the web host changes your IP address at some point.

I can access your site via the domain name in the NE.

--
==============================================
Thomas A. Rowe (Microsoft MVP - FrontPage)
WEBMASTER Resources(tm)

FrontPage Resources, WebCircle, MS KB Quick Links, etc.
==============================================
 
M

Mark

Rich -

No, I tried it both ways and neither works. Thanks for the
suggestion, though!

- Mark
 
S

Steve Easton

They both work perfectly for me, from two different Earthlink DSL accounts at
two different locations.
Not sure who told you that about caching domain names, because domain names
aren't *cached.*

Web site *content* is cached by AOL however, and the reason it will always show
in AOL is because if and when it is cached by them you are seeing your site from
their servers, not your actual web site from your server.

The Domain Name servers don't regularly "expire" registrations, they only update
them when their status is changed.

You say you've checked via AOL and Earthlink. It's possible your connection
settings have become corrupt from using both.


--
Steve Easton
Microsoft MVP FrontPage
95isalive
This site is best viewed..................
...............................with a computer
 
B

Bob

The next time you are unable to publish, try this:

c:>tracert www.hydrostream.org

If it works, you will see a screen full of output while it traces
each hop on the way to your server. That means DNS is fine and
you have a system, FP, or connection issue.

If it comes back as "Unable to resolve target system name
www.hydrostream.org" then try to tracert to your site by IP.

c:>tracert 216.16.122.80

If it still comes back as "unable to resolve..." you definitely
have a connection problem between you and your ISP, or from
your ISP to the outside world.

If the IP resolves but your domain name won't, then either you
have a DNS problem or your ISP does. If you can tracert to
any other domains (tracert www.microsoft.com for example or
tracert www.earthlink.net) then you need to complain to your ISP
that your domain is not resolving and I'd be fairly confident
it's a DNS problem at their end. Call them up, ask them to try to
tracert to your domain, see what happens, go from there.
If you can't get to microsoft, earthlink, etc then you have a
major connection issue that you need to resolve.
 
J

Jim Cheshire

Keep in mind that a tracert trace will often not be able to go the whole way
because it will eventually hit a firewall that won't allow it to proceed
further.

--
Jim Cheshire
Jimco
http://www.jimcoaddins.com
================================
Author of Special Edition
Using Microsoft Office FrontPage 2003
5 Stars on Amazon and B&N
================================
The opinions expressed by me in the
newsgroups are my own opinions and
are in no way associated with my
employer or any other party. Jimco is
not associated in any way with any other
entity.
 
M

Mark

I'll try the tracert when I get home tonight, but I'm
really confused here.

FrontPage aside, I can always reach my website though my
browser using the IP address, but usually not by the
domain name (using Earthlink). Since the website caters
to a large group around the country, I was hearing that
most people could access it, but some were having
problems like myself. I thought it was an Earthlink
problem, so I contacted them though their "live chat". I
talked to seven different people and none of them were
helpful. They said at the time that they also couldn't
access the site through the domain name, but could with
the IP address. They all blamed the website. Finally, I
had one of their techs call me and he gave me the caching
explanation I outlined above. He said it was not their
problem and they could not help me.

So that's where I'm at right now. It's very strange
because once in awhile the website will come up for me
using the domain name, but then the next day it will be
down. Most people seem to never have a problem with it,
yet some do, like me. Right now I can not get help on the
server end, so I'm pretty much on my own.

Thanks for all the help so far!
- Mark
 
G

Guest

Have you tried the usual cures? Search and delete all *.web files, delete all FP .tmp files.
ALso check your network places.
 
G

Guest

I tried it and it came back "unable to resolve...." I
then tried the IP address and it made about 10 hops and
then kept timing out on the 11th try.

Any more thoughts?

Thanks,
Mark
 
M

Myron Johnson

Mark said:
I have been having problems lately with my web server not
updating to the domain servers - meaning that I can always
access my website by its IP address, but not always by its
www. domain name. Until I can get the script corrected, I
would like to see if I can work around the problem.
Mark
Click to expand...

Mark,

Try www.dnsreport.com and insert your domain name.

When I looked at it, you had SEVERE domain name system (DNS)
nameserver problems. None of your nameservers are returning nameserver
records. Your nameservers aren't responding properly. If none of your
nameservers are responding, nobody will be able to access your site
via domain name.

The missing nameservers are:
NS2.ONVOY.NET
NS.STARPOINT.NET

Nameservers are usually furnished by the site that hosts your web
site, which appears to be Starpoint Communications. But there are
independent nameservers available, too.

You normally specify the nameservers where your domain name is
registered, which appears to be 15dollardomains.com

Fix the missing/nonreponsive DNS servers and all should be well.
Myron
 
M

Mark

Myron -

THANK YOU! That information should really help me a lot.
The only problem now will be getting some help from the
host server people - they have been unresponsive. I don't
suppose the missing nameservers has anything to do with me
not being able to publish using the IP address instead of
the domain name in FrontPage? It would be nice to be able
to work around this problem until I can get the nameserver
problems fixed.

Thanks again,
Mark
 
M

Myron Johnson

Mark said:
I don't suppose the missing nameservers has anything to do with me
not being able to publish using the IP address instead of
the domain name in FrontPage? It would be nice to be able
to work around this problem until I can get the nameserver
problems fixed.
Click to expand...

Mark, you are welcome. If your site host doesn't fix their nameservers
PROMPTLY, I suggest you find a different host!

I publish with Frontpage to my own (Windows Server 2003 and Windows
XP) servers all the time using IP address, both in-house and
externally.
Simply publish to http://xxx.xxx.xxx.xxx. As long as the FrontPage
extensions on the server are working properly, it should work fine.
Myron
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads

publishing to yahoo 1
Static IP on a printer fails 6
Cannot publish - Server error 1
weird publishing problem 2
Frontpage Publishing Host header password problem 1
we80.cnf 1
Problem Publishing to Server 2
Unable To Connect To Internet - IP Address Conflict 6

Top