Wanting to place my hosted web on my server

Discussion in 'DNS Server' started by Mark, Oct 11, 2005.

  1. Mark

    Mark Guest

    Wow..I see all the xperts here and I am amazed. Heres the deal.
    1. I have www.mydomain hosted at IPOWERWEB
    2. I have a new server, I can ping and all that..
    3. I have made it an application role
    4.Under Admin tools, Iwent to DNS and started by local server / forward look
    up zones, there are 2 areas with +. the 1st is _msdcs.xxxx.xx(my stuff)Do I
    create a CNAME here under domains?
    5. the second + is XXX.XX(my stuff, and under it is domain.dns.zones. Is
    THIS where I make a CNAME.
    6.When it asks for a FQDN do I only put www.mydomain.com in there(whereever)
    &. The goal is to move www.mydomain from Ipoerweb to my server and be able
    to type www.mydomain.com and have it read the web I made off my own server.
    9. Don't fall down laffing to hard. iIhave come a long way to this point. I
    set up FTP(new for me).
    10. I have NOT configured my router for web yet, I assume that comes to..
    11. Help from you Big Guns is very much apprecuaited. I'm sure I will have
    MUVHO follow up. Thanks in advance.
     
    Mark, Oct 11, 2005
    #1
    1. Advertisements

  2. Under your Forward Lookup Zones, rt-click your "mydomain.com" zone name,
    select new Host record, type in www, provide the IP of the webserver.

    Do not alter the SRV records, since they are for domain functionality. If
    altered, depending on what you've changed, you may compromise AD's
    functionality.

    If the webserver is on a domain controller, you may need to forget using the
    http://mydomain.com version of connectivity (without the www portion)
    because that record, which is called the LdapIpAddress and looks like:
    "(same as parent) A 192.168.x.x", is also for domain functionality. In most
    cases, a stand alone machine is chosen for webservers as to not interfere
    with the DNS recordsAD functionality. As long as you don't care about not
    being able to connect without the www record, then you can go ahead and use
    the DC if that is all is available.


    --
    Ace

    This posting is provided "AS-IS" with no warranties or guarantees and
    confers no rights.

    If this post is viewed at a non-Microsoft community website, and you were to
    respond to it through that community's website, I may not see your reply
    unless that website posts replies back to the original Microsoft forum.
    Therefore, please direct all replies ONLY to the Microsoft public newsgroup
    this thread originated in so all can benefit or ensure the web community
    posts it back to the original forum.

    Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSE+I, MCT, MVP
    Microsoft Windows MVP - Windows Server - Directory Services
    Microsot Certified Trainer
    Infinite Diversities in Infinite Combinations.
    =================================
     
    Ace Fekay [MVP], Oct 12, 2005
    #2
    1. Advertisements

  3. Mark

    Mark Guest

    Wow, Thanks for your replay.

    I am studying as hard as I can while waiting for some expert help like
    yourself. this is where I am.

    I went under lacal server, and "added a new web" it is set for port 80" I
    FTP'ed all my files there and when I hit browse on the index file, I can
    actually see the web work.

    This server has IIs on it and I gave it a role of application server. We
    have already learned how to log in remote and FTP.

    What would be my next prelimanary steps to get my hosted www.mydomain, off
    of my host and when you or I type www.mydomain it would begin to read it off
    of MY server rather then my host?

    I am seeing recommendations that that is not a good idea. But this is not
    going to be a sight that 1000's of people are going to hit. Just a few a day.

    SO... what do I say to my host holder. And what are the next diectional
    thing I need to set up under w2k3 to point there?

    Should I be working under DNS at all? Cause under Local server in DNS, I
    only see the server names and the tcp points to the correct 192.....

    Still a bit lost. Bottom line. I made a new web, and I can browse it in the
    server.

    You guys are great.
     
    Mark, Oct 12, 2005
    #3
  4. In
    Thanks for the plug. :)

    Ok, let me get this straight, you want to host your website on your
    Windows2003 server for the public off of your cable or DSL line? Do you want
    to host DNS too? What kind of line do you have?

    Ace
     
    Ace Fekay [MVP], Oct 13, 2005
    #4
  5. Mark

    Mark Guest

    I have a small Dell server. It has remote access. I just want people to type
    www.mydomain.com and have it on my server rather then having it hosted. I
    think the DNS wuestion is no. I made a sight I ipload the page, I can browse
    it from within the server. BUT. It is still hosted at another place. How do I
    turn it off there and point it to me? Other then Makeing the site with "Make
    web site, port 80, all assigned IP's, did, I miss something?. Yes I am a
    beginner on servers, But, I made one heck of a page and am great with PC's.
    Just not a lot of help out there on servers and w2ks. Just need some more
    pointers. Of course I see a lot of recommedations to NOT host my own web.
    But, I would like to try. I aked some questions before that I believe do not
    apply.. Summary, I created a site in IIS and assigned port 80, all assigned
    IP's , gave it my name(www.) now. pointing suggestions.

    You guys are still the best to take your valuable time to help the newbies.

    Mark
     
    Mark, Oct 13, 2005
    #5
  6. Mark

    Mark Guest

    Business Class DSL...

     
    Mark, Oct 13, 2005
    #6
  7. Mark

    Charlie Tame Guest

    Once you are hosting a website on your own machine you will have to think
    twice before playing games that require reboot to clean up afterwards and
    all that - else your site will quickly become unpopular :)

    Better to get a spare machine and run it on that, even an old and slower
    one. Speed only comes into it if you have a lot of concurrent users and even
    then unless you are doing much server-side scripting it should be tolerable.

    I started a website here on an old Compaq 350 MHz machine (to see how
    quickly it got hacked :) You should be able to see it I think.
    http://12.216.107.56/ There is no need to register the domain just to see it
    via the net. There really is not "That much" difference between a "Server"
    and an ordinary "Client Peer" at this level.

    Of course that is not a fixed IP, which does not matter to me at all, but
    you need a business deal with the ISP to get a fixed IP if you intend to
    register the domain - you can't register a random IP - and you also need to
    nominate name servers to do it properly.

    I can't help with DNS issues much, I'm here to learn from folks like Ace
    just as you are, but I can tell you there are benefits to having someone
    else take the responsibility for hosting - you have to weigh up how much you
    want to "Dedicate" your machine to the rest of the world :)

    Sorry if this is not 100% on topic, just passing on what I learned,
    otherwise go for it. Learning is always good.

    Charlie
     
    Charlie Tame, Oct 13, 2005
    #7
  8. Mark

    Mark Guest

    Nope, It is a business web site, that very very few, would log into, It is a
    stand alone server with no games. Just Quickbooks. I want my business website
    to be on it. It is hosted by another company. I am afraid to have them
    transfer it to my 192...., because I am not sure I have done everything
    needed. Like I said. from IIS I made a new site, opened port 80, chose all
    assigned IP's, now is there something else needed, before I have my host
    point this at my IP? Could it be that simple. There will not be more then 1
    or 2 hits a day. Thats why I see no need for hosting outside. I do not need
    to reboot. If I do, I'm right there. AM I done????

    Thanks in advance to you wizards.

    mark
     
    Mark, Oct 13, 2005
    #8
  9. Mark

    PeterD Guest

    Let's say you are talking your ISP. Your IP with them is what they
    will use. Let's say you have a ADSL line. Your modem connects to them
    (the ISP) through the phone line. The modem probably contains a basic
    router, and this is assigned the IP address for your Internet IP. The
    output of the router is typically NAT'ed to your 192 range. There's a
    firewall in there, too.
    I know what you mean, you're sure something won't work, but don't know
    On a local server wiht a 192 IP? That is then going through your NATed
    Router? If yes, then the router/NAT box must forward port 80 to the
    correct IP address--the address of your web server.
    Yep, make sure that the router/NAT (and firewall if it is built in)
    point port 80 to the correct server in your business. Make sure that
    if that server has a firewall running (such as the one in
    Windows/Windows Server, or a third party software firewall) then also
    open port 80 in that one.

    You can test locally: from one machine try to open your 'new' web
    page. Use an IP address, or the server's local name. It shoudl open up
    if the server is configureed correctly.
    Probaably not... <g> but sometimes you have to just jump in and find
    the problems. Test the system locally first. If it doesn't work
    locally then it cannot work from outside. <g> (basic logic...) Get the
    local server setup to provide web pages locally first. Then have the
    ISP point things to your IP. Set your router/NAT/firewall to pass port
    80 to the correct server, adn you should be working.
     
    PeterD, Oct 14, 2005
    #9
  10. Mark

    Mark Guest

    Oh yeah, one more thing(oh sure just one right?) On Websites within IIS,
    under Web sites(header)/Directory service/Authentication and
    Service/Edit..should I have the Enable anonymous access checked with the
    efault in there or unchecked? I would assume that applies to the actual www.
    below in the tree too. Confusing you.? Man I'm missin a
    step...Locally...Hm,mmmm. I'm screwed ...up.
     
    Mark, Oct 14, 2005
    #10
  11. Mark

    Mark Guest

    All I can say is WOW again. You experts on servers are very kind. NOW, That
    answer leaves me with a couple more(7 or 8) questions(go figure).

    My server, with business ADSL(I guess) came with 5 static IP's.

    1.The server stands alone. (couple pc's on that nework)but the server, is
    not the ISP. Bellsouth is.
    2.The server connects to a modem and there is a Linksys wireless Router
    involved.
    3.I have logged into the router from here (remote) and opened port 21, when
    I set up the FTP. I used the 192.. address on the router page,. FTP works
    fine.
    4. While reading directions for setting up a web. I created the new
    web(create new) from IIS, and it configs automatically on the IIS at port 80,
    with all assigned IP's.
    5.I logged into the router and set app. web port 80, and assigned my
    192....(IS that what you mean forward to the correct IP?)
    6.NOW....What do you mean...(.NATed) and what do I look for to make sure
    that is taken care of?(Yep, make sure that the router/NAT (and firewall if it
    is built in)
    7.You can test locally: from one machine try to open your 'new' web
    OK... Not sure.. this should be simple. If I type in the 192...,that says
    no.. if I type in one of the 5 static ip's that says no. That tells me I'm
    either doing that wrong, or I'm not getting the clue. How do I test locally?
    Ya see, I can log into the server, go to the directory, where the web is,
    browse the index file and Voila' it works. But, I can't get the web to just
    open up, from remote or the pc that is inline(same workgroup.)

    OK, I'm NOT doing the local thing right. What did I miss? What should I be
    doing to check it locally. Are you saying when logged in and I type the
    192...the web should just flop open. or one of the 5 static..63.xx.xx.. Well
    I'm a failure. crap.

    I know I should get this. I can just tear into a PC, but, this one last
    thing is just killin me.

    Thanks for listening to this sob story. Feel free to give up, cause someday
    I'll figure out what's wrong.

    Thanks again

    Mark
     
    Mark, Oct 14, 2005
    #11
  12. Mark

    Charlie Tame Guest

    Quick answer to a couple of points, sorry, not all of them :)

    Let's guess your router is 192.168.0.1 and your other machines are
    192.168.0.10 and 100 respectively. They are name Fred and George.

    From inside the local network you would likely type in 192.168.0.1 to get to
    the router setup page. From outside the local network there may be some
    specific things you have to do so I can;t help there because I don't have
    one of those Linksys models.

    Now, if the FTP server is on Fred (10) you should be able to type in
    ftp://192.168.0.10 or FTP://Fred but from outside the net it will have to be
    ftp://xxx.xxx.xxx.xxx which is whatever your WAN IP address is. I think from
    what you said earlier any of the 5 IP addresses your ISP allocated will do
    that.

    NAT or network address translation is what the router does when that request
    for FTP hits it - it looks to see if it has a port allocated for FTP on any
    of the local machines and if it does it "Translates" the incoming WAN IP to
    the local network IP. It's really more complex but I think that will do for
    explanation.

    Now, if your webserver is on the same machine it will be http:// followed by
    the same as before from inside or outside the local net, but if it's on
    George then the local addresses will change to 192.168.0.100 and "George" as
    above. From outside though the IP will stay just the same, because the
    router will change the address to the local one which has been stored as the
    one with port 80 open. This is what port forwarding does.

    Again this is vastly oversimplified but your ISP is doing roughly the same
    thing in order to give you 5 IP addresses :)

    The "Proper" IP port addresses (21 and 80) are assumed by the use of ftp://
    and http:// but you could run the webserver on a different port - say 90, in
    which case the address to reach it would be http://xxx.xxx.xxx.xxx:90 and
    you would then HAVE to type the colon 90 part. So you could run 5 webservers
    on say xxx.xxx.xxx.xxx:80 (Default) :90, :100 etc if you wanted, or else you
    could replace the last xxx with your 5 IP addresses and use port 80 for all
    of them. It is as if the combination of address and port together make a
    complete address.

    Obviously these are only examples, not suggestions, and for your purposes I
    think simply using one IP with FTP webserver and mail might be the sensible
    option. I would also think all will run on the one machine, but once the
    domain is directed to your IP the router will sort out what goes to which
    port on any machine you choose.

    Anyway have fun, it's late and I don't think I screwed up anything but if I
    did I don't doubt it will be corrected :)

    Charlie
     
    Charlie Tame, Oct 14, 2005
    #12
  13. Mark

    Mark Guest

    I sure Thank you is not enough, but Thank you. I'm traveling today so I will
    start again when i get home. I think the part I was missing for the test was
    the :80 or :90 like you said. I only have the one so I will key in on
    George... Thanks so much for your time.

    Mark
     
    Mark, Oct 14, 2005
    #13
  14. Mark

    Mark Guest

    http://192.168.x.xx:80 does not work from outside or inside the server.
    ftp://192.168.x.xx:80 does not work from outside (from my pc)or in the
    server.(when logged in)

    ****Do I need the anonymopus box unchecked in all placesunder web. on IIS or
    leave the default username ans PW in. I didn't think I needed any forwarding
    stuff done.

    I guess I am doing something wrong or do not have it set up right yet. I
    hate to give up, I feel I'm so close. I'm sure I am confusing you,. Remember.
    One server. I connect remote. Or My son is on that network where the server
    is . One pc connected on the same workgroup. I log in via MSTSC and a 63.xx
    number.

    I think I read that I needed the :80.
     
    Mark, Oct 14, 2005
    #14
  15. In
    Mark,

    Just as an FYI, there's a great site with a bunch of tutorials at
    www.iisanswers.com for IIS how-tos, etc.

    Cheers!

    Ace
     
    Ace Fekay [MVP], Oct 14, 2005
    #15
  16. In
    What is the exact error you get in the webpage when you connect by
    http://192.168.x.xx:80 ?

    Port 80 is the default port for web services, meaning it automatically uses
    that for 80 when you type in a URL, unless you want to use a different port
    to keep it private, but the web site properties must match the port used in
    the browser.

    Keep the anonymous box checked, unless you want to keep it private and must
    log in to the site everytime you visit it. Leave the password for the
    anonymous account alone for now.

    As far as FTP, the default FTP port is 21, not 80. Since you stipulated 80
    for FTP, then the FTP service default port 21 will need to be changed to 80,
    but that will conflict with the HTTP service listening for requests for the
    website on port 80, and it will tell you so warning you not to do it when
    you attempt to set it. If you say yes, the service will not start because of
    the conflict. Each service needs a unique port number to identify itself.
    Does that make sense?

    Another method for unique website identification is the hostheader. That is
    the name you type in for the URL. It can be configured in the website
    properties, general tab, click on the Advanced button next to the IP address
    dropdown box. You can type in the name, such as www.domain.com, domain.com,
    and/or the IP address. If it's the only website machine, it will use the IP
    set on the machine, and the default port, but no hostheader. Hostheaders are
    a great method to host multiple websites with one IP address on the machine,
    and using only the default HTTP port. It identifies each website on the
    machine by it's hostheader. All webhosting companies do it this way, unless
    you want SSL, on the website, which requires a certificate and a unique IP,
    in addition to the hostheader.

    Here's a little about hostheaders:
    IIS TIPS - Host Header - What is it:
    http://msmvps.com/bernard/archive/2004/07/29/10855.aspx

    IIS Answers - How to create multiple websites with one IP address:
    http://www.iisanswers.com/Top10FAQ/t10-hostheaders.htm

    Using Host Headers to Allow for One I.P Address to Host Multiple Domains:
    http://www.4guysfromrolla.com/ASPscripts/PrintPage.asp?REF=/webtech/080200-1.shtml

    HOW TO Use Host Header Names to Configure Multiple Web Sites in Internet
    Information Services 5.0 (308163):
    http://support.microsoft.com/?id=308163



    In your case, it sounds like something is misconfigured assuming you didn't
    change the default ports. You mentioned earlier you installed DNS but wasn't
    sure what to do with it. Simply, under your zone name (like domain.com),
    make sure the machine name has either self registered or manually entered.

    For the resource records (www, etc), rt-click domain.com, choose new Host
    record. Type in www, and provide the same IP address. You can also create a
    blank record by rt-clicking, new host, keep the name box blank, and just put
    the same IP in. This allows you to connect by http://www.domain.com and
    http://domain.com (without the www). Both of these must match the website
    properties hostheader names. But this will only work on the private internal
    network, and not from the Internet. From the internet you would point to the
    router's outside IP address. To make the outside requests work bringing them
    to the webserver, yes, you must make a port remap rule allowing inbound port
    80 requests coming in on the outside interface (the 63.x.x.x number you
    mentioned), to go to the private 192.168.x.x or whatever IP it is of the
    machine. If you want to host if for all to see from the Internet, you must
    change the www address for your domain name to point to the outside IP of
    your router. This way you can connect by name, and not needing the IP. But
    if just for private use, then connect by IP.

    Or you can create an alias for the real machine name. If the machine name is
    'ralph' under domain.com, and ralph is already a host record created under
    the zone set with it;s own IP, then rt-click, new Alias (or CNAME), type in
    www for the name, and point it to ralph.domain.com.

    315982 - HOW TO Configure DNS Records for Your Web Site in Windows 2000:
    http://support.microsoft.com/?id=315982

    But more imporantly about DNS, in order for your own internal machine to use
    your own DNS server, and get to the website by name internally (only), you
    must ONLY set itself as the DNS address in it's IP properties, and no other
    DNS, or it may or may not use it if you mix numbers. If you have your ISP's
    DNS set in your IP properties, or getting it from DHCP somewhere (such as
    your router?), then it will never use itself. You have to set it to be a
    client of itself. As for DHCP, the machine should really have a static IP
    configuration.

    Read a little on how DNS works on the Internet in regards to domain names
    and their websites.

    IIS Answers - DNS basics for IIS Administrators:
    http://www.iisanswers.com/articles/dns_for_iis.htm

    I hope that sets you in the right direction.

    Ace
     
    Ace Fekay [MVP], Oct 15, 2005
    #16
  17. Mark

    Todd J Heron Guest

    "Ace Fekay [MVP]"
    Yup. Brett Hill is a great instructor. I actually attended his 3-day IIS
    5.0 course back in 2002. Speaking of courses, I'm co-teaching one up in
    Philly Nov. 28th. Maybe we can link up for a beer or two afterwards some
    night!
     
    Todd J Heron, Oct 15, 2005
    #17
  18. Actually all this depends on the modem type and if it is a also a router.

    Some modems are actually routers and the modem has an address of its own,
    This address is one of the /29 IPs you own, but not one of the 5 IPs you can
    use. Are you totally confused now?
    I wouldn't blame you if you are and what really confuses me as some ISPs
    have different setups from location to location, the last one I setup was a
    Netopia Model 3346N DSL Ethernet Switch Modem/router/firewall and I ended up
    calling Netopia to get it set up. You can usually tell which type of
    connection you have by using a web browser to connect to the Gateway IP for
    your /29 netblock

    Some modems don't have an IP you can connect to and just pass the IPs
    through to your NIC. With this type, if it goes to a cheapo router you can
    only use one of the five IPs you own. You can also use a Win2k or Win2k3
    server as your router, which allows you to use all 5 IPs you own.



    --
    Best regards,
    Kevin D. Goodknecht Sr. [MVP]
    Hope This Helps
    ===================================
    When responding to posts, please "Reply to Group"
    via your newsreader so that others may learn and
    benefit from your issue, to respond directly to
    me remove the nospam. from my email address.
    ===================================
    http://www.lonestaramerica.com/
    http://support.wftx.us/
    https://secure.lsaol.com/
    ===================================
    Use Outlook Express?... Get OE_Quotefix:
    It will strip signature out and more
    http://home.in.tum.de/~jain/software/oe-quotefix/
    ===================================
    Keep a back up of your OE settings and folders
    with OEBackup:
    http://www.oehelp.com/OEBackup/Default.aspx
    ===================================
     
    Kevin D. Goodknecht Sr. [MVP], Oct 15, 2005
    #18
  19. Mark

    Charlie Tame Guest

    "Ace Fekay [MVP]"
    Just like a phone extension identifies your desk... :) Hey Ace I have heard
    something that might be relevant here, not sure if it is true in my case or
    not. Basically that:-

    Some routers expect port 21 whatever the forwarding setting is and do not
    NAT FTP traffic correctly unless you use the default port. They will pretend
    to accept it but access from the WAN is not possible.

    I have el cheapo MS router which seems to suffer from this problem, although
    I suppose it could be that the IIS FTP server has a problem somehow with a
    "Routed or NATed" address. In any case the combination using port 2100 or
    21000 (for examples) gives at the other end the kind of failure one might
    see from bad authorization. Simply going back to 21 fixes this. IIRC even
    putting the machine in the DMZ and killing firewall etc did not help and I
    spent some time chasing non existent user ID problems.

    Lemme see... I found this site useful http://www.slacksite.com/ftp.html

    I guess a little OT but if this is what's happening I suppose it could
    appear to be a DNS problem too.

    Charlie
     
    Charlie Tame, Oct 15, 2005
    #19
  20. In
    I've never met Brett, but heard of him and commend him for his site. I think
    Randy Hinders helps him with that too. I've conversed with Randy in the past
    when I was running a webservice. Randy doesn't teach anymore, as far as I
    remember.

    Where will you be teaching in Philly? Let me know and we'll plan for those
    beers!

    Ace
     
    Ace Fekay [MVP], Oct 17, 2005
    #20
    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.