DNS Resolving Issues

Hello All,

I'm running Novell OES Netware v6.8. I have three servers connected to the network - one of these servers is also connected to the Internet to provide outside access. Another server is supposed to be providing my internal DNS (using NAMED.nlm).

Our school's website is hosted through Network Solutions (for about a month now, before that it was hosted internally using Apache on the Internet connected server). WebAccess is hosted internally on the same server doing DNS. The DHCP server gives out 3 DNS addresses, the first is my internal DNS server, the other 2 are the public DNS servers provided to me by Cablevision (my ISP).

When my desktops (all Windows XP) connect to the Internet they do so through Webroot's Desktop Web Proxy (DWP) and they connect to any site just fine. However, I have other devices (iPad's & Mac's) that connect to the Internet without using the Webroot DWP and they cannot connect to our website. They can connect to any other website, and they can connect to my Internal Web Access just fine. If I use the backdoor address to my website (that Network Solutions provided to me) I can access the page just fine. But any time any of these devices try to access my site through its domain name it fails.

My initial guess is that there is something left over in the system from when the site was hosted internally, but I've looked everywhere (that I know of) and cannot find the problem. (Its worth noting that the original internal web server is still up and running and if I go to the internal IP address of the old web server, and old version of my website comes up, just like it used to - this would lead me to believe that the problem isn't that they website address is still resolving to the old IP address).

In order to access the website, the address is www.mydomainname.org - in order to access Novell Web Access, the address is webaccess.mydomainname.org - could the problem stem from the fact that they have the same domain name... in which case I dunno what to do...

I hope this makes sense and you can help - if there are any questions, feel free to ask.

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.

If your internal systems use the same domain internally and externally, update the internal Record for www.yourdomain.com pointing to the external referenced IP. Unfortunately the only thing/way to deal with domain.com  is configure your apache server with a redirect to www.domain.com
Under no circumstances have your domain.com pointing to the external IP nor CNAME to anything as a CNAME of the root could create a huge problem for your setup.
jstonendAuthor Commented:
Arnold - Can you explain how to do the step with Apache? Also, I really don't understand the last sentence in your response...
I've not used netware
Try the following, in your DNS change the www record to point to the external IP.
I do not know whether netware relies on the domain.com reference, if it does not, you can point it to the External IP.
If it does, on apache, you would use a Redirect.

Looking back, it seems I dove into an AD setup rather than sticking with the netware setup that you have.

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
jstonendAuthor Commented:
Sorry for forgetting about this string... anyway, I have the problem solved.

It seems because the internal domain was the same as the external. Since my external website is hosted by Network Solutions, they were able to provide another address for me to use (the address I connect to with my ftp). Their DNS servers point the www address to this new address.

So, in my DNS setup inside my network I created a CNAME record what point www to the "private" domain name that they gave me.

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

From novice to tech pro — start learning today.