Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

foo@bar.com

bar.com

Post reply on HN
Print view View original

91–100 of 301 posts

Re: foo@bar.com

#91

Post by CydeWeys »

yesbabyyes wrote: post #67
Hamuko wrote: post #61

Earlier quoted context omitted.

Didn't Microsoft for the longest time use a domain in their documentation that they didn't own and were basically forced to buy it now?

Yes, you're probably thinking of corp.com, which MS used as the default for AD setups. It went up for auction this spring and MS bought it: https://krebsonsecurity.com/2020/04/microsoft-buys-corp-com-...

I used to work for a company named Foo Bar Solutions with the public website foobarsol.com, but that used foobar.com for the internal AD name for some reason (which they didn't actually own). That was ... interesting. Microsoft clearly did not do their due diligence in explaining that the domain configured in AD must absolutely, positively, 100% no bullshit, be a real domain name that you actually own and will never relinquish. I'd argue they should have gone so far as WHOISing the domain name in question and failing outright if it didn't exist, and displaying the Registrant/Organization information if it did and prompting "Is this you?" before continuing. Would have saved so many sysadmins so much grief over the years.

And to be clear, Foo Bar is a placeholder here, not the actual name.

Re: foo@bar.com

#92

Post by Wistar »

davemtl wrote: post #54
chrismeller wrote: post #4

Something that I’m surprised a lot of devs don’t know; there are official domains you’re supposed to use for documentation, testing, etc. They are specifically reserved by IANA for these purposes. Originally I think it was just example.com, but they now have a list of all them: https://www.iana.org/domains/reserved

Indeed. I've owned `invaliddomain.com` for almost 20 years. You'll be surprised how many use it for testing. One morning I woke up to 30,000 e-mails from Sony Japan with PDFs attached of scanned hand-written part orders. Something similar with Boeing sending me backup notifications. I notified each of these companies about their configuration through their official channels, only to be told "no, it's your server doin…

I owned forexample.com for 15 years or so and saw all kinds of mail but the most persistent was a record company owner who, from time-to-time, wrote semi-deranged angry emails demanding that I turn the domain over to him. I always had grand plans for the domain but never acted and, a couple years ago, I forgot to renew and the domain is now in someone else's hands. I don't miss it, especially the record company guy.

Re: foo@bar.com

#93

Post by throw0101a »

nebulous1 wrote: post #20
chrismeller wrote: post #4

Something that I’m surprised a lot of devs don’t know; there are official domains you’re supposed to use for documentation, testing, etc. They are specifically reserved by IANA for these purposes. Originally I think it was just example.com, but they now have a list of all them: https://www.iana.org/domains/reserved

A lot of people learned this the hard way when Google bought and later enabled permanent HSTS for the .dev domain (prior to actually publicly releasing it) in Chrome, breaking everybody's non https local .dev environments. As mentioned above, it should have been .test

> .dev domain (prior to actually publicly releasing it) in Chrome, breaking everybody's non https local .dev environments.

Yeah, except it broke more than that.

A lot of folks use/d ".dev" and and ".prod" as internal sub-domains in their actually-owned domain (dev.example.com, prod.example.net).

For convenience you could however use the resolve.conf's "search" option to simply things, so at the CLI one could type "ssh webserv01.dev" and the resolver would would then append the company's domain to get the FQDN for the query.

Except once Google made their changes "webserv01.dev" now could go out to the Internet—especially if you had it in a browser and it tried to be "clever".

Re: foo@bar.com

#94

Post by darkerside »

kubanczyk wrote: post #36
ryanbrunner wrote: post #13

Earlier quoted context omitted.

In practice, is there any difference? As long as example.com is guaranteed to be reserved, I don't see any downside in using it. Not using .test was a big problem for tools like Pow a while ago, but that's because they were using .dev, which had no official recognition as being reserved or special-purposed. For e-mail addresses in particular, I could easily see a situation where your domain logic prevents you from us…

> In practice, is there any difference? RFC 6761 says that there is a difference when I actually resolve these names. The example.com, example.net, etc. will resolve normally to an existent IP. Moreover they resolve the same way on every DNS cache. The xxx.test will resolve as non-existent by default, unless you configure your own DNS specifically for them.

I stand corrected

Re: foo@bar.com

#95

Post by JdeBP »

djsumdog wrote: post #62

I always used bob@bob.bob. It's not a real TLD (although at the rate of new TLDs, it might be soon) but it still validated on most websites.

Someone whimsical will grab it, and not be happy with the ground that you've laid. Consider that dot@dotat.at exists.

* https://news.ycombinator.com/item?id=21369013

Re: foo@bar.com

#96

Post by e12e »

cedilla wrote: post #84
AdamGibbins wrote: post #50

Earlier quoted context omitted.

https://tools.ietf.org/html/rfc5321#section-2.3.5

Do MTAs actually do it though?

Yes? http://postfix.1071664.n5.nabble.com/MX-lookup-fallback-to-A...

Note that odds are probably low today of anything listening on port 25 if no mx record is set up, I'm guessing (I'm guessing most people that setup an smtp server also sets up mx and a handful of records in dns).

Re: foo@bar.com

#97

Post by akritrime »

CydeWeys wrote: post #87
akritrime wrote: post #81

Earlier quoted context omitted.

I actually confirmed your GitHub before I made the previous comment. It was just a frivolous reply that I found funny but HN didn't. Tough crowd. But I really, really appreciate your reply, thanks for taking your time to prove your identity. Hopefully I didn't waste too much of your Sunday morning.

My experience here is that humor (especially deadpan) tends to land very poorly on HN, both because people are never contextually expecting it and because they tend to downvote it when they do recognize it, as they dislike perceived low effort comments that they don't feel are meaningfully contributing to the discussion (i.e. adding noise, not signal). HN may as well put "Don't try to be funny" in the FAQ, because it…

Mistake made and lesson learnt. After being introduced to the larger internet community via reddit, sometimes you slip up in more serious places like HN.

Re: foo@bar.com

#98

Post by hmcamp »

CydeWeys wrote: post #39
owl57 wrote: post #32

Earlier quoted context omitted.

Sounds like it could be intentional. — We bought .dev, now what we do with all those people in the wild misusing it? — Well, most of them misuse it with our browser, let's break at least their hacks early and loudly.

It was unintentional. Source: The horse's mouth. I'm the guy who came up with the idea of launching .dev and .app as HTTPS-only TLDs, and I'm the one who had them added to the HSTS preload list.

@Cydeweys, I respect this level of candidness

Re: foo@bar.com

#99

Post by comfyinnernet »

CydeWeys wrote: post #77
Sharlin wrote: post #29

Earlier quoted context omitted.

But people who know and use the words foo and bar are almost exclusively developers, so they should know better eveb when typing a fake address to a random form. But it’s easy to type reflexively, without thinking, so I’m not surprised people do it.

I'll be honest, even I do this when it's a form that has an email requirement but that I don't otherwise care about at all. I'm not gonna sign myself up for spam. Sometimes example.com and whatever other testing TLD that comes to mind is blocked because they want something that could plausibly be a real email address, so I give them something that could plausibly be a real email address, like asfgjklahsfgjklh@asdfogh…

Have you tried theunabomberwasright@fbi.gov?
Post reply on HN