My website is not working, but when I typed this address http://10.14.1.1 it run fine from our workstation. The ISP provider changed the DNS addresses in their system. How about our cisco router? Do we have to change/edit this? Not only our website, the SMTP and IMAP are also affected. Any inputs here will be appreciated.

how long has it been since you did the address changes? Most ISPs say it will take up to 72 hrs for DNS changes to propogate over the net.

All of the 10.x.x.x IP range is private and will not route across the net. That range is set aside for internal networks or test networks. Having that IP work from your workstation is not a valid test for determining that it should work over the net. You need to use the actual IP that it is assigned in DNS. It may be that the website isn't set to listen to the real IP.

HTH

Forrest

bret381 last friday night started the changes of IP addresses of the ISP from their system. The first problem is our IMAP and SMTP in Monday morning, we cannot use it. Then in evening same day, our intranet and our WWW.

Forrest Yes, I just trying to test that the web server is working.

Thanks for your replies!

What will I do?

The point I was trying to make is that you need to use the IP assigned by your ISP for that system, not the internal one in order to make sure it is working. You can also do an nslookup on the FQDN of the system and see if it gives you the correct new Internet IP.

Forrest

Forrest OK, after running the nslookup, this is the message: server can't find <myaddress>: SERVFAIL

And are you using your ISP's dns servers or internal ones?

Forrest

The ISP said that they only changed the secondary DNS. I use the internal one. BTW what is the internal one? My old DNS IPs?

An internal one would be one you are running and administering.

Forrest

The internal DNS server.

your address needs to point to the ip assigned to you by your ISP.

Where will I change it? in my internal DNS server or in my cisco router?

who do you have the Domain name registered through?

Let me make sure I am understanding you correctly...

You have a domain name: www.yourdomain.com registered and currently pointing to 10.x.x.x When you type in yourdomain.com, it doesn't make it to your server. correct?

If this is the case, you need to login to your account through whatever registrar you have the name yourdomain.com registered to and point that name to your IP address assigned to you by your ISP.

So for example, say you registered your domain name yourdomain.com through yahoo. Your ISP assigns you the ip address of 68.112.48.1. You will point through yahoo yourdomain.com to 68.112.48.1. This is of course assuming you have a static IP address. If you hae a dynamic IP, you will have to use a service such as dyndns. You can register a domain name through them and use their service to keep track of your ip, however it is generally a little more expensive than other registrars for the name, but you don't have to pay the cost of having a static ip.

If I'm not understanding you right, my apologies and just ignore me

Correct!

bret381 Thanks for the info. I'm not sure which of this two servers is my DNS. Can you analyze this error from openDNS Guide?

Nameserver trace for www.yourdomain.com:

* Looking for who is responsible for yourdomain.com and followed hostname1.yourdomain.com.

Nameservers for www.yourdomain.com:

* hostname1.yourdomain.com returned (NORECORDS)
* hostname2.yourdomain.com returned (SERVFAIL)

Hostname1 is my DNS server, right?

do you have static or dynamic ip? If you have dynamic, you can't run a dns server. Just not gonna work, even with dyndns service it's not gonna work. If it's static, then looking at what you posted earlier, I would say that hostname1.yourdomain.com is probably your dns server... but not real sure.

Are you setting all this up at home or are you setting this up at a corporation?

If at home, there really is no need for a dns server other than for local requests if you want.

I would point your domain name to the ip address assigned. Then through your cisco router, I would forward port 80 and 443 to the local ip of your web server.