Frogworks
asked on
New website is not loading on in-house computers.
A client's new website went active almost two weeks ago. Today, they reported that when they try to get to their new site, they are still sent to the old site. However, this is only happening on computers that are in their office. If they try from their phones, it works just fine and when I tried from my office PC, it worked fine as well. I have tried clearing browsing data, using a different browser, flush DNS, and even called the ISP to see if they had cached settings. Can anyone assist?
Paul MacDonald
I'd wager it works if they use www.domain.tld from within their office. There will be a DNS record somewhere that points domain.tld (no www.)to the old web site.
Simple solution is always the same.
1) Use only 1x DNS view...
2) So only use public DNS for resolution.
3) Use DNS caching servers on local machines.
4) Delete every trace of any other local DNS zone file serving.
5) My DNS goes 1x step further by setting 60 second TTLs on all records, including NS records, so if there is a DNS problem, whatever the problem can be corrected in <60secs.
If you have TTLs of hours or days, then any change in DNS becomes impossible to debug.
Well... not impossible... just hours to days of debugging, where you never really know what you're looking at or... if any other person has the same view of DNS as you do, because they might be running different local caching.
Low TTLs == First step of DNS debugging...
1) Use only 1x DNS view...
2) So only use public DNS for resolution.
3) Use DNS caching servers on local machines.
4) Delete every trace of any other local DNS zone file serving.
5) My DNS goes 1x step further by setting 60 second TTLs on all records, including NS records, so if there is a DNS problem, whatever the problem can be corrected in <60secs.
If you have TTLs of hours or days, then any change in DNS becomes impossible to debug.
Well... not impossible... just hours to days of debugging, where you never really know what you're looking at or... if any other person has the same view of DNS as you do, because they might be running different local caching.
Low TTLs == First step of DNS debugging...
ASKER
Question im trying to delete the DNS forward lookup zone for the company website in question.
I'm getting a error when deleting stating: This folder or one of its children has one or more property sheets open. The zone cannot be deleted until all property sheets are closed.
I'm getting a error when deleting stating: This folder or one of its children has one or more property sheets open. The zone cannot be deleted until all property sheets are closed.
My recommendation was going to be to do the following on a workstation while it is in the office from a CMD prompt:
nslookup
ourwebsite.com
server 1.1.1.1
ourwebsite.com
exit
The line that results from the first "ourwebsite.com" will tell you what the default DNS gives for an IP address for the site. The line following the second "ourwebsite.com" will tell you what a public DNS server (1.1.1.1) gives for the address. If they are different, then it shows that whatever the default DNS server is giving out the wrong (likely old) address and the solution is to reconfigure that server.
My strong general preference is to identify the real source of the problem before applying fixes.
"Question im trying to delete the DNS forward lookup zone for the company website in question. "
That implies that you've identified the problem as being in your local DNS server. In any case, if it is a publicly-hosted web site, you likely should remove this zone locally (as you are trying to do).
When you try to delete the zone, have you opened anything else in the manager?
Can you go into the zone and delete any of the items?
nslookup
ourwebsite.com
server 1.1.1.1
ourwebsite.com
exit
The line that results from the first "ourwebsite.com" will tell you what the default DNS gives for an IP address for the site. The line following the second "ourwebsite.com" will tell you what a public DNS server (1.1.1.1) gives for the address. If they are different, then it shows that whatever the default DNS server is giving out the wrong (likely old) address and the solution is to reconfigure that server.
My strong general preference is to identify the real source of the problem before applying fixes.
"Question im trying to delete the DNS forward lookup zone for the company website in question. "
That implies that you've identified the problem as being in your local DNS server. In any case, if it is a publicly-hosted web site, you likely should remove this zone locally (as you are trying to do).
When you try to delete the zone, have you opened anything else in the manager?
Can you go into the zone and delete any of the items?
Take a look at:
https://community.spiceworks.com/topic/649244-windows-dns-help
That individual got the same message. The solution was:
Edit: Found a hidden window and fixed this.
Any chance of that?
https://community.spiceworks.com/topic/649244-windows-dns-help
That individual got the same message. The solution was:
Edit: Found a hidden window and fixed this.
Any chance of that?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
"Cahnged DNS settings"
From what to what?
From what to what?
Did you try my suggestions from two weeks ago? I'm not seeing the results.