I went into WHM and edited a DNS zone. I added an A record to the zone, with "testing" as the subdomain name.
It won't resolve.
I used nslookup:
-bash-3.00$ nslookup testing.domain.com
Server: 69.73.181.166
Address: 69.73.181.166#53
** server can't find testing.domain.com: NXDOMAIN
I tried nslookup specifically querying my private nameserver:
nslookup testing.domain.com @ns1.privatenameserver.org
nslookup: couldn't get address for 'testing.domain.com': not found
I used SQUISH.NET to traverse my DNS and got:
Asking vns1.nocdirect.com (64.22.65.220) for testing.domain.com (type A)
Error: No such domain
HMMMMM, that's odd: I had been wondering why my private nameservers were on this particular domain's DNS zone. I haven't looked at this in YEARS but I was fairly certain that for this domain I'd be using the generic nocdirect nameservers.
At first I was thinking this might be a propagation issue, but I was very careful not to use the subdomain name before creating it. Now I fear this is just a symptom of a bigger problem. My EDIT DNS funtion is storing that somewhere and is pointing to my private nameserver but DNS traversal (and simple whois lookups) shows this domain pointing to nocdirect nameservers.
When I save the zone I get the following messages from WHM:
zone domain.com/IN: loaded serial 2008112604 OK
nameserver: reload skipped on myservername (nameserver disabled)
But I'm used to seeing lots of gobbledygook coming from WHM when you update a zone. Is this a real error message this time?
EDIT: I checked my registrar, and sure enough I point to vns1.nocdirect.com. So if I just update my DNS zone to agree, will everything just sort of work? I mean, they are really supposed to be the same nameservers under the skin, no?
Anyone have any ideas what is wrong? Is DNS Zone editing just broken? What is it looking at to pull the wrong nameserver info? Where is this being saved?


LinkBack URL
About LinkBacks




Reply With Quote
Bookmarks