-
Notifications
You must be signed in to change notification settings - Fork 56
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Starting the beta and specifying a .io domain breaks resolution of any .io domains at all #219
Comments
Had to read dlite's source to fix it. In In that directory, there were three files, all with the same contents.
Removing all the files, I am able to resolve domains again. |
Moving the resolve files to a more specific domain also fixes it
|
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.. |
whois
From: Kubernetes Submit Queue <notifications@github.com<mailto:notifications@github.com>>
Reply-To: nlf/dlite <reply@reply.github.com<mailto:reply@reply.github.com>>
Date: Monday, January 23, 2017 at 1:23 PM
To: nlf/dlite <dlite@noreply.github.com<mailto:dlite@noreply.github.com>>
Cc: Subscribed <subscribed@noreply.github.com<mailto:subscribed@noreply.github.com>>
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 GitHub<#219 (comment)>, or mute the thread<https://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.
|
@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 |
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 |
Bug Reports
dlite --version
):dlite version 2.0.0-beta9
dlite is accessible on a .io domain
dlite is not accessible on a .io domain, and no .io domains can be resolved whatsoever
Specify a .io domain for the hostname, here is my config:
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).EDIT: It happens with
.com
domains too. Had to put github's IP in my/etc/hosts
to make this post.The text was updated successfully, but these errors were encountered: