On Fri, Nov 12, 2021 at 11:30 AM Stephane Bortzmeyer <bortzmeyer@nic.fr> wrote:
On Thu, Nov 11, 2021 at 09:44:04PM +0000,
 Richard <lists-nanog@listmail.innovate.net> wrote
 a message of 37 lines which said:

> The second of these is returning the 208.nnn IPnumber for your
> a-record:
>
>    dig @VOYAGER.VISER.NET 2dpnr.org
>
>    2dpnr.org. 300 IN A 208.91.197.132

It depends on where you are (from my resolver, I get
64.130.197.11). This is because the name voyager.viser.net is not
stable yet. Depending on your resolver, it points to 64.130.200.16 -
which seems to give correct answers - or to 208.91.197.132 - which
replies even for nonexisting domain names.

Lesson: don't use a name as an argument to dig's @


I think 208.91.197.132 (Network Solution's domain bucket) needs to go in everyone's troubleshooting notebook as a sign there is an expired domain somewhere affecting whatever you have going wrong. 

--
Jeff Shultz


Like us on Social Media for News, Promotions, and other information!!

       https://www.instagram.com/sctc_sctc/          







*** This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. E-mail transmission cannot be guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. The sender therefore does not accept liability for any errors or omissions in the contents of this message, which arise as a result of e-mail transmission. ***