Before you do anything with apache I would use nslookup

if you do this

nslookup yourregistereddomain.com

you should get back the ip address of your machine, then you should be able to access the webserver by that name.

also registration can take several hours before all the dns servers on the internet update their cache with you new name

I'm still having the same problem. I can go to https://192.168.0.x but not https://www.mydomain.com. Why can I do it locally but not through the domain name? This doesn't make any sense and has become extremly frustrating.

what ip address do you get from this

nslookup www.mydomain.com

Reading over this post it becomes obvious that you are unfamiliar with Internet addressing and naming.

Any IP address beginning with 192.168.XXX.XXX is unrouteable, meaning you cannot get to it from outside of it's own subnet. No router on earth will push packets along with that IP, so to answer your first question, yes you must bind it to your WAN ip.

DNS names are managed by a hierarchy of domain hosts. If you did not specifically register a domain and assign it an IP, noone on earth can find it(including yourself). A previous poster mentioned running your own DNS server. Doing this you could effectively replace www.google.com on YOUR OWN NETWORK. In order to resolve correctly you must register a domain to a specific IP

Well I am a bit unfamiliar with Internet addressing but my domain name is registered and working. I can go to http://www.mydomain.com but not https://www.mydomain.com but http://192.168.0.x works as well as https://192.168.0.x. The domain only works through the standard http protocol but not https.

Hey, what is the IP address that is assigned to your domain name. In other words, type (not including quotes) "ping www.mydomain.com" (which is actually your Domain name)


-What ip address responds? That is the IP that the domain points too, thus, that is where you need to make your conf. changes.


-BB