From owner-freebsd-hackers@FreeBSD.ORG Sun Apr 12 09:45:28 2009 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id CCA68106564A for ; Sun, 12 Apr 2009 09:45:28 +0000 (UTC) (envelope-from aryeh.friedman@gmail.com) Received: from mta4.srv.hcvlny.cv.net (mta4.srv.hcvlny.cv.net [167.206.4.199]) by mx1.freebsd.org (Postfix) with ESMTP id A12D98FC12 for ; Sun, 12 Apr 2009 09:45:28 +0000 (UTC) (envelope-from aryeh.friedman@gmail.com) Received: from flosoft.no-ip.biz (ool-435559b8.dyn.optonline.net [67.85.89.184]) by mta4.srv.hcvlny.cv.net (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) with ESMTP id <0KHZ00CXUF3POEP0@mta4.srv.hcvlny.cv.net> for freebsd-hackers@freebsd.org; Sun, 12 Apr 2009 05:45:28 -0400 (EDT) Received: from flosoft.no-ip.biz (localhost [127.0.0.1]) by flosoft.no-ip.biz (8.14.3/8.14.3) with ESMTP id n3C9jO3e000438; Sun, 12 Apr 2009 05:45:24 -0400 Date: Sun, 12 Apr 2009 05:45:24 -0400 From: "Aryeh M. Friedman" In-reply-to: <49E1B35C.9040106@unsane.co.uk> To: Vincent Hoffman Message-id: <49E1B834.2080604@gmail.com> MIME-version: 1.0 Content-type: text/plain; charset=ISO-8859-1; format=flowed Content-transfer-encoding: 7BIT References: <49E10406.7060006@gmail.com> <49E1B35C.9040106@unsane.co.uk> User-Agent: Thunderbird 2.0.0.21 (X11/20090331) Cc: freebsd-hackers@freebsd.org Subject: Re: setting up local authorative name server with a no-ip.com registered domain X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 12 Apr 2009 09:45:29 -0000 Vincent Hoffman wrote: > On 11/4/09 21:56, Aryeh M. Friedman wrote: > >> I have 3 domains that are registered with no-ip.com >> (istudentunion.com, org and net). All three are also using their >> "no-ip plus" service which provides both static and dynamic resolution >> via their nameservers. When I configure the domains nameservers to >> be theirs everything works great (for the most part), but when I >> change the nameservers to my own sites BIND (base 7.3-RELEASE) I can >> get everything to resolve locally and via dig/host/nslookup remotely >> (if and only if I specify the nameserver by IP). What appears to be >> happing is this: >> >> ~/Desktop:aryeh@flosoft% !d >> dig ns istudentunion.org +trace >> >> ; <<>> DiG 9.4.3-P2 <<>> ns istudentunion.org +trace >> ;; global options: printcmd >> . 463753 IN NS I.ROOT-SERVERS.NET. >> . 463753 IN NS C.ROOT-SERVERS.NET. >> . 463753 IN NS L.ROOT-SERVERS.NET. >> . 463753 IN NS K.ROOT-SERVERS.NET. >> . 463753 IN NS M.ROOT-SERVERS.NET. >> . 463753 IN NS A.ROOT-SERVERS.NET. >> . 463753 IN NS E.ROOT-SERVERS.NET. >> . 463753 IN NS B.ROOT-SERVERS.NET. >> . 463753 IN NS H.ROOT-SERVERS.NET. >> . 463753 IN NS D.ROOT-SERVERS.NET. >> . 463753 IN NS G.ROOT-SERVERS.NET. >> . 463753 IN NS F.ROOT-SERVERS.NET. >> . 463753 IN NS J.ROOT-SERVERS.NET. >> ;; Received 500 bytes from 127.0.0.1#53(127.0.0.1) in 0 ms >> >> org. 172800 IN NS B2.ORG.AFILIAS-NST.org. >> org. 172800 IN NS A2.ORG.AFILIAS-NST.INFO. >> org. 172800 IN NS C0.ORG.AFILIAS-NST.INFO. >> org. 172800 IN NS B0.ORG.AFILIAS-NST.org. >> org. 172800 IN NS A0.ORG.AFILIAS-NST.INFO. >> org. 172800 IN NS D0.ORG.AFILIAS-NST.org. >> ;; Received 437 bytes from 192.203.230.10#53(E.ROOT-SERVERS.NET) in 86 ms >> >> istudentunion.org. 86400 IN NS ns2.istudentunion.org. >> istudentunion.org. 86400 IN NS ns1.istudentunion.org. >> ;; Received 103 bytes from 199.19.54.1#53(B0.ORG.AFILIAS-NST.org) in >> 88 ms >> >> ;; connection timed out; no servers could be reached >> >> > Since your nameservers for istudentunion.org are in the > istudentunion.org domain, you will need glue at the parent nameservers > to prevent a chicken and egg problem. > Exactly how you tell no-ip this i'm not sure but its not a terribly > unusual request. Once the have added it you will need to wait for the > .org tld zone to update (not sure of their schedule but better than the > once or twice a day of 10 years ago :) > The other way around this is to have the nameservers for the domain > to be in an already resolving domain, that way you dont need to worry > about glue. This is very common. > > I had already used the second trick earlier today (after posting the message) and what I did is pointed a "dead" domain I personally had at the right IP (the other register correctly lets you register/change nameservers [which no-ip has a form for but it seems to do absulutly nothing])... now I am stuck with a corporate domain depending on a domain owned by a single employee (me [even though I am the CTO/COO I personally think it is inapporiate to do it this way]).... the other crazy thing is no-ip puts a 30 day lock on transfers from them when you transfer a domain to them [we transfered from dreamhost]). > > Vince > > > >> _______________________________________________ >> freebsd-hackers@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-hackers >> To unsubscribe, send any mail to >> "freebsd-hackers-unsubscribe@freebsd.org" >> > > >