Ask Question Forum:
Model Library:2025-02-08 Updated:A.I. model is online for auto reply question page
C
O
M
P
U
T
E
R
2
8
Show
#
ASK
RECENT
←
- Underline
- Bold
- Italic
- Indent
- Step
- Bullet
- Quote
- Cut
- Copy
- Paste
- Table
- Spelling
- Find & Replace
- Undo
- Redo
- Link
- Attach
- Clear
- Code
Below area will not be traslated by Google,you can input code or other languages
Hint:If find spelling error, You need to correct it,1 by 1 or ignore it (code area won't be checked).
X-position of the mouse cursor
Y-position of the mouse cursor
Y-position of the mouse cursor
Testcursor
caretPos
Attachment:===
Asked by cocosyseng
at 2024-07-28 07:36:14
ModifyPoint:500 Replies:12 POST_ID:829136USER_ID:12029
Topic:
Domain Name Service (DNS);;
Experts,
We're confused. We moved our corp website to an external hosting provider, and from the external world, we can hit the site just fine. It seems to work everywhere BUT internally. We are able to ping the IP of the site, we can tracert by the URL and the public IP successfully, but we cannot get any internal browser to bring the page up. Not by URL or IP address. What are we missing!?
Thanks!
We're confused. We moved our corp website to an external hosting provider, and from the external world, we can hit the site just fine. It seems to work everywhere BUT internally. We are able to ping the IP of the site, we can tracert by the URL and the public IP successfully, but we cannot get any internal browser to bring the page up. Not by URL or IP address. What are we missing!?
Thanks!
Expert: Joshua Grantom replied at 2024-07-28 08:54:58
Awesome, Glad we could help!
Author: cocosyseng replied at 2024-07-28 08:50:22
That worked! we got it! We added a blank record to allow clients to just resolve domain.com and the www. record. it fired right up! Thanks all!!!
Expert: Joshua Grantom replied at 2024-07-28 08:35:13
I would also make sure that your local host file has not been changed. The host file is located here
C:WindowsSystem32driversetc
Open "hosts" with notepad and make sure there is not a line
mywebsite.com Old internal ip address
C:WindowsSystem32driversetc
Open "hosts" with notepad and make sure there is not a line
mywebsite.com Old internal ip address
Accepted Solution
Expert: Joshua Grantom replied at 2024-07-28 08:31:57
500 points EXCELLENT
Also make sure that both records
@
www
are set to the new public IP address in your internal dns.
@
www
are set to the new public IP address in your internal dns.
Expert: duncanb7 replied at 2024-07-28 08:29:24
And one more thing, supposed your hosting company will make sure everything
transfer is okay to any issue whatever it is caused by internally or externally.
Duncan
transfer is okay to any issue whatever it is caused by internally or externally.
Duncan
Expert: duncanb7 replied at 2024-07-28 08:26:04
Be sure your IP/domain you typed on browser and nslookup is same.
just waiting one more day. nslookup connection is working but doesn't
mean browser will work since nslookup will use different DNS server to resolve the domain.
Duncan
just waiting one more day. nslookup connection is working but doesn't
mean browser will work since nslookup will use different DNS server to resolve the domain.
Duncan
Author: cocosyseng replied at 2024-07-28 08:17:39
nslookup for both our site and yahoo returned correct information, bot the live IPs for yahoo and our corporate site were returned.... So I guess this is still a waiting game then?
Expert: duncanb7 replied at 2024-07-28 08:11:35
Please wait for one more day( I experienced this for 3 or 4 days). And contact your hosting provider and
ask them what is wrong on the server with DNS record.
If possible, could you try one command of "nslookup http://yourcompany.com" at window command shell
and "nslookup http://yahoo.com" to see any issue
Duncan
ask them what is wrong on the server with DNS record.
If possible, could you try one command of "nslookup http://yourcompany.com" at window command shell
and "nslookup http://yahoo.com" to see any issue
Duncan
Author: cocosyseng replied at 2024-07-28 08:05:22
We transferred the site to the new hosting vendor Friday afternoon last week. It works fine externally, in fact, it started working almost immediately. it seems to be isolated to just the internal network here.
Author: cocosyseng replied at 2024-07-28 08:04:00
When we try to resole it internally, it resolves according to our DNS record with the current live public IP.
Tracert's confirm this, as our external DNS from our ISP is able to hit it just fine.
When we try to bring the page up internally, we get a 'page canot be displayed'. If we enter in the IP address, we get a splash page from the vendor, not the site.
Tracert's confirm this, as our external DNS from our ISP is able to hit it just fine.
When we try to bring the page up internally, we get a 'page canot be displayed'. If we enter in the IP address, we get a splash page from the vendor, not the site.
Expert: duncanb7 replied at 2024-07-28 08:02:41
If it is not blocked by firewall from your internal network for blocking all http access, it should be
DNS propagation delay issue .Normally, the company website domain if change to
other new hosting provider that will take within 48 hours to propagate the domain around
the world, so it will see some region can view your page , some are not.
Up this moment, how long you transfer your site to the new hosting provider, one or two day ?
Maybe wait for one more day
Duncan
DNS propagation delay issue .Normally, the company website domain if change to
other new hosting provider that will take within 48 hours to propagate the domain around
the world, so it will see some region can view your page , some are not.
Up this moment, how long you transfer your site to the new hosting provider, one or two day ?
Maybe wait for one more day
Duncan
Expert: David Piniella replied at 2024-07-28 07:57:06
When you resolve the DNS address of the site internally, does it resolve the public IP or the address from before you moved it?
What is the error you're actually getting? 404 not found, 500/503 or Page cannot be displayed or what, exactly?
Check the logs of the hosting provider, verify that your connection attempts are actually getting to the site and that the IP that you're coming from (your org is probably NAT'ing your internal users out) is not blocked from that site.
What is the error you're actually getting? 404 not found, 500/503 or Page cannot be displayed or what, exactly?
Check the logs of the hosting provider, verify that your connection attempts are actually getting to the site and that the IP that you're coming from (your org is probably NAT'ing your internal users out) is not blocked from that site.
