SirTKC
asked on
How do you point an external domain name to a server inside a "dot.local" domain?
Hi,
Here I am today as a writer!
My problem maybe simple to resove, maybe not...
I've just setup a "dot.local" domain within my network. Before it was a "dot.net" So, internaly it wasnt so hard for all internal computers to find the Webserver using the domain name used by the DNS. But since I've made that change no matter how I try to set the DNS forward lookup zones AND/OR Reverse lookup zones, the only way I can get to our web server is by using the internal IP address. If I use the original "dot.net" domain name, niet!
Also I have to mention that we are using a NO-IP service on these domains (2 actually) that points to our server inside Active Directory environnement.
Finally, my question; How can I make all internal "dot.net" request to point directly to our webserver when it is their absolute destination. (external request work just fine).
Here I am today as a writer!
My problem maybe simple to resove, maybe not...
I've just setup a "dot.local" domain within my network. Before it was a "dot.net" So, internaly it wasnt so hard for all internal computers to find the Webserver using the domain name used by the DNS. But since I've made that change no matter how I try to set the DNS forward lookup zones AND/OR Reverse lookup zones, the only way I can get to our web server is by using the internal IP address. If I use the original "dot.net" domain name, niet!
Also I have to mention that we are using a NO-IP service on these domains (2 actually) that points to our server inside Active Directory environnement.
Finally, my question; How can I make all internal "dot.net" request to point directly to our webserver when it is their absolute destination. (external request work just fine).
ASKER
Yes it is Windows SBS DNS
The DNS is resolving all external names in fact.
Lets work with exemples -> My network domain is "mydomain.local". Our hosted website have the domain "my-domain.net".
Our PDC and IIS resides in the same server on 192.168.0.1. So the A record configured in the FLZ are
my-domain Host(A) 192.168.0.1 -> (in the "net" folder within the mydomain.local)
Inside this folder (net/my-domain) I Also included
www Host(A) 192.168.0.1
NOTE: I am using a 3Com Gateway that does not support NAT. BUt this role can be handled by WinSBS2k3 I assume?
Thanks for your time spent on it :-)
The DNS is resolving all external names in fact.
Lets work with exemples -> My network domain is "mydomain.local". Our hosted website have the domain "my-domain.net".
Our PDC and IIS resides in the same server on 192.168.0.1. So the A record configured in the FLZ are
my-domain Host(A) 192.168.0.1 -> (in the "net" folder within the mydomain.local)
Inside this folder (net/my-domain) I Also included
www Host(A) 192.168.0.1
NOTE: I am using a 3Com Gateway that does not support NAT. BUt this role can be handled by WinSBS2k3 I assume?
Thanks for your time spent on it :-)
>> Yes it is Windows SBS DNS
>> The DNS is resolving all external names in fact.
OK, so is the 192.168.0.1 server also the one with DNS server running?
Do all your client systems (and the server) have this address as the primary DNS in TCP/IP config?
Cheers.
>> The DNS is resolving all external names in fact.
OK, so is the 192.168.0.1 server also the one with DNS server running?
Do all your client systems (and the server) have this address as the primary DNS in TCP/IP config?
Cheers.
ASKER
TCP Settings are all set to "obtain DNS server address automatically"
By doing a "ipconfig /all" at the cmd prompt on clients, we can see that 192.168.0.1 is recognised as the DNS server IP Add.
Also, I tricked the DNS this morning by adding the internal domain name and its relative internal IP Address by adding this string to the Hosts file on clients
192.168.0.1 my-domain.net
It worked! But I am still positive that its not the way to go.
By doing a "ipconfig /all" at the cmd prompt on clients, we can see that 192.168.0.1 is recognised as the DNS server IP Add.
Also, I tricked the DNS this morning by adding the internal domain name and its relative internal IP Address by adding this string to the Hosts file on clients
192.168.0.1 my-domain.net
It worked! But I am still positive that its not the way to go.
Go to your DNS Server and add a new Primary forward lookup zone of dot.net
Create a new host (A) Record of www and point its IPAddress to the Webserver
Now www.dot.net should resolve to the IPAddress you specified
To test it out once it is done do the following. Go to a Workstation, Go Start -- Run -- IPCONFIG /FlushDNS
Then open the web browser and go to www.dot.net is should open your webpage
Create a new host (A) Record of www and point its IPAddress to the Webserver
Now www.dot.net should resolve to the IPAddress you specified
To test it out once it is done do the following. Go to a Workstation, Go Start -- Run -- IPCONFIG /FlushDNS
Then open the web browser and go to www.dot.net is should open your webpage
ASKER
I think that we're getting there!
I followed 2hype recommendations and now I can go "www.dot.net" and reach the server. - it works.
But If we type "dot.net" we still have the same problem - we can't get to the our internal web site using our domain name.
Thanks for your precious help
I followed 2hype recommendations and now I can go "www.dot.net" and reach the server. - it works.
But If we type "dot.net" we still have the same problem - we can't get to the our internal web site using our domain name.
Thanks for your precious help
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thanks a zillion both!
Learning is as good as teaching, believe me!! :-)
Learning is as good as teaching, believe me!! :-)
is the DNS resolving host names at all? (even external ones? e.g. www.google.com?) what A records have you defined in the dns for the dot.net and dot.local zones?
Cheers.