Guest Scott W Posted August 22, 2008 Posted August 22, 2008 couple of things: Windows server 2000 NIC tcp/ip protocol is assigned 4 different ip addresses? DHCP reserves these so as not to get assigned to clients I didn't set this up I can't really assign a host record (WWW) for the website: http://www.company.com because when i ping http://www.company.com OUTSIDE of the domain I just get the ip of the name server that's hosting the website. typing that ip address in an address bar resolves to a completly different website. I did assign a delegation to www that points to the nameserver. I tested by pinging http://www.company.com and it resolved the ip address of the name server. I pulled up http://www.company.com on IE and got to the website. NOW it doesn't work! pinging http://www.company.com (inside domain) is resolving to 192.168.1.129, one of the ip addresses assigned to tcp-ip. (we call this dhcp/dns server 192.168.1.20 the more "popular" of the 4 ip addresses) stupid split horizon.... Suggestions?
Guest Anteaus Posted August 23, 2008 Posted August 23, 2008 RE: DNS-Split horizon Try using nslookup to see what's actually going on here in terms of DNS lookups. It sounds as if some of the domain records are incorrect, but the first thing is to establish whether it's your internal DNS server or an ISP's one that's putting-out the wrong info. It may also be that the webserver is set to redirect a particular URL, which could be the reason for the different ping/browser behaviour. "Scott W" wrote: > I can't really assign a host record (WWW) for the website: > http://www.company.com > because when i ping http://www.company.com OUTSIDE of the domain I just get > the ip of the name server that's hosting the website. typing that ip > address in an address bar resolves to a completly different website.
Guest Scott W Posted August 25, 2008 Posted August 25, 2008 Re: DNS-Split horizon On Aug 23, 12:00 am, Anteaus <Ante...@discussions.microsoft.com> wrote: > Try using nslookup to see what's actually going on here in terms of DNS > lookups. It sounds as if some of the domain records are incorrect, but the > first thing is to establish whether it's your internal DNS server or an ISP's > one that's putting-out the wrong info. > > It may also be that the webserver is set to redirect a particular URL, which > could be the reason for the different ping/browser behaviour. > > > > "Scott W" wrote: > > I can't really assign a host record (WWW) for the website: > >http://www.company.com > > because when i pingwww.company.comOUTSIDE of the domain I just get > > the ip of the name server that's hosting the website. typing that ip > > address in an address bar resolves to a completly different website.- Hide quoted text - > > - Show quoted text - Interesting behaviour here OUTSIDE the domain: Authoritative = the IP address of our ISP NON-authoritative = the IP address of the Nameserver for our website INSIDE the domian: Authoritative = our DNS server NON authoritative = 4 IP addresses mentioned earlier & IP address of our ISP Aliases = http://www.company.com
Recommended Posts