DNS Question

[Bill McGonigle]

On Aug 17, 2005, at 12:38, Cole Tuininga wrote:

> Secondly, (in retrospect) it doesn't really make sense that a
> ns1.code-energy.com could be the primary nameserver for code-energy.com
> since it's required in order to resolve itself!
>
> What am I misunderstanding here?  Is there somewhere else that's doing 
> a
> mapping for ns[12].code-energy.com to IPs?

There should be host records with your registrar for your name servers.

e.g.:

     >whois ns1.bfccomputing.com -h whois.internic.net
     [Querying whois.internic.net]
     [Redirected to whois.easydns.com]
     [Querying whois.easydns.com]
     [whois.easydns.com]

        Server Name: NS1.BFCCOMPUTING.COM
        IP Address: 217.160.248.65
        Registrar: EASYDNS TECHNOLOGIES, INC.
        Whois Server: whois.easydns.com
        Referral URL: http://www.easydns.com

But I don't see any for your host:

     >whois ns1.code-energy.com -h whois.internic.net
     [Querying whois.internic.net]
     [Redirected to whois.godaddy.com]
     [Querying whois.godaddy.com]
     [whois.godaddy.com]
     No match for "ns1.code-energy.com" in the registrar database.

an aside: OMFG, you're not using GoDaddy for your business account, are 
you?  There are plenty of competent Registrars.  Someone here works for 
DynDNS which I've been using for my recent registrations.  If you can 
get someone at GoDaddy on the phone who knows how to deal with host 
records in a reasonable amount of time without battling four levels of 
script-kiddies I'll retract this comment.

Also, you can't lie about anything and expect DNS to work right.  No 
CNAMES, forward and reverse DNS must match.  If the reverse has an 
inconvenient name and you can't get that changed, suck it up and have 
your nameservers listed as whatever they happen to be.

In addition, there are lots of broken DNS servers and caches out there 
(some buggy, some intentional) that don't give a whit about your TTL, 
they've got it set for 2 weeks, and that's that.

The best way to do this, typically, is to add the new servers as NS3 
and NS4, wait a couple weeks, remove NS1 and NS2 (remember, both in 
your whois records and in your zone file), wait a couple weeks, add new 
entries for NS1 and NS2 with the IP's of NS3 and NS4, wait a couple 
weeks, then remove NS3 and NS4 for good.   It sucks, but it works.

-Bill

-----
Bill McGonigle, Owner           Work: 603.448.4440
BFC Computing, LLC              Home: 603.448.1668
bill at bfccomputing.com           Mobile: 603.252.2606
http://www.bfccomputing.com/    Pager: 603.442.1833
AIM: wpmcgonigle                Text: bill+text at bfccomputing.com
RSS: http://blog.bfccomputing.com/rss

For fastest support contact, please follow:
http://bfccomputing.com/support_contact.html