[NTLUG:Discuss] DNS help

[Chris Cox]

Okie Dokie...

The domain is friscobible.com.  You can get the name servers
from that.  You can do a zone transfer from the authoritative
name servers and see the correct address for www (and you'll
see other entries as well).  Query your own DNS for the www
address and you'll likely see a different address...if you see
the correct one (which happens from time to time), query a different
name server... or query one of the roots.

The wrong address belongs to a machine that does not exist
anymore... in fact that range of IPs has been reassigned just
about a week ago.  The change to the new name servers at buz.net
happened approximately 5 weeks ago... change was made with
Network Solns.  The prior DNS of record at Network Solns was
216.91.201.103 and 104 (that being of course the bad IP as well).
Again, there is nothing on those IPs.. those machines were taken
completely down and now even their IPs have been reassigned.

Happy hunting... but in reality you didn't need to know all
of this to give hints... but sometimes going through the motions
is a good thing.

Let me know what you discover.

Regards,
Chris



Victor Brilon wrote:
> 
> Can you give out info about the domain name, who is supposed to be
> authorative for what, and what IPs are involved? That would certainly
> allow someone to diagnose the problems very quickly instead of trying
> to get at it via abstract descriptions.
> 
> Victor
> 
> On 05-Aug-2001 Chris Cox wrote:
> > The situation, my DNS authority for my domain has a record that
> > gets cached correctly on others DNS servers sometimes... but most
> > of the time, a different IP addressed gets cached... clear up
> > to the root... even though they all see my DNS provider as
> > being the authority for the domain.
> >
> > So occasionally, I see the right address in @home's DNS, and
> > sometimes the wrong one.
> >
> > My guess is that the other DNS is stating that it has authority
> > records for the domain.... and for whatever reason (TTL or
> > otherwise), most people end up caching the bad record instead
> > of the one coming from the true authority for the domain.
> >
> > Any clues... without having access to DNS records directly...
> > of how to track down the host that is causing the problem
> > in DNS??
> >
> > I have examined the DNS from our hoster... the records look
> > fine (requested a zone xfer to examine the records).  I have
> > found another site that claims to have authority
> > records (which is wrong of course), but their records
> > are fine, though redundant with ours.
> >
> > I have an outstanding call to Network Solns to help solve this
> > issue.  No one associated with the domain during its lifetime
> > remembers anyone else possibly having authoratative records
> > for the domain.
> >
> > The TRUE provider of DNS records for the domain, cleared out
> > all of their entries.  As one would expect, gradually DNS
> > servers deferred up the ladder until eventually it was
> > only cached at the root server level... then eventually
> > it did not show up at all (which is what you would expect
> > after TTL experiation).  That experiement did not reveal
> > anything to us.... so they put the records back in.  The
> > right address was cached correctly by some, then the
> > wrong address (the address is nowhere to be found in thier
> > DNS files btw) started getting cached again... sigh.
> >
> > How do I track down a site that is portraying bad records
> > of authority for my domain??
> >
> > Any thought or ideas?
> > Chris
> > _______________________________________________
> > http://www.ntlug.org/mailman/listinfo/discuss
> 
> --
> 
> Victor Brilon
> victor at vail.net
> http://www.victorland.com
> 
> Thought for the day --
> If trees could scream, would we be so cavalier about cutting them
> down?  We might, if they screamed all the time, for no good reason.
>     -- DEEP THOUGHTS by Jack Handey
> 
> _______________________________________________
> http://www.ntlug.org/mailman/listinfo/discuss