Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.debian.user > #244182 > unrolled thread

cooperative.co.uk has address 127.0.0.1

Started byRichmond <richmond@criptext.com>
First post2022-01-18 14:50 +0100
Last post2022-01-18 21:30 +0100
Articles 15 — 13 participants

Back to article view | Back to linux.debian.user


Contents

  cooperative.co.uk has address 127.0.0.1 Richmond <richmond@criptext.com> - 2022-01-18 14:50 +0100
    Re: cooperative.co.uk has address 127.0.0.1 Greg Wooledge <greg@wooledge.org> - 2022-01-18 15:00 +0100
      Re: cooperative.co.uk has address 127.0.0.1 Cindy Sue Causey <butterflybytes@gmail.com> - 2022-01-18 15:50 +0100
      Re: cooperative.co.uk has address 127.0.0.1 Georgi Naplatanov <gosho@oles.biz> - 2022-01-18 15:50 +0100
      Re: cooperative.co.uk has address 127.0.0.1 Richmond <richmond@criptext.com> - 2022-01-19 15:10 +0100
        Re: cooperative.co.uk has address 127.0.0.1 Jonathan Dowland <jon+debian-user@dow.land> - 2022-01-19 15:20 +0100
          Re: cooperative.co.uk has address 127.0.0.1 Dan Ritter <dsr@randomstring.org> - 2022-01-19 16:00 +0100
            Re: cooperative.co.uk has address 127.0.0.1 Nicholas Geovanis <nickgeovanis@gmail.com> - 2022-01-20 02:00 +0100
              Re: cooperative.co.uk has address 127.0.0.1 Jonathan Dowland <jon+debian-user@dow.land> - 2022-01-20 11:00 +0100
                Re: cooperative.co.uk has address 127.0.0.1 David Wright <deblis@lionunicorn.co.uk> - 2022-01-20 17:40 +0100
    Re: cooperative.co.uk has address 127.0.0.1 piorunz <piorunz@gmx.com> - 2022-01-18 16:00 +0100
      Re: cooperative.co.uk has address 127.0.0.1 "Andrew M.A. Cater" <amacater@einval.com> - 2022-01-18 16:10 +0100
        Re: cooperative.co.uk has address 127.0.0.1 Richard Hector <richard@walnut.gen.nz> - 2022-01-19 20:50 +0100
          Re: cooperative.co.uk has address 127.0.0.1 John Crawley <john@bunsenlabs.org> - 2022-01-20 02:40 +0100
    Re: cooperative.co.uk has address 127.0.0.1 Thomas Hochstein <thh@thh.name> - 2022-01-18 21:30 +0100

#244182 — cooperative.co.uk has address 127.0.0.1

FromRichmond <richmond@criptext.com>
Date2022-01-18 14:50 +0100
Subjectcooperative.co.uk has address 127.0.0.1
Message-ID<DGX22-7Os-5@gated-at.bofh.it>
Why do I see this?

host cooperative.co.uk
cooperative.co.uk has address 127.0.0.1

host cooperative.co.uk 1.1.1.1
Using domain server:
Name: 1.1.1.1
Address: 1.1.1.1#53
Aliases: 

cooperative.co.uk has address 127.0.0.1

cat /etc/hosts|grep -i coop

This has nothing to do with debian other than that I am using debian,
but I am not sure where else I would ask.

[toc] | [next] | [standalone]


#244183

FromGreg Wooledge <greg@wooledge.org>
Date2022-01-18 15:00 +0100
Message-ID<DGXbI-7RQ-3@gated-at.bofh.it>
In reply to#244182
On Tue, Jan 18, 2022 at 01:19:58PM +0000, Richmond wrote:
> Why do I see this?
> 
> host cooperative.co.uk
> cooperative.co.uk has address 127.0.0.1

Because whoever set up that DNS zone made an error.

unicorn:~$ host cooperative.co.uk
cooperative.co.uk has address 127.0.0.1

[toc] | [prev] | [next] | [standalone]


#244188

FromCindy Sue Causey <butterflybytes@gmail.com>
Date2022-01-18 15:50 +0100
Message-ID<DGXY5-8ns-1@gated-at.bofh.it>
In reply to#244183
On 1/18/22, Georgi Naplatanov <gosho@oles.biz> wrote:
> On 1/18/22 15:49, Greg Wooledge wrote:
>> On Tue, Jan 18, 2022 at 01:19:58PM +0000, Richmond wrote:
>>> Why do I see this?
>>>
>>> host cooperative.co.uk
>>> cooperative.co.uk has address 127.0.0.1
>>
>> Because whoever set up that DNS zone made an error.
>>
>> unicorn:~$ host cooperative.co.uk
>> cooperative.co.uk has address 127.0.0.1
>
> I have seen local-link IPv6 addresses as well :)


