domain goof

  • Thread starter Thread starter Martin
  • Start date Start date
M

Martin

Ok where to start... When I built my companies internal
domain I called the domain name XXXXXXXXX.co.uk instead
of XXXXXXXXX.local. the problem is when internal people
want to look at/FTP to our web page XXXXXXXXXX.co.uk it
looks to our server instead of to the web. I would
imagine there is a setting where you get the server to
redirect the request to the web or to look at another IP
address. I'm lost and up to my neck in TechNet articles
and getting no where


The DC is also the Exchange server and DHCP/DNS server so
in rebuilding it I would be even more unpopular than I
already am
 
Just add a DNS entry on your internal DNS server which dishes up the IP
address of webserver on the internet. Then when they request
wwww.domain.co.uk they will hit the external site instead of your server.

Keep in mind DNS client keeps a cache on the PCs so either do a reboot or
ipconfig /flushdns when you have made the DNS update
 
I tryed that. that does work but useing a external DNS
server. But it means the internal network runs slow and
has a few problems. sorry.. do you have any other ideas..
I welcome anything
 
please descibe exactly how you are setting this up then testing it. It will
work.

After you have setup the DNS records on your DNS server, from a client
computer first clear the DNS cache then ping www.yourdomain.co.uk - does it
resolve to the correct external IP address.
 
When the users need to ftp, give them the ftp URL you defined in your
internal DNS server. Example ftp.domain.co.uk. In other words...add an "ftp"
pointer in DNS zone. You could also define www2 in DNS and use that. After
all, its just a pointer.

If your internal web uses the same pointer as the external web, then modify
the internal pointer and distribute the new pointer within the organization.
 
Back
Top