11 replies
by astute
1. Check the whois database and make sure it
points to the correct name servers, If not
request network solutions to change it to the correct IP of the name servers.
2. Make sure u have a new zone created in the dns server for this new domain.Also
u can add some host entries or cnames records
to the new site.
Good luck
by nuru
by bhrdwh
by nuru
by frobo
Hi,
i am not the best in DNS-problems, but could it be, that your DNS-Forwarder have old-Data in its cache ? It might be right, that you have to check the hole way from your network down to the Provider. I would call the ISP first, and ask him ifcould check that for me. If it works by him, than i would look back to my Network and would cut Problem in peases, IP-Segemnt for Segment and look if the lokal DNS has the same problem.
It sounds like abit of work to do, i mean could that some one else has a better idea.
havanice day
frobo
by nuru
Thanks frobo,
Our internet conection does not go through any provider we are connected straight to the internet backbone via sattelite. However someone sugested the problem might be from the router, I'm still checking but the question is still open for any suggestion.
Your description certainly sounds like a name resolution issue...
To debug, you may want to try temporarily pointing one of your machines to another DNS server.
Is your DNS server managed by your company or are you using your ISP's DNS server?
If it is managed by your company, try using your ISP's DNS server. If you are using your ISP's DNS server try to find a DNS server that is reasonably close to you geographically.
by nuru
by stillatit
Unfortunately, the .com domain has been liberalized over the years, and you will frequently see a .com hosted by a host site in another country. If their DNS is right, you should have no problems on that account.
Typing www.landell-mills.com frommy home brought up their site.
Because of the way site hosting companies work, it is possible for the IP of a named site to move around at infrequent intervals as the host shuffles servers, or as the company moves to a different hosting site. Asa result, the IP address you saved last week may not be good this week.
Unfortunately, not all host sites use a short TTL (time to live) on their DNS entries, and as a result if, for example, they have a 30 day TTL and do not change their serial number when they change an IP, your DNS server will cache the old address for 30 days or until it flushes the cache to make room for other entries.
By the way, talking about using the domain name, it is NOT always the case that if a company has a site www.company.com, that using company.com will get to the same address, or to any address. It depends on what they have set up in their DNS.
Things to check:
a) If you have a HOSTS file on your computer, make sure that if you have an entryfor your target site, the entry is correct. Better yet, comment out the entry.
b) If you have put any records for these sites into your DNS as shortcuts, delete them.
c) If you have shortcuts in "favorites" the same thing applies. You may be pointing at an old IP address.
d) Using NSLOOKUP, try looking up their site (don't forget the www.) on your DNS server, then on someone else's DNS server. If your server has a different result, you may have an old number cached.
Good luck.
by nuru
Thanks Guys, the problem has been solved.
Apperently the problem was from the router, A cisco egineer solved it, but I've requested that he makes a write up of the solution. I will post the answer as soon as I get it.
Nurudeen
by nuru
This discussion is closed to new replies.
Trending Windows Forum posts
Sort by Trending