It's only been once or twice, but I've seen it, too. Pondered it for a
few seconds each time then a-sumed it was somehow tied to the other
end running their own server. The afterthought problem with it is the
inevitable collision with others (obviously) doing the same across the
Web.

Cindy :)
-- 
Cindy-Sue Causey
Talking Rock, Pickens County, Georgia, USA
* runs with birdseed *

[toc] | [prev] | [next] | [standalone]


#244190

FromGeorgi Naplatanov <gosho@oles.biz>
Date2022-01-18 15:50 +0100
Message-ID<DGXY5-8ns-3@gated-at.bofh.it>
In reply to#244183
On 1/18/22 15:49, Greg Wooledge wrote:
> On Tue, Jan 18, 2022 at 01:19:58PM +0000, Richmond wrote:
>> Why do I see this?
>>
>> host cooperative.co.uk
>> cooperative.co.uk has address 127.0.0.1
> 
> Because whoever set up that DNS zone made an error.
> 
> unicorn:~$ host cooperative.co.uk
> cooperative.co.uk has address 127.0.0.1

I have seen local-link IPv6 addresses as well :)

Kind regards
Georgi

[toc] | [prev] | [next] | [standalone]


#244212

FromRichmond <richmond@criptext.com>
Date2022-01-19 15:10 +0100
Message-ID<DHjFg-4IP-1@gated-at.bofh.it>
In reply to#244183
Greg Wooledge <greg@wooledge.org> writes:

> On Tue, Jan 18, 2022 at 01:19:58PM +0000, Richmond wrote:
>> Why do I see this?
>> 
>> host cooperative.co.uk
>> cooperative.co.uk has address 127.0.0.1
>
> Because whoever set up that DNS zone made an error.
>
> unicorn:~$ host cooperative.co.uk
> cooperative.co.uk has address 127.0.0.1

Thanks for your reply and others.

It doesn't seem like an appropriate use of the address to me, and I
stared in disbelief when I saw it, thinking something had gone wrong.

Even, for example, example.com has its own ip address. Or perhaps they
should have returned an error like an.invalid. I guess they want to
discourage its use but also prevent anyone grabbing it.

[toc] | [prev] | [next] | [standalone]


#244213

FromJonathan Dowland <jon+debian-user@dow.land>
Date2022-01-19 15:20 +0100
Message-ID<DHjYB-54D-1@gated-at.bofh.it>
In reply to#244212
On Wed, Jan 19, 2022 at 01:36:30PM +0000, Richmond wrote:
>It doesn't seem like an appropriate use of the address to me, and I
>stared in disbelief when I saw it, thinking something had gone wrong.

This is unlikely to be an explanation for cooperative.co.uk, but it used
to be fashionable to register a vanity domain, set an A record to
127.0.0.1, set the AAAA record to a valid IPv6 address from which you
connect to an IRC network, set the AAAA rdns record to match, and then
you appear on IRC as your chosen vanity host. If you get into an
argument with someone on IRC (perhaps more common for the types of
people who go about setting this up) and the other end decides to packet
flood you, if they aren't careful they'll direct their packet cannons at
127.0.0.1.


-- 
Please do not CC me for listmail.

👱🏻	Jonathan Dowland
✎	 jmtd@debian.org
🔗	https://jmtd.net

[toc] | [prev] | [next] | [standalone]


#244218

FromDan Ritter <dsr@randomstring.org>
Date2022-01-19 16:00 +0100
Message-ID<DHkBk-5hR-1@gated-at.bofh.it>
In reply to#244213
Jonathan Dowland wrote: 
> On Wed, Jan 19, 2022 at 01:36:30PM +0000, Richmond wrote:
> > It doesn't seem like an appropriate use of the address to me, and I
> > stared in disbelief when I saw it, thinking something had gone wrong.
> 
> This is unlikely to be an explanation for cooperative.co.uk, but it used
> to be fashionable to register a vanity domain, set an A record to
> 127.0.0.1, set the AAAA record to a valid IPv6 address from which you
> connect to an IRC network, set the AAAA rdns record to match, and then
> you appear on IRC as your chosen vanity host. If you get into an
> argument with someone on IRC (perhaps more common for the types of
> people who go about setting this up) and the other end decides to packet
> flood you, if they aren't careful they'll direct their packet cannons at
> 127.0.0.1.

It was also fashionable for a while to set up names like ftp.warez.org 
and point them to 127.0.0.1. 

"They look OK, but they only have stuff I already have."

-dsr-

[toc] | [prev] | [next] | [standalone]


#244226

FromNicholas Geovanis <nickgeovanis@gmail.com>
Date2022-01-20 02:00 +0100
Message-ID<DHtXY-2zm-1@gated-at.bofh.it>
In reply to#244218

