Robot | Path | Permission |
GoogleBot | / | ✔ |
BingBot | / | ✔ |
BaiduSpider | / | ✔ |
YandexBot | / | ✔ |
Title | Blog - |
Description | Schinckel.net Schinckel.net Projects Archives --> Tags About Contact Feed Wireguard and Dynamic Hostnames Posted: 2021 - 11 - 02 @ 19:52:45 Tags: wireguard dns dynam |
Keywords | N/A |
WebSite | schinckel.net |
Host IP | 208.94.118.238 |
Location | United States |
Site | Rank |
US$1,812,300
Last updated: 2023-04-28 06:21:23
schinckel.net has Semrush global rank of 5,840,262. schinckel.net has an estimated worth of US$ 1,812,300, based on its estimated Ads revenue. schinckel.net receives approximately 209,112 unique visitors each day. Its web server is located in United States, with IP address 208.94.118.238. According to SiteAdvisor, schinckel.net is safe to visit. |
Purchase/Sale Value | US$1,812,300 |
Daily Ads Revenue | US$1,673 |
Monthly Ads Revenue | US$50,187 |
Yearly Ads Revenue | US$602,242 |
Daily Unique Visitors | 13,941 |
Note: All traffic and earnings values are estimates. |
Host | Type | TTL | Data |
schinckel.net. | A | 300 | IP: 208.94.118.238 |
schinckel.net. | AAAA | 776 | IPV6: 2607:ff18:80:4::da6 |
schinckel.net. | NS | 900 | NS Record: ns2.hover.com. |
schinckel.net. | NS | 900 | NS Record: ns1.hover.com. |
schinckel.net. | MX | 900 | MX Record: 5 ALT1.ASPMX.L.GOOGLE.COM. |
schinckel.net. | MX | 900 | MX Record: 1 ASPMX.L.GOOGLE.COM. |
schinckel.net. | MX | 900 | MX Record: 10 ASPMX3.GOOGLEMAIL.COM. |
schinckel.net. | MX | 900 | MX Record: 10 ASPMX5.GOOGLEMAIL.COM. |
schinckel.net. | MX | 900 | MX Record: 5 ALT2.ASPMX.L.GOOGLE.COM. |
schinckel.net. | MX | 900 | MX Record: 10 ASPMX4.GOOGLEMAIL.COM. |
schinckel.net. | MX | 900 | MX Record: 10 ASPMX2.GOOGLEMAIL.COM. |
schinckel.net. | TXT | 900 | TXT Record: v=spf1 include:aspmx.googlemail.com ~all |
Schinckel.net Projects Archives --> Tags About Contact Feed Wireguard and Dynamic Hostnames Posted: 2021 - 11 - 02 @ 19:52:45 Tags: wireguard dns dynamic vpn Comments: here . We use Wireguard at work for our VPN: this allows us to limit who can access our administration interface based on being on our company VPN. I’ve set up Wireguard on my router so that I don’t need to connect to the VPN on each of my devices, but I also use a split tunnel so that only the IP addresses that are required go through there. I discuss in a previous post how I use VPN Policy Based Routing to ensure that the IP addresses are updated there. However, I also run a different Wireguard interface allowing me to connect back to my LAN. This sits behind a dynamic IP address (even though it doesn’t change much). In most cases that’s okay - if my IP address happens to have changed, I can just reconnect my VPN, and in reality it’s very unlikely that I’d be actually using the VPN when the IP address changed. |
HTTP/1.1 301 Moved Permanently Date: Thu, 21 Oct 2021 08:08:43 GMT Server: Apache Location: https://schinckel.net/ Content-Type: text/html; charset=iso-8859-1 HTTP/2 200 date: Thu, 21 Oct 2021 08:08:43 GMT server: Apache last-modified: Fri, 10 Sep 2021 00:50:24 GMT etag: "21ebc-5cb998034ceed" accept-ranges: bytes content-length: 138940 content-type: text/html; charset=UTF-8 via: e2s |
Domain Name: SCHINCKEL.NET Registry Domain ID: 132488595_DOMAIN_NET-VRSN Registrar WHOIS Server: whois.tucows.com Registrar URL: http://www.tucows.com Updated Date: 2020-10-10T08:52:06Z Creation Date: 2004-10-11T15:27:26Z Registry Expiry Date: 2021-10-11T15:27:26Z Registrar: Tucows Domains Inc. Registrar IANA ID: 69 Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited Domain Status: clientUpdateProhibited https://icann.org/epp#clientUpdateProhibited Name Server: NS1.HOVER.COM Name Server: NS2.HOVER.COM DNSSEC: unsigned >>> Last update of whois database: 2021-09-10T01:03:32Z <<< |