Starting the beta and specifying a .io domain breaks resolution of any .io domains at all

[synic]

Bug Reports

• dlite version in use (run dlite --version):

dlite version 2.0.0-beta9

• expected behavior:

dlite is accessible on a .io domain

• actual behavior:

dlite is not accessible on a .io domain, and no .io domains can be resolved whatsoever

• steps to reproduce

Specify a .io domain for the hostname, here is my config:

cpu: 2
disk: 20
dns: 192.168.64.1
docker: latest
extra: ""
hostname: ebdev.io
id: d3a0649d-e181-11e6-9f68-a0999b1068eb
memory: 3
route: true

This has happened before, I thought it was unrelated to dlite, however, I'm fairly sure it's dlite now. It has also happened to a coworker. Once you try to specify a .io domain, no .io domains will be resolvable (including the one you specified).

~]$ ping sentry.io
ping: cannot resolve sentry.io: Unknown host
[~]$ ping slither.io
ping: cannot resolve slither.io: Unknown host
[~]$

EDIT: It happens with .com domains too. Had to put github's IP in my /etc/hosts to make this post.

[synic]

Had to read dlite's source to fix it. In cmd_setup.go, it mentions /etc/resolver

In that directory, there were three files, all with the same contents. com, io and docker:

[resolver]$ cat com
nameserver 127.0.0.1
port 1053

Removing all the files, I am able to resolve domains again.

[synic]

Moving the resolve files to a more specific domain also fixes it

$ cd /etc/resolver
$ sudo mv io ebdev.io

[nlf]

ahhh yes, this is a good point. i should probably make it clear when choosing a hostname that the tld portion should be invalid since its dns lookups will be hijacked

i wonder if there's an api somewhere that will let me determine if a tld is valid or not..

[ultiweb-zz]

whois

From: Kubernetes Submit Queue <[email protected]mailto:[email protected]> Reply-To: nlf/dlite <[email protected]mailto:[email protected]> Date: Monday, January 23, 2017 at 1:23 PM To: nlf/dlite <[email protected]mailto:[email protected]> Cc: Subscribed <[email protected]mailto:[email protected]> Subject: Re: [nlf/dlite] Starting the beta and specifying a .io domain breaks resolution of any .io domains at all (#219)

ahhh yes, this is a good point. i should probably make it clear when choosing a hostname that the tld portion should be invalid since its dns lookups will be hijacked

i wonder if there's an api somewhere that will let me determine if a tld is valid or not..

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHubhttps://github.com/nlf/dlite/issues/219#issuecomment-274572813, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AAqpbXF-LfslFVj-3uRSK8FDDfgSypWFks5rVPANgaJpZM4LrNHo.

This e-mail, including attachments, may include confidential and/or proprietary information, and may be used only by the person or entity to which it is addressed. If the reader of this e-mail is not the intended recipient or his or her authorized agent, the reader is hereby notified that any dissemination, distribution or copying of this e-mail is prohibited. If you have received this e-mail in error, please notify the sender by replying to this message and delete this e-mail immediately.

[synic]

@nlf: perhaps if it IS valid, the entire domain should be used when creating the file.

This is something that the old dlite did not have a problem with

[nlf]

the old dlite also wasn't able to resolve containers :) the reason i setup the resolver for the whole tld is because when container routing is enabled you can do lookups for <containername>.<tld>