Re: [SLUG] Verisign Annoyance?

From: Eben King (eben1@tampabay.rr.com)
Date: Fri Sep 26 2003 - 14:39:41 EDT


On Fri, 26 Sep 2003, Ian Blenke wrote:

> Eben King wrote:
> > I'm toying with the idea of adding a null route to 12.158.80.10
> > (sitefinder.verisign.com). I think that would give a different error ("no
> > route to host" or some such) than a typo would ("host not found" or some
> > such). Problem 1, would that work? and problem 2, how would I do that?
> > The first guess for the method would be to add it using a "route" command
> > in rc.local . But would that route stay if I brought interfaces down and
> > up?
> >
> > My second guess is to trawl /etc for the word "route" and see where that
> > leads. Ideas?
>
> On a RedHat <9.0 box, I believe you add something like this to your
> /etc/sysconfig/static-routes file:
>
> eth0 host 64.94.110.11 reject

Yup, that's me. Thanks.

Has Verisign taken out the offending entries? Or is the nameserver I use
"broken"? I'm getting actual "host not found" errors from Proxomitron
and Junkbuster, on otherwise-normal setups.

Also, I see 64.94.110.11 is sitefinder-idn.verisign.com. . How is that
related to sitefinder.verisign.com ?

-- 
-eben    ebQenW1@EtaRmpTabYayU.rIr.OcoPm    home.tampabay.rr.com/hactar

"You're one of those condescending Unix computer users!" "Here's a nickel, kid. Get yourself a better computer" - Dilbert.

----------------------------------------------------------------------- This list is provided as an unmoderated internet service by Networked Knowledge Systems (NKS). Views and opinions expressed in messages posted are those of the author and do not necessarily reflect the official policy or position of NKS or any of its employees.



This archive was generated by hypermail 2.1.3 : Fri Aug 01 2014 - 19:03:17 EDT