Dont know if this is relative. Basically dilberts_left_nut siggestion
When i run to the inconvienance of having to remeber two address, one for external and one for local then thats when i setup what they call split dns. i dont know if they call it that but it sounds good.
Local DNS is something like
External dns is something like
So being a puny host on the same (local) network as the webserver i cant use the external domain name due to some rule of the network gods that i cant think of way to explain, loops or something.
Like myself and so many im use to using the FQDN, mattch.com, i hated email.mattch.local or ip blah
So of course i go to my internal dns server, everyone has one right? lol
the internal DNS has one zone (shown above) mattch.local
so on the same dns server add a second zone, and call it mattch.com or your FQDN,
add records for the FQDN that corresponding local hosts addresses, ie
AAA: email.mattch.local > 10.1.1.2
AAA: webserver.match.local > 10.1.1.3
AAA: you get the picture!
AAA mail.mattch.com > 10.1.1.2
AAA (same as parent folder, MS DNS
) > 10.1.1.3
so know when you want mail.mattch.com on the same local network your local DNS serves you the webservers local IP
:devil: Alternativly you could change your FQDN dns to a local ip but forget about anyone outside accessing it
(dont really do that its my attempt to create some humor)
the network gods sent me a internal pm to talk about why you cant use external names in the same local network.
your webserver sits at home with you and your local PC's. You have port forwarding enabled for the webserver so the world can see it.. of course you can use internal IP to access the webserver from home, but the hell wants to do that since we pay 10$ for a FQDN?! so now we have a FQDN and when we are showing the website off at a friends house it looks awesome! but when we go home (where webserver is) and try that FQDN is doesnt work... hmm. wtf you might ask, as i once did.
You query your fav DNS server for your new FQDN to view your website from the same local network the website resides on. the query is sent out yer router to the dns server, the dns server says HEY! that FQDN IP is 220.127.116.11, you say ok thats cool i know address is my WAN interface on my router. so now your request is leaving the LAN and then comming back to the LAN, most NAT implementations dont allow this, before you say that i am a liar, the cheapo linksys and soho routers know about this and do something unknown to me to make it work, has somethign to do with IP and Port numbers and some intelligence. i lack all 3
Workaround setup local dns server with FQDN zone pointing to local ip's
Im sure my explaination is unorganized and confusing but hopefully it will shed a ray of light.