Parent organization web site not accessible; their site uses an ip address within my DHCP scope.
Being relatively new here and not a frequent user - 500pts
A corporate website of another organization, which is somewhat like parent company, is using an ip address for their website that is within my DHCP scope, I've already excluded that ip from distribution.
Access to the external website is completely unavailable. (IE, pinging etc.)
What configuration would help me out in this situation. Do I configure DNS or the router so that users can access this site. I am definitely not an expert when it comes to DNS.
Were using, for the time being, a U.S. Robotics Broadband Router (Model # USR8000, Version V1.25), an upgrade to a Cisco 2621 will occur within a few months.
I'm using Win2K Server, DNS, DHCP, public IP addressing, no subnetting, ~50 computers, DNS forwarding, caching within DNS is also running.
I have only the single DNS server in our environment and will be adding another in the next 2-3 months, with the eventual goal of hosting both web and mail in-house.
Both organizations also share a wireless T1 connection.
Our organizations (oshki.ca) site is hosted third party (66.165.220.20) by hosting.knet.ca. I did add a host address (A) record to access our externally hosted web site.
KNET is an ISP both organizations use for mail or website site hosting.
The organization in question host its web site in house.
nan.on.ca (66.165.204.67)
If other information is required, I'll provide whatever may help.
Thank you,
Rob Wesley
A corporate website of another organization, which is somewhat like parent company, is using an ip address for their website that is within my DHCP scope, I've already excluded that ip from distribution.
Access to the external website is completely unavailable. (IE, pinging etc.)
What configuration would help me out in this situation. Do I configure DNS or the router so that users can access this site. I am definitely not an expert when it comes to DNS.
Were using, for the time being, a U.S. Robotics Broadband Router (Model # USR8000, Version V1.25), an upgrade to a Cisco 2621 will occur within a few months.
I'm using Win2K Server, DNS, DHCP, public IP addressing, no subnetting, ~50 computers, DNS forwarding, caching within DNS is also running.
I have only the single DNS server in our environment and will be adding another in the next 2-3 months, with the eventual goal of hosting both web and mail in-house.
Both organizations also share a wireless T1 connection.
Our organizations (oshki.ca) site is hosted third party (66.165.220.20) by hosting.knet.ca. I did add a host address (A) record to access our externally hosted web site.
KNET is an ISP both organizations use for mail or website site hosting.
The organization in question host its web site in house.
nan.on.ca (66.165.204.67)
If other information is required, I'll provide whatever may help.
Thank you,
Rob Wesley
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Moving to a private IP addressing scheme! I figured this would have to be done, I was just hoping for something easier and quicker.
With that said, I expect to have problems with AD and DNS (basically with the IP address change throughout the network), it wouldn't be a big issue for me demote our DC and start from scratch.
Would you recommend this route to avoid any potential problems?
With that said, I expect to have problems with AD and DNS (basically with the IP address change throughout the network), it wouldn't be a big issue for me demote our DC and start from scratch.
Would you recommend this route to avoid any potential problems?
Well, I've moved NT domains to a new IP scheme but I've never done it for AD. Perhaps someone out there could help.
But, for NT, Redoing IPS wasnt really a big deal. Schedule DHCP leases to expire over the next weekend. Come in and activate a new scope with the new IP's. Make sure you change IP's on DNS and WINS as well and do your best to test the new IP assignments.
The worst experience with the IP change was the WINS issue, but that souldnt be a problem with DNS.
Good luck
But, for NT, Redoing IPS wasnt really a big deal. Schedule DHCP leases to expire over the next weekend. Come in and activate a new scope with the new IP's. Make sure you change IP's on DNS and WINS as well and do your best to test the new IP assignments.
The worst experience with the IP change was the WINS issue, but that souldnt be a problem with DNS.
Good luck
If so, then you just have to reslove the name, and a hosts file on the clients will facillitate that