Re: DNS server resolved 64.106.154.50 to all domain name
From: Roger Abell (mvpNOSpam_at_asu.edu)
Date: 08/13/04
- Next message: RG: "Name servers"
- Previous message: Feng Mao: "RE: Connection DNS Suffix automation"
- In reply to: jmadd: "Re: DNS server resolved 64.106.154.50 to all domain name"
- Messages sorted by: [ date ] [ thread ]
Date: Fri, 13 Aug 2004 00:52:14 -0700
Jim,
Are you still with us ?
Based on the info Matt provided, you may be able to
resolve this by enabling protecting of the cache from
pollution (in the Adv tab of the server node properties),
and then using adv view so you can see the cache and
going in and highlighting and deleting the cached entry
for com.
However, I am doubting that this will resolve things.
The first poster showed us that ping got the bogus IP,
but nslookup using their DNS did not.
This tell me that the bad caching is happening not in
the DNS server but in the DNS caching resolver client.
You did not respond with the requested nslookup, so
we do not know if this is also how it is on your machines.
-- Roger Abell Microsoft MVP (Windows Server System: Security) MCSE (W2k3,W2k,Nt4) MCDBA "jmadd" <jmaddox@oaktreesys.com> wrote in message news:facc3982.0408100439.54cbf8a5@posting.google.com... > we are experiencing the same problem not all websites but the majority > will resolve to the same 64.106.154.50 ip. I was able to stop it for > a day our 2 by using a different cache.dns. The strange thing is that > I have 2 files and I just swap them and it works for awhile it almost > seems like the root hint servers are being spoofed very weird indeed. > > Jim Maddox > > > > "Kevin D. Goodknecht Sr. [MVP]" <admin@nospam.WFTX.US> wrote in message news:<ewJacrkdEHA.1692@tk2msftngp13.phx.gbl>... > > In news:74483CAA-95B1-4757-8D64-FD39E8BFA152@microsoft.com, > > Ravi <Ravi@discussions.microsoft.com> posted a question > > Then Kevin replied below: > > > Hi, > > > > > > Our DNS server is acting little funny. When we try to > > > resolve any domain name it resolves to 64.106.154.50. We > > > tried resinstalling dns server but no luck. Any > > > suggesation? > > > > It takes a combination of your DNS suffix matching a public domain that uses > > a wildcard record to do this. > > Usually if you deselect "Append parent suffixes of the primary DNS suffix" > > or select "Append these suffixes in order" with you local Domain suffix in > > the list only, it won't append the combination of suffixes to get the > > wildcard record. > > > > If when you run nslookup use the d2 switch you can see nslookup appending > > suffixes. > > > > Posting your ipconfig /all will verify this. > > > > > > -- > > Best regards, > > Kevin D4 Dad Goodknecht Sr. [MVP] > > Hope This Helps > > ============================ > > -- > > When responding to posts, please "Reply to Group" via your > > newsreader so that others may learn and benefit from your > > issue. To respond directly to me remove the nospam. from my > > email. ========================================== > > http://www.lonestaramerica.com/ > > ========================================== > > Use Outlook Express?... Get OE_Quotefix: > > It will strip signature out and more > > http://home.in.tum.de/~jain/software/oe-quotefix/ > > ========================================== > > Keep a back up of your OE settings and folders with > > OEBackup: > > http://www.oehelp.com/OEBackup/Default.aspx > > ==========================================
- Next message: RG: "Name servers"
- Previous message: Feng Mao: "RE: Connection DNS Suffix automation"
- In reply to: jmadd: "Re: DNS server resolved 64.106.154.50 to all domain name"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
