DNS Reset Turnaround?

TVallier

New Member
I'm asking this here instead of a ticket because I'm not 100% sure it's an issue yet.

I have a number established domains pointing to my VPS. The DNS was set up months ago and prior to this weekend (When I decided it was server cleanup time) things worked fine.

I wiped out the WHM accounts for these domains (Say, example.com and example.net) and obviously took out the parked domains and addon domains with it.

Last night, I created a new WHM account for one domain (example.com) and it's up and running fine now. This morning (About 4hrs ago) I created the second WHM account (example.net) and added two parked domains to the first one.

Now, the primary domain on one (example.com) is up and running, but it's parked domains aren't up, nor is the second WHM account.

Am I just being impatient and need to wait for DNS things to catch up? Seems like I wouldn't need to as the DNS was pointed to my server and it's IP months ago.

Any input? Should I move this into a ticket?

Thanks
 

TVallier

New Member
Hey Paul,

There are "WARN" flags and "FAIL" flags in both parent and ns for all three domains (The second WHM domain and the two parked on the first).

Tommy
 

TVallier

New Member
Two report the following: (One is the second WHM account, the other is one of the parked domains)

Parent:
Warn - Glue at parent nameservers
NS:
Warn - All nameservers report identical NS records
Fail - Lame nameservers
Fail - Missing nameservers 2
Warn - Nameservers on separate class C's
Fail - Single Point of Failure
Fail - Stealth NS record leakage
SOA:
Fail - Stealth NS record leakage

The other parked domain reports the same ... except it isn't reporting the "Glue at parent nameservers" warning.
 

KH-Paul

CTO
Staff member
TVallier,

I believe the problem is related to "Lame nameservers" - this happens when nameservers defined at your domain registrar don't match what you have in your domain's DNS zone. To resolve this you need to either modify nameserver names at your domain registrar or edit domain's DNS zones and change "NS" records to nameserver names as you use at your domain registrar.

Regards,
Paul
 

tremane

New Member
I have the same error when I checked mine, is it to do with recently migrating from another host and changing records with your domain registrar? I changed the records Saturday evening and the transfer was quick but perhaps it does take a little while for DNS things to catch up, as initially suggested? I'm probably completely wrong ... :p
 

rezag

New Member
I just moved to KH and saw this issue with dnsreport

Seems the Plesk template for dns settings creates ns.domain.com. but at the registrar we are registering and using ns1.domain.com and ns2.domain.com should the plesk template be changed to add ns1 and ns2 and not ns?
 

ppc

Moderator
I just moved to KH and saw this issue with dnsreport

Seems the Plesk template for dns settings creates ns.domain.com. but at the registrar we are registering and using ns1.domain.com and ns2.domain.com should the plesk template be changed to add ns1 and ns2 and not ns?
That is correct. You should change it.
 
Top