[Multipart message — attachments visible in raw view] — view raw

On Wed, Jan 19, 2022, 8:51 AM Dan Ritter <dsr@randomstring.org> wrote:

> Jonathan Dowland wrote:
> > On Wed, Jan 19, 2022 at 01:36:30PM +0000, Richmond wrote:
> > > It doesn't seem like an appropriate use of the address to me, and I
> > > stared in disbelief when I saw it, thinking something had gone wrong.
> >
> > This is unlikely to be an explanation for cooperative.co.uk, but it used
> > to be fashionable to register a vanity domain, set an A record to
> > 127.0.0.1, set the AAAA record to a valid IPv6 address from which you
> > connect to an IRC network, set the AAAA rdns record to match, and then
> > you appear on IRC as your chosen vanity host. If you get into an
> > argument with someone on IRC (perhaps more common for the types of
> > people who go about setting this up) and the other end decides to packet
> > flood you, if they aren't careful they'll direct their packet cannons at
> > 127.0.0.1.
>
> It was also fashionable for a while to set up names like ftp.warez.org
> and point them to 127.0.0.1.
>

I hate to douse the party, but all 127.0.0.0/8 addresses are defined to be
loop back. So no network interface card or network stack on top of it
should write anything to the wire or air to that address.

It's just bored system administrators :-)

"They look OK, but they only have stuff I already have."
>

When I figured this out LMFAO :-D

-dsr-
>
>

[toc] | [prev] | [next] | [standalone]


#244230

FromJonathan Dowland <jon+debian-user@dow.land>
Date2022-01-20 11:00 +0100
Message-ID<DHCoy-7Mj-1@gated-at.bofh.it>
In reply to#244226
On Wed, Jan 19, 2022 at 06:50:06PM -0600, Nicholas Geovanis wrote:
>I hate to douse the party, but all 127.0.0.0/8 addresses are defined to be
>loop back. So no network interface card or network stack on top of it
>should write anything to the wire or air to that address.

…that's entirely consistent with what we wrote. That's the entire point
of the setup I described.


-- 
Please do not CC me for listmail.

👱🏻	Jonathan Dowland
✎	 jmtd@debian.org
🔗	https://jmtd.net

[toc] | [prev] | [next] | [standalone]


#244236

FromDavid Wright <deblis@lionunicorn.co.uk>
Date2022-01-20 17:40 +0100
Message-ID<DHIDE-3eB-5@gated-at.bofh.it>
In reply to#244230
On Thu 20 Jan 2022 at 09:50:01 (+0000), Jonathan Dowland wrote:
> On Wed, Jan 19, 2022 at 06:50:06PM -0600, Nicholas Geovanis wrote:
> > I hate to douse the party, but all 127.0.0.0/8 addresses are defined to be
> > loop back. So no network interface card or network stack on top of it
> > should write anything to the wire or air to that address.
> 
> …that's entirely consistent with what we wrote. That's the entire point
> of the setup I described.

Agreed, …

> > It's just bored system administrators :-)

… and I can't see just how that would alleviate their boredom.

But nobody here has said what cooperative.co.uk pointed to in the past,
if anything. My own relationship with the Coop (bank¹/shopping/divi)
ceased before I started using the internet for personal business, so
it's not something I could look up on old correspondence, stationery etc.

I did wonder if it might ever have pointed to the banking arm of the
Coop, back in the days when the "Coop bank" was part of the Coop. If
that were so, they might want to "sanitise" the domain for a long
period of time rather than have people fetch up at either the Coop
proper, or the now completely separate "Co-operative Bank".

That kind of sanitisation would contrast with, say, the way in which
lloydstsb.co.uk gets treated. Here, the old domain is still
functionally identical to lloydsbank.co.uk even though the TSB part
of Lloyds TSB was spun off years ago into tsb.co.uk.

¹ Their selling point back in the 1980s was free current account
  banking for clubs and societies, something the commercial banks
  charged for. And they even gave you giant cheque books (for
  multiple signatories).

Cheers,
David.

[toc] | [prev] | [next] | [standalone]


#244191

Frompiorunz <piorunz@gmx.com>
Date2022-01-18 16:00 +0100
Message-ID<DGY7L-8qz-1@gated-at.bofh.it>
In reply to#244182
On 18/01/2022 13:19, Richmond wrote:
> Why do I see this?
>
> host cooperative.co.uk
> cooperative.co.uk has address 127.0.0.1
My local DNS resolver says:
$ dig cooperative.co.uk

; <<>> DiG 9.17.21-1-Debian <<>> cooperative.co.uk
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 26460
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
;; QUESTION SECTION:
;cooperative.co.uk.             IN      A

;; ANSWER SECTION:
cooperative.co.uk.      292     IN      A       127.0.0.1

;; Query time: 0 msec
;; SERVER: 192.168.1.10#53(192.168.1.10) (UDP)
;; WHEN: Tue Jan 18 14:56:38 GMT 2022
;; MSG SIZE  rcvd: 62


Haha.

--
With kindest regards, Piotr.

⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org/
⠈⠳⣄⠀⠀⠀⠀

[toc] | [prev] | [next] | [standalone]


#244192

From"Andrew M.A. Cater" <amacater@einval.com>
Date2022-01-18 16:10 +0100
Message-ID<DGYhr-i7-3@gated-at.bofh.it>
In reply to#244191
On Tue, Jan 18, 2022 at 02:58:02PM +0000, piorunz wrote:
> On 18/01/2022 13:19, Richmond wrote:
> > Why do I see this?
> > 
> > host cooperative.co.uk
> > cooperative.co.uk has address 127.0.0.1
> My local DNS resolver says:
> $ dig cooperative.co.uk
> 
> ; <<>> DiG 9.17.21-1-Debian <<>> cooperative.co.uk
> ;; global options: +cmd
> ;; Got answer:
> ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 26460
> ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1
> 
> ;; OPT PSEUDOSECTION:
> ; EDNS: version: 0, flags:; udp: 1232
> ;; QUESTION SECTION:
> ;cooperative.co.uk.             IN      A
> 
> ;; ANSWER SECTION:
> cooperative.co.uk.      292     IN      A       127.0.0.1
> 
> ;; Query time: 0 msec
> ;; SERVER: 192.168.1.10#53(192.168.1.10) (UDP)
> ;; WHEN: Tue Jan 18 14:56:38 GMT 2022
> ;; MSG SIZE  rcvd: 62
> 
> 
> Haha.
> 
> --
> With kindest regards, Piotr.
> 
> ⢀⣴⠾⠻⢶⣦⠀
> ⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
> ⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org/
> ⠈⠳⣄⠀⠀⠀⠀
>

So - the Cooperative Society - is at https://www.coop.co.uk 

It's quite possible that the 127.0.0.1 is genuine to prevent someone else using it and that their webserve rand DNS provision  will redirect cooperative.co.uk
to coop.co.uk in due course.

Hope this helps,

Andy Cater 

[toc] | [prev] | [next] | [standalone]


#244223

FromRichard Hector <richard@walnut.gen.nz>
Date2022-01-19 20:50 +0100
Message-ID<DHp7X-83Y-1@gated-at.bofh.it>
In reply to#244192
On 19/01/22 04:08, Andrew M.A. Cater wrote:

> So - the Cooperative Society - is at https://www.coop.co.uk

Oddly, when I searched for "Co-operative Group Limited" (which I got 
from whois), I found a different site: https://co-operative.coop

It seems to be the same people, but a totally independent site.

> It's quite possible that the 127.0.0.1 is genuine to prevent someone else using it and that their webserve rand DNS provision  will redirect cooperative.co.uk
> to coop.co.uk in due course.

AFAIK a domain doesn't have to have an A record at all. Or any records 
for that matter; having it registered should be enough to save it.

Why not just redirect it now? Maybe they can't decide which of the above 
sites is the right one :-)

Cheers,
Richard

[toc] | [prev] | [next] | [standalone]


#244228

FromJohn Crawley <john@bunsenlabs.org>
Date2022-01-20 02:40 +0100
Message-ID<DHuAG-318-3@gated-at.bofh.it>
In reply to#244223
On 20/01/2022 04:46, Richard Hector wrote:
> On 19/01/22 04:08, Andrew M.A. Cater wrote:
> 
>> So - the Cooperative Society - is at https://www.coop.co.uk
> 
> Oddly, when I searched for "Co-operative Group Limited" (which I got from whois), I found a different site: https://co-operative.coop
> 
> It seems to be the same people, but a totally independent site.
https://co-operative.coop looks like the parent organization while https://www.coop.co.uk is the supermarket. The "Food" link on the former redirects to the latter.

-- 
John

[toc] | [prev] | [next] | [standalone]


#244205

FromThomas Hochstein <thh@thh.name>
Date2022-01-18 21:30 +0100
Message-ID<DH3h7-3eo-1@gated-at.bofh.it>
In reply to#244182
Richmond schrieb:

> Why do I see this?
> 
> host cooperative.co.uk
> cooperative.co.uk has address 127.0.0.1

Because that's the IP that is associated with that name in the DNS.

There may be multiple reasons for that; one is to effectively block all requests
without straining the host that name had been associated with before.

[toc] | [prev] | [standalone]


Back to top | Article view | linux.debian.user


csiph-web