Resolve

From 42Experiment

Jump to: navigation, search
Language: English  • Español • Français

Contents

[edit] Using Openresolvers

If either you're not able or you don't want to configure your own resolvers, you can use the resolvers listed here.

Here will be set a full list of DNS servers open to recursion you will be able to use and that resolve zone 42. You will just have to choose the one(s) you want and configure it (them) as a DNS resolver on your computer. While using those DNS, you'll continue to resolve the usual domains correctly plus the ".42" domains without a supplementary configuration.

[edit] The list

[edit] GeekNode OpenResolvers

  1. 81.93.248.69
  2. 81.93.248.68
  3. 91.194.60.196
  4. 193.17.192.53

[edit] Other OpenResolvers

[edit] .42 + OpenNIC + ICANN

  1. 95.142.171.235
  2. 85.17.236.67

[edit] Privately operated resolvers

[edit] Configuration

[edit] Linux

The modification depends on your distribution. Here are some examples. If you don't find instructions according to your distribution here, try to look at the distribution documentation. Then, feel free to append the method in this section !

[edit] Archlinux

Create a file named /etc/resolv.conf.head containing the lines: 

nameserver 81.93.248.69
nameserver 81.93.148.68
nameserver 91.194.60.196
nameserver 193.17.192.53

Then restart your Internet connection and the zone .42 should be resolved.

[edit] Mandriva

As stated in the /etc/resolv.conf file, you should not edit it directly. I added the 42 DNS this way as root : 

echo nameserver 81.93.248.69 >> /etc/resolvconf/resolv.conf.d/head
service network restart

I did not add more than one server as GNU tools only use the three first servers and I wanted to keep the 2 servers given by the DHCP as backup.

[edit] Ubuntu

Edit /etc/dhcp3/dhclient.conf and add this at the end of the file : 

prepend domain-name-servers 81.93.248.69, 81.93.248.68, 91.194.60.196, 193.17.192.53;

Note: You may have to disconnect-reconnect the computer to the network. Note: It seems that it doesn't work for every web-sites.

[edit] Ubuntu and Dnsmasq

The following allows you to use Geeknode DNS only for .42 domains while keeping your regular DNS provider for other domains.

Install dnsmasq : 

aptitude install dnsmasq

Edit /etc/dnsmasq.conf and add the line : 

server=/42/81.93.248.69

Restart dnsmasq : 

sudo /etc/init.d/dnsmasq restart

Edit /etc/dhcp3/dhclient.conf, then uncomment or add the line : 

prepend domain-name-servers 127.0.0.1;

Now disconnect and reconnect to you local network, to refresh the /etc/resolv.conf file, then test it !

[edit] OpenWRT (and Dnsmaq generic)

OpenWrt uses Dnsmasq. The following details generic configuration for the latter, then specific configuration of the former.

Dnsmasq can delegate domain resolutions to specific servers. This is done with the -S option. The syntax of its argument is (for our purpose) /DOMAIN/SERVER. We thus use one of the OpenResolvers by adding the following to the invocation of Dnsmasq. 

dnsmasq [OTHER OPTIONS] -S /42/91.194.60.196


For OpenWrt, the command line of Dnsmasq is based on the contents of /etc/config/dhcp, and more specifically the server list: 

config dnsmasq
 [...]
 list server             '/42/91.194.60.196'

[edit] Windows

It is a known problem: Windows, whatever the version is, defaults to refuse a numeric TLD. Because some companies, that uses internally numeric TLDs, Microsoft itself published a patch that solves this problem: http://support.microsoft.com/kb/947228 If you are an idler, you just have to download it, double-click, and problem is solved. What the patch does is really basic, you can do it yourself: 

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Dnscache\Parameters

[edit] Mac OS

2604:8800:100:1E:0:0:0:2 05:08, 3 March 2011 (CET) not working, see discussion

On Mac OS X (Snow Leopard 10.6.* and Leopard 10.5.*):

[edit] Verification

You can test on a domain. For instance, try to visit http://nic.42. You also try a simple "ping". On Windows and Unix : 

ping nic.42

If there is an answer, it works.

[edit] Using your own resolvers

It's pretty easy. On each resolver you are using and where you want to be able to resolve 42, you have to add IPs of [A/B/C/D].42TLD-SERVERS.NET as "Forwarders" for the "42" DNS zone. You may also want to use IPv6 of C.42TLD-SERVERS.NET as a forwarder (2a01:678:fff:42:42::). Please have a look a the followings sections for further explanations.

IMPORTANT: as far as forwarding servers are concerned, we only maintain the [Resolve] page. In order to avoid misleading people using literal adresses in the HOWTOs below, we have used <resolvern> placeholders instead. Please use resolvers from the list accordingly.

[edit] Bind

Add the following lines to your bind config file (/etc/bind/named.conf): 

zone "42" IN { 
    type forward;
    forwarders { <resolver1>; <resolver2>; [...] };
};

[edit] Unbound 

server:
    domain-insecure: "42"
stub-zone:
    name: "42"
    stub-addr: <resolver1>
    stub-addr: <resolver2>
    [...]

[edit] Djbdns

Type the following lines into a prompt : 

cd /services/dnscache
echo <resolver1> > root/servers/42
echo <resolver2> >> root/servers/42
[...]
svc -t /services/dnscache

[edit] MaraDNS

Add this line to your /etc/mararc: 

upstream_servers["42."] = "<resolver1>, <resolver2> [...]"

[edit] PowerDNS

[edit] Case 1 : you use PowerDNS recursor and it's working

You need to edit recursor.conf which should be in /etc/powerdns. You'll need to add the servers given at the top in the line :

forward-zones= 42=<resolver1>;<resolver2>[;...]

If you already have a forward-zones, proceed by adding the servers from the top at the end after a coma like this :

forward-zones= ...already_existing_zones..., 42=<resolver1>;<resolver2>[;...]

[edit] Case 2 : you use PowerDNS server and a third party recursor

In this case, you should see in /etc/powerdns/pdns.conf or maybe in a file of /etc/powerdns/pdns.d/* something like :

recursor=xxx.xxx.xxx.xxx or recursor=xxx.xxx.xxx.xxx:yyy

If this IP is yours, you need to edit the config files of the server at this address.

If not, you need to install PowerDNS recursor. In recursor.conf, proceed like in case 1 and also add :

allow-from=127.0.0.0/8, ::1/128 local-address=127.0.0.1 local-port=1153 (or any free port. If you're unsure, try "netstat -an" and verify that nothing is listening on 1153)

Start PowerDNS recursor and modify PowerDNS server with :

recursor=127.0.0.1:1153 (or the port you choose)

Restart PowerDNS server, it's done. If not, look at /var/log/syslog to see if errors exist.


[edit] And then ?

If not already : 

 echo "nameserver 127.0.0.1" > /etc/resolv.conf

[edit] Chromium/Chrome Bug

We are aware of this issue, and we have reported it to the project Chromium's developers. We are still waiting a correction and/or answer. However, there is a way to bypass the issue : type the wanted adress starting by http:// (or any other protocol you want to use), then, in the context menu choose the second option (usually the one which is green). Once you have made this choice, it will be set by default next times you will type this address.

Related: http://news.ycombinator.com/item?id=2144225

Retrieved from "http://wiki.42registry.org/page/Resolve"
Personal tools
Namespaces
Variants
Actions
Navigation
Toolbox