Regular domain plus WordPress not accessible from inside network

We recently hired a vendor to create a new website on WordPress.  I can access http://www.ourdomain.org as always.  From OUTSIDE the network, I can access http://www.ourdomain.org/wp/wp-admin.  From INSIDE the network, I cannot access the /wp or /wp/wpadmin.  I get a "this webpage is not available" error and the detail error states "The server at ourdomain.org can't be found, because the DNS lookup failed. I do have a DNS entry in our forward lookup zone for "www" that points to the correct address - as pinged from either inside or outside the network.  Why can't my internal network find the /wp site?  Do I need to make a manual entry in the forward lookup zone?  Is this possibly a SonicWall firewall issue?

Thanks for your help.
sksaathoffAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

carlmdCommented:
Yes you will need to add the other specific URL's. You can test by doing an nslookup just on www, which should return the local address of the server. Do the same for the other complete url's and you will see they are not found.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
sksaathoffAuthor Commented:
I had already performed the nslookup with the results you predicted.  I already have a Host(A) record named "www" that statically points to the domain IP address.  What type of record do I use to create the URL?  I tried a CNAME and it gave me an error that said "The DNS name contains records that are incompatible with the CNAME record.  I put "www" in the Alias name and tried leaving it blank.  In the FQDN box I tried both www.ourdomain.org/wp and http://www.ourdomain.org/wp - and some other variants.  I get the same error.
0
footechCommented:
If you can access http://www.ourdomain.org from inside your network, then DNS is correct and there is nothing more to do there.  DNS only deals with resolving the fully qualified domain name (FQDN) portion (the "www.ourdomain.org" part)of a URL.  If you can access http://www.ourdomain.org but not http://www.ourdomain.org/wp, then you need to check the site to see if there are any redirects in place or any references that might use a different FQDN for which you might need to add a DNS record.

Is "ourdomain.org" the name of your internal AD domain (assuming you have one)?  If so, make sure the site doesn't have URLs which reference "ourdomain.org", but only "www.ourdomain.org".
0
Managing Security Policy in a Changing Environment

The enterprise network environment is evolving rapidly as companies extend their physical data centers to embrace cloud computing and software-defined networking. This new reality means that the challenge of managing the security policy is much more dynamic and complex.

sksaathoffAuthor Commented:
Our internal domain is different - xxdomain.local - not even close to the public domain.  The "wp" folder is in the same GoDaddy folder as our main site.  How would I look for redirects?
0
sksaathoffAuthor Commented:
Disregard the former question.  I used Redirect Checker.  I get a "301 Moved Permantently" returned.  Given that fact, what's the next step?
0
sksaathoffAuthor Commented:
I called GoDaddy and we discovered the problem, but not the solution.  My DNS record for www points to the public domain.  However, the WP site was created without the www (i.e. http://publicdomain.org/wp, rather than http://www.publicdomain.org).  If I create an A record with nothing in the top box, thus pointing only to publicdomain.org and set it to the same public ip as www, I get a webpage that says "pageok" in the top left corner, and nothing else.  I changed the WP site URL to include www and I can get to the site, but the pictures won't load.  I am not worried about that because I assume that's internal to the site design.  Also, I can get to the wp-admin site after adding the www.

So now I need to know what DNS entries I need to make so the publicdomain.org without www in the front will allow the full wp site in.  I have mail and autodirect A records in the publicdomain.org on my local DNS server.
0
footechCommented:
If you have a blank (same as parent) A record in the "publicdomain.org" zone which points to the same IP as the www record, then there shouldn't be anything more to do with DNS.

At this point I would do a network capture when browsing to the site from outside your network, and then compare it to a capture performed while inside your network.  You can see if other DNS queries are being made, any problems, redirects, etc.

It's for reasons like this (and others) that I don't recommend setting up any sites on just somedomain.org, but instead always use www.somedomain.org.
0
sksaathoffAuthor Commented:
I also tried reversing the DNS entries, creating an A record that pointed to the pubic IP (replacing the www record) and then creating a CNAME record with "www."  I got the same result.  I could get to the server without using "www" but got only the "pageok" in the upper left hand corner of the web page.
0
sksaathoffAuthor Commented:
How would you recommend I go about doing the network capture?  Apologies, but I'm a "general I.T." person, not a networking expert.
0
footechCommented:
I just did a google search for "wordpress pageok" and got a bunch of hits, particular in combination with GoDaddy.  You might want to peruse those.  GoDaddy and Wordpress is not in my wheelhouse.  Are you sure everything is working fine outside of your network?  BTW, you should also be able to test inside your network, just configure your machine to use an external DNS server (like 8.8.8.8) instead of your internal one.  The results I browsed indicated it was often a configuration problem with GoDaddy, and so would be independent of your internal network.

In regards to a network capture, you need to install a capture program like Wireshark or MS's Network Monitor or Message Analyzer.  Start the capture, browse to the site, stop the capture, then examine the results.  However, examining the results from a network capture takes some practice.  You can filter the results and so forth, but you kind of need to know what you're looking for.
0
sksaathoffAuthor Commented:
When I reversed the DNS entries, that took care of it.  The pictures load fine now.  I think they just loaded slowly.
0
sksaathoffAuthor Commented:
Reversing the DNS entries was an idea I came up with and would provide a solution to others.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
DNS

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.