Okay, a couple hours banging away trying to get zoneedit working properly has not worked on my Linode properly. Im running Debian Linux. When I use dig on my local machine I get a correct zoneedit nameserver response but I'm at a loss at how to set up zoneedit on my server correctly. Any help _greatly_ appreciated!

This may not seem like the most helpful thing in the world to say,
but read the book.

Having some understanding of DNS will save you time in the long run.

There are lots of cheaper, or free web based DNS services, http://www.everydns.net/
is but one.

I have that book and your post is not helpful (sorry!).[/i]

Are your zones on zoneedit setup correctly?
If so do your names resolve on a different machine?
Do they resolve on your linode?
Is your linode setup to use a recursive nameserver ( either linodes or your own )?

Need more information!

This a dig response from my home computer:

;; AUTHORITY SECTION:
edit.net. 7200 IN NS ns13.zoneedit.com.
edit.net. 7200 IN NS ns17.zoneedit.com.

But when I ping I get:

PING edit.net (0.0.0.0): 56 data bytes
64 bytes from edit.edit.128.1: icmp_seq=0 ttl=64 time=11.678 ms
from my previous ISP's gateway. I erased the old ISP's dns records and set up the zoneedit yesterday so it should have propagated by now.

I was going to install bind to take care of everything from my Linode, but thought zoneedit would be easier for now.

My registar wants to charge for including IP-based nameservers and that does not fly with me.

My linode resolves through IP all well, but not through DNS, as far as I can tell, i'm having an A record issue.

I have not set up a recursive nameserver although that might not be a bad idea... suggestions?

Thanks (again!) in advance!

Assuming those Zoneedit name servers are the correct ones, that definately means theres a problem with your setup in Zoneedit. It is possible changes in Zoneedit haven't been committed (their system is pretty slow since their zone files are *massive*), but I wouldn't count on that... I've had little trouble with Zoneedit in the past (I use BIND on my Linode now instead, managed to rack up more than 5 domains I wanted DNS for, and didn't feel it was worth paying for).

digging the ZoneEdit nameservers you specified produces no result.

digging on my Linode (Fremont) or home machine (Amsterdam) gives the same result:

;; ANSWER SECTION:
edit.net.               38400   IN      A       64.39.31.55
 
;; AUTHORITY SECTION:
edit.net.               38400   IN      NS      ns1.netgears.com.
edit.net.               38400   IN      NS      ns2.netgears.com.

Looks like your ZoneEdit changes have not been committed.

Have you informed your registrar about the new nameservers?

_________________
/ Peter