I have set up a webserver and connected a dns with the domain shown bellow to it. The Problem is that when I copy and paste the domain it changes to a weird string, as shown bellow.
The original domain i used is "https://negertöter.de" and it changes to "https://xn--negertter-57a.de/".
Is this because of the "ö" or what's the problem, can i fix this or do i have to register a new domain without the "ö" to get rid of the problem?
Thank you!
What you see is ok and works as designed. What you see is not a "weird" string, it is the ASCII representation of Internationalized Domain Names aka IDNs which are domain names using characters outside of the ASCII range.
You can search for IDNA specification to understand more about that.
Browsers support it differently depending on the TLD and the characters in the domain name. For security reasons, they may not display the IDN in "Unicode" form and fall back to ACE (ASCII Compatible Encoding) form as you witnessed.
You don't have to register anything else, xn--negertter-57a.de is the correct ASCII representation per IDNA specification of IDN negertöter.de.
Your registrar, DNS provider, and/or website provider should be able to explain things further and guide you as needed.
I type route, the result is strange, as shown in the pic, why?
enter image description here
From the man you can read:
-n
show numerical addresses instead of trying to determine symbolic host names. This is useful if you are trying to determine why the route to your nameserver has vanished.
If you omit the -n option you will see a hostname instead of the numerical IP address.
I'm working on ways to automate the updating of .htaccess to block IP ranges that have come in and tried to hack the site.
I've been doing it manually for a while, pulling an IP address, then using a web based whois utility to find the range it's in, then manually adding the range to the blocked IP list for the site. It's a pain.
Now I'm parsing the logfile to find the IP address of suspicious entry attempts with a Perl script, and I want to find the IP address range to which that IP address belongs, and maybe pull some other descriptive information that will quickly tell me if this is a range I want to block.
I know it can be done because the web utilities provide the information. Here's an example
.
I can run gethostbyaddr on them, but that's not what I need.
I've seen some whois modules that had some information, but could not find access to the range to which the IP address belongs. I'm hoping there is a module I can use to pull the address range from to help me speed up the security process.
I suggest that you make use of the Net::Whois::Raw module. It returns just a block of text, and you will have to use regex patterns to extract the information that you need
Here's an example that displays the IP range for the same address as you use in your example. Just print $info to see the whole thing
use strict;
use warnings 'all';
use feature 'say';
use Net::Whois::Raw;
my $info = whois('95.137.240.189');
say $info =~ /NetRange:\s*(.+)/;
output
95.0.0.0 - 95.255.255.255
Is there a way that I for example use my website called www.mywebsite.com and in address bar to show www.wikipedia.com?
And of course to load my contents from mywebsite.com?
That's exactly the kind of thing that you don't want to happen, because then, many people would fish visitors going to facebook.com into their ads or clickbait websites instead. You couldn't do it even if you wanted to, it would be like saying, if you call at Person A's number, it would directly refer to Person B instead.
Hope that gives you an explaination!
You can use iframe to display the contents from Wikipedia or any other URL on your webpage.
As an overall solution i'd like to split dns resolving between different servers, using dnsmasq.
i.e. Default to dns server A, unless explicitly set to dns server B per host (mac).
I'd like to split my network into dnsmasq tagged subnets, for this example say:
192.168.1.80-150 = green
192.168.1.40-50 = red
I would like dhcp leases to be handed by, by -default- tagged green, except for a few specific MACs where I would like to hand out the red tag.
I have this part working successfully (I believe), where i explicitly set it by MAC - but what i would like is for everything -unless specified otherwise- to default to green.
I would then like to say "for all green tags, give them dns server A as their resolver", "for all red tags, give them dns server B as their resolver".
is this possible?
I have the following config that does not seem to work:
--8<--
dhcp-range=set:green,192.168.1.80,192.168.1.150,infinite
dhcp-range=tag:red,192.168.1.40,192.168.1.50,infinite
dhcp-option=net:green,option:dns-server,8.8.8.8,8.8.4.4
dhcp-option=net:red,option:dns-server,192.168.1.11
dhcp-host=AA:BB:CC:DD:CC:BB,redhost1,192.168.1.41,infinite,net:red
dhcp-host=BB:CC:DD:AA:BB:00,greenhost1,192.168.1.81,infinite,net:green
dhcp-option=option:router,192.168.1.1
--8<--
This does not seem to work however, I have different hosts being assigned different ip addresses based on whether i have matched their MAC, and then it seems as if the dns server is not correctly being handed out.
I believe the dns server is not being handed out because a "cat /etc/resolv.conf" on one of the hosts shows 127.0.0.1.
To summarise my queries:
Can i make everything default to 'green', unless explicitly set to 'red' by MAC (at the moment I am having to explicitly put the mac of everything into the conf file)?
Can i specify different DNS servers, for different tagged networks?
For extra clarity I am a bit confused about the different between "tag" and "set" and in googling have found references to both, a short and clean definition of these would be great.
thanks very much
ok, i fixed it (wrt my particular request) and i'll post what i've got here in case it helps someone else.
so my requirement was handing out different dns server (and perhaps different gw) to different hosts, and this seems to work:
dhcp-range=set:green,192.168.1.80,192.168.1.150,infinite
# red network
dhcp-host=11:22:33:44:55:66,hosta,192.168.1.11,infinite,set:red
dhcp-host=66:55:44:33:22:11,aa:bb:cc:dd:ee:ff,hostb,192.168.1.12,infinite,set:red
# green network mobile
dhcp-host=dd:dd:dd:dd:dd:dd,android1,192.168.1.21,infinite,set:green
dhcp-host=cc:cc:cc:cc:cc:cc,android2,192.168.1.22,infinite,set:green
unless expicility set otherwise, everything is tagged green. Some certain MACs are tagged red. Then to do the different dns server and different gw you can do:
# options
dhcp-option=tag:green,option:dns-server,192.168.1.1,192.231.a.b # ,8.8.8.8,8.8.4.4
dhcp-option=tag:red,option:dns-server,192.168.1.c
dhcp-option=tag:green,option:router,192.168.1.1
dhcp-option=tag:red,option:router,192.168.1.c
some other notes / context that i found helpful about this, and also about the net / set / tag options:
The optional set: sets an alphanumeric label which marks this network so that dhcp options may be specified on a per-network basis. When it is prefixed with 'tag:' instead, then its meaning changes from setting a tag to matching it. Only one tag may be set, but more than one tag may be matched.
More than one tag can be set in a dhcp-host directive (but not in other places where "set:" is allowed)
This system evolved from an earlier, more limited one and for backward compatibility "net:" may be used instead of "tag:" and "set:" may be omitted. (Except in dhcp-host, where "net:" may be used instead of "set:".) For the same reason, '#' may be used instead of '!' to indicate NOT.
therefore i think it's safe to just:
use set and tag, and avoid using net (since it's the old way)
use set in your dhcp-range and dhcp-host, to assign the tags, and
use tag in your options to match the tags that you've already set.
as an aside on of those dhcp-hosts you can see with multiple mac addresses, because it's the eth0 and wlan mac's for the same box.
seems to work for me anyway, perhaps this will help someone.
why not change the mind to setup 2 dhcp sections over 2 vlans with just 1 dnsmasq service, and make the 2 vlans communicate with each other through their gateways (or not).