- Any DNS Experts Out There?
- Posted by Rick Bellefond on July 8th, 2003
I am running SBS 2000 with all of the service packs installed in order to
set up an environment to run Microsoft CRM.
Right now I have 1 server, 1 station, a Linksys router and am accessing the
internet through a cable modem.
I have an ISP that hosts our website which is www.rbdata.com
I setup up the DNS on my SBS to be rbdata.com to make the Exchange Server
setup easier when I get to that point.
If I try to access my website I get a message saying "Cannot find server"
and this happens from either the server or the workstation.
If without unplugging my router, I turn both my server off and workstation
off and then with the server still off I turn my workstation back on, I can
access my website. If I turn my server back on and then launch a second
instance of Internet Explorer from my workstation, I can still access my
website. If I go to my server, launch internet explorer and then try to go
to my website it comes back and says "cannot find server"
I think that I most likely just have a wrong DNS setting. Any ideas on how
to fix this?
Thanks.
Rick Bellefond
RB Data Services
- Posted by Brian Kurzynowski on July 8th, 2003
Add an entry into the forward lookup zone on your conputer for
www.rbdata.com and point it at your web site's ip.
Your problem is because while your server is on, it is your dns server, and
it has entries for the zone in question, so It dosen't forward the query up
the pipe, it just answers as host not found.
There may be other fixes that are more appropriate, but I'm not on my
network now and can't look. This should work however.
BK
"Rick Bellefond" <rick@rbdata.com> wrote in message
news:eEyTwDXRDHA.940@TK2MSFTNGP11.phx.gbl...
- Posted by Jamie Sachs on July 8th, 2003
Rick
You're most likely providing internal IP addresses via
DHCP and along with the DHCP data you're probably
assigning your internal DNS server to your network. Your
internal DNS server, which has a zone that is the same as
a public zone, is not resolving to your website because
you don't have an "A" record and a "CNAME" record
pointing to to real public address. You don't need to
call your internal zone rbdata.com, although I think I
understand why you did. You want to have one "face" on
your network and want your users to logon to "your"
domain whether at work or wherever. So if you want to
keep rbdata.com as your internal zone then you need to
make sure you've enabled Forwarding on the DNS server and
those forwarding DNS servers are public. If you do that
you don't need to add any "A" or "CNAME" records.
Jamie
- Posted by Rick Bellefond on July 8th, 2003
Brian,
Thanks for getting back to me.
Do I need to contact my isp to get my website's ip or is there a command
that will return the ip for a given website?
Once I have the IP do I just go into DNS from Administrative Tools and then
right click on rbdata.com under Forward Lookup Zone and select properties?
Then select Name Servers and then add my website's ip to the rbdata.com
entry? Thanks.
Rick Bellefond
RB Data Services
"Brian Kurzynowski" <briank@myspamfilter-taxfirm.com> wrote in message
news:%23U1n8QZRDHA.2768@tk2msftngp13.phx.gbl...
- Posted by Rick Bellefond on July 8th, 2003
Jamie,
Thanks for getting back to me.
So are you saying that once I have gone into DNS that I just need to right
click on my server and then select properties and then select the Forwarders
Tab and then add my website's IP to the Listen on portion of the screen?
Is there anything else that I need to do?
Thanks again.
Rick Bellefond
RB Data Services
"Jamie Sachs" <jsachs@1to1.com> wrote in message
news:03fa01c34599$657a42d0$a501280a@phx.gbl...
- Posted by Brian Kurzynowski on July 9th, 2003
Your web server's ip is 216.86.143.223
I ran an nslookup from a UNIX box. You can also run whois from a unix
command line, or go to checkdomain.com, or i think nslookup will work from
win2k and up command line.
good luck
"Rick Bellefond" <rick@rbdata.com> wrote in message
news:%23ch2TwaRDHA.2332@TK2MSFTNGP10.phx.gbl...
- Posted by Rick Bellefond on July 9th, 2003
Brian,
Thanks.
Someone gave me the following instructions:
************************************************** ***
You can not access your site that is hosted by your ISP.
Why is this happening? Well, if you named the domain of SBS 2000
"yourcompany.com" every request for this domain will resolved to the local
IP address of your server. In a default setup this is 192.168.16.2 and there
you will not find your website when it is running at your ISP. So, you have
to do something that it resolves to the IP address of the website.
1.. Go to Start/Programs/Administrative Tool/DNS
2.. Expand out the server name by clicking on the plus sign to the left of
the name
3.. Expand out Forward Lookup zones
4.. Right click on the company.com DNS zone and select New Host
5.. For the name enter "www" (without the quotes) , for the IP address you
will need to specify the IP address of where the web page is on the Internet
6.. Click the Add Host button
7.. Click the Done button after the pop up message that the record was
added
At this point you should be able to go to a command prompt and ping
www.company.com to at least have it resolve to the IP address.
************************************************** ****
This seems to make it so that I can now access my website from my
workstation but if I try to access it from my server I am still getting
"Cannot find server" and if I try to ping it from the server I get "Unknown
Host" This is definitely progress. Any other ideas as to how to get it so
that I can get rid of the conflict and access my website from my server?
Thanks.
Rick Bellefond
RB Data Services
"Brian Kurzynowski" <briank@myspamfilter-taxfirm.com> wrote in message
news:eQYLIdiRDHA.2188@TK2MSFTNGP10.phx.gbl...
- Posted by Brian Kurzynowski on July 9th, 2003
Set your server to use itself for dns resolution.
BK
"Rick Bellefond" <rick@rbdata.com> wrote in message
news:eNCVF1jRDHA.2460@TK2MSFTNGP10.phx.gbl...
- Posted by Rick Bellefond on July 9th, 2003
Brian,
How do I do that? Thanks.
Rick
"Brian Kurzynowski" <briank@myspamfilter-taxfirm.com> wrote in message
news:u%23pLRMkRDHA.1896@TK2MSFTNGP12.phx.gbl...
- Posted by Brian Kurzynowski on July 9th, 2003
in dns servers in tcpip properties on that network adapter
"Rick Bellefond" <rick@rbdata.com> wrote in message
news:uk6H4ckRDHA.560@TK2MSFTNGP10.phx.gbl...
- Posted by Robert Carrier on July 9th, 2003
You should have named your AD Domain company.local, and used dns to point
company.com requests to your interface. Using top level domain names for AD
Domain names creates problems, as you've seen.
On 7/9/03 4:13 PM, in article umY2LalRDHA.2768@tk2msftngp13.phx.gbl, "Brian
Kurzynowski" <briank@myspamfilter-taxfirm.com> wrote:
