Support the ongoing development of Laravel.io →
Installation
Last updated 2 years ago.
0

Then I get this result:

PING google.com (216.58.212.238): 56 data bytes
64 bytes from 216.58.212.238: icmp_seq=0 ttl=53 time=22.586 ms
64 bytes from 216.58.212.238: icmp_seq=1 ttl=53 time=9.226 ms
64 bytes from 216.58.212.238: icmp_seq=2 ttl=53 time=24.096 ms
64 bytes from 216.58.212.238: icmp_seq=3 ttl=53 time=42.983 ms
64 bytes from 216.58.212.238: icmp_seq=4 ttl=53 time=135.692 ms

When I do a DNS query with the dig command:

Lees-MacBook-Air:Code Lee$ dig +short google.com
216.58.212.238

When I make a request using cURL:

Lees-MacBook-Air:Code Lee$ curl google.com
<HTML><HEAD><meta http-equiv="content-type" content="text/html;charset=utf-8">
<TITLE>302 Moved</TITLE></HEAD><BODY>
<H1>302 Moved</H1>
The document has moved
<A HREF="http://www.google.nl/?gfe_rd=cr&ei=WBl-V_3xLKPH8AfzzJOYDQ">here</A>.
</BODY></HTML>

...and another one to google.nl;

Lees-MacBook-Air:Code Lee$ curl google.nl
curl: (6) Could not resolve host: google.nl

Edit: A dig result for google.nl:

Lees-MacBook-Air:Code Lee$ dig +short google.nl
216.58.212.227

I really think that this has something to do with DNS issues after installing dnsmasq for valet. Because when I use another network (my LTE network for example) I reproduce the same issue. I can't however trace what exactly is causing this behaviour.

0

So it turned out that when setting the gTLD to .nl in Valet, somehow a conflict can occur when visiting several sites that use .nl as a gTLD. Such as Google.nl. My work-around is using a non-existant gTLD in the future. Fixed.

0

Sign in to participate in this thread!

Eventy

Your banner here too?

ravenberg ravenberg Joined 25 Mar 2016

Moderators

We'd like to thank these amazing companies for supporting us

Your logo here?

Laravel.io

The Laravel portal for problem solving, knowledge sharing and community building.

© 2024 Laravel.io - All rights reserved.