Find the answer to your Linux question:
Results 1 to 6 of 6
Greetings, Could someone help? Red Hat 2.4.24-31.9 I've just got our server set up and we have access to the net. The only thing we don't have is access to ...
Enjoy an ad free experience by logging in. Not a member yet? Register.
  1. #1
    Just Joined!
    Join Date
    Sep 2006
    Posts
    5

    domain non-existant


    Greetings,

    Could someone help?

    Red Hat 2.4.24-31.9

    I've just got our server set up and we have access to the net. The only thing we don't have is access to our domain. It's accessible from the outside world, just not within. Anyone have any clues?

    www.cecinet.com

    Any help would be greatly appreciated!

    Thank you.

  2. #2
    Super Moderator Roxoff's Avatar
    Join Date
    Aug 2005
    Location
    Nottingham, England
    Posts
    3,915
    I take it you mean you dont have access to your website?

    Is the website hosted inside your building on your own machines, or is it hosted by a hosting company?

    What happens if you do 'http://68.225.90.103'? (This is the IP address that DNS returns for that domain name).
    Linux user #126863 - see http://linuxcounter.net/

  3. #3
    Just Joined!
    Join Date
    Sep 2006
    Posts
    5
    Thanks for the reply.

    That's right. I do not have access to our website internally.

    However, I can access it by typing http://68.225.90.103 into the browser. The website is hosted on our machine.

    Thoughts?

  4. $spacer_open
    $spacer_close
  5. #4
    Just Joined!
    Join Date
    Sep 2006
    Posts
    5
    Ok, still no progress.

    an error from the boot.log file states:

    "Could not create INET socket on 127.0.0.1:783 - Address already in use"

    could this be the problem?

    Once again, the basic problem is that I cannot connect to our domain/website while inside our network.

  6. #5
    Super Moderator Roxoff's Avatar
    Join Date
    Aug 2005
    Location
    Nottingham, England
    Posts
    3,915
    The problem is that most routers/NAT systems wont let you go from an internal address on the LAN out to the external address.

    What you need to do is set up your own internal DNS machine so that www.cecinet.com resolves to the internal LAN IP address of the server rather than its external interface IP address.

    As far as your own domain goes, the view of that domain from inside the LAN will be different to the view from outside on the internet - a well configured DNS server on the LAN can make the change of perspective completely invisible.
    Linux user #126863 - see http://linuxcounter.net/

  7. #6
    Just Joined!
    Join Date
    Sep 2006
    Posts
    5
    I appreciate your responses Roxoff.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •