On Tue, Oct 07, 2003 at 11:28:34AM -0700, Crist Clark wrote: ==>Jared Mauch wrote: ==>> ==>> I've reported it to them in the past and their IT ==>> folks can't seem to get it fixed :( ==> ==>In BIND logs too, but if I do the check now, they both seem to be returning ==>authoritive records. But also note, ==> ==> $ host sjce-dirty-ddir.cisco.com ==> sjce-dirty-ddir.cisco.com has address 128.107.240.86 ==> sjce-dirty-ddir.cisco.com has address 172.17.153.22 ==> ==>Uhhh... Hello? 172.17.153.22? 172.16.0.0/12, RFC1918? We fixed most of this problem when Jared reported it, but it appears all hasn't been changed. Some configuration entries were missed in the distributed directors. ns1.cisco.com/ns2.cisco.com have the correct nameservers but the distributed director has the old values. I've forwarded the info and it will be fixed accordingly. /cah -- Craig A. Huegen, Chief Network Architect C i s c o S y s t e m s IT Transport, Network Technology & Design || || Cisco Systems, Inc., 400 East Tasman Drive || || San Jose, CA 95134, (408) 526-8104 |||| |||| email: chuegen@cisco.com CCIE #2100 ..:||||||:..:||||||:..