Home
| Calendar
| Mail Lists
| List Archives
| Desktop SIG
| Hardware Hacking SIG
Wiki | Flickr | PicasaWeb | Video | Maps & Directions | Installfests | Keysignings Linux Cafe | Meeting Notes | Linux Links | Bling | About BLU |
On Tue, 26 Dec 2000, Daniel Hagerty wrote: > Let's say you want to register foobar.com, with a name server of > ns1.foobar.com (which we'll say is IP 10.1.1.1). For this to happen, In my case, it's more like I'm trying to register foo.com, with a nameserver of ns.bar.com, where ns.bar.com already acts as the primary dns for bar.com. I own and manage bar.com, and I added the zone for foo.com. I test this with nslookup: > server ns.bar.com > www.foo.com Name: www.foo.com Address: 10.1.1.1 and it all works fine. Now I register the domain name at domainzoo.com, and their tech support tells me "your dns server does not exist". > .... > Without an A record in the parent zone, there's no way for anybody on > the net to *find* ns1.foobar.com to ask them about foobar.com . It's > a bootstrap problem. > .... ns.bar.com does indeed have a valid A record. I don't understand why domainzoo has a problem with it. -- John Abreau / Executive Director, Boston Linux & Unix ICQ#28611923 / AIM abreauj / Email jabr at blu.org - Subcription/unsubscription/info requests: send e-mail with "subscribe", "unsubscribe", or "info" on the first line of the message body to discuss-request at blu.org (Subject line is ignored).
BLU is a member of BostonUserGroups | |
We also thank MIT for the use of their facilities. |