I posted this in SM's forum; so I'm just gonna quote it :).

Hello all,

We've recently got a server from here, and we're kind have run into a problem with sorting out general NS issues. Its a new company, but I'm not new to the hosting business, where I was at previously used Cpanel/WHM. Basically I've created the NS's at our totalregistrations, and have the main domains using them, Skylis.net, using ns1/ns2.skylis.net. Now, at this present time, ive got the domain resolving to the server, but its giving what I can gather as the default page for a domain pointing at plesk that isnt set up to use the server yet. Except of course, it is, and theres and account for it.. but I'm thinking its to do with the zonefile issues on the server, and since I never dealt with DNS personally in the previous company nor used Plesk, I not sure what I should be putting down for the DNS template to sort this out; if at all this is the problem.

Help would much be appriciated. Thankyou.

Go into SSH, and do the following

pico /etc/resolv.conf

After doing that add the following, or get rid of what is already in there


domain skylis.net
nameserver xx.xx.xx.xx(use the IP you have for the ns1)

If both nameservers IPs are on the same box, just do that, if they're in different locations, to get the maximum redundancy add another nameserver. Then exit and save.

Then go back into PSA, and goto the Skylis.net domain, and go into it's DNS settings, if you have the NS records setup for them, make sure you have A records for the NS records. So if you have domain.com NS ns1.skylis.net you should have ns1.skylis.net A xx.xx.xx.xx -- See what I mean?

Hope that works, give it a few hours to make sure it fully propogates :)

Thanks. :) I'm giving it a go now :).

Hey. Ive set everything, though you did say leave it to propergate, shouldnt it be working still via links on that box, since it checks the next DNS up, which would have propergated instantly. If so, no change.

Nah, it'll take 24-48 hours for your new NS to register.

What PSA does is, it'll recognize the IP since you put in the resolv.conf, and it'll goto the IP, which gives you that ugly looking PSA default. Give it a day or so, it'll propogate. I've used PSA5-7 and I've always had similar issues with it like this, it'll propogate, just give it some time :)

http://www.dnsreport.com/tools/dnsreport.ch?domain=skylis.net

It should not even take a day for your new settings in DNS to fully propogate over.

Hey, ok, Been looking around fixing other stuff, and something occoured to me.... FTP is working on the domains. this means propagation has been completed, yet i still get the Plesk page error. My inital thoughts are vhost settings in apache now, but i've been thro all the conf files related to them.

Hmm.. that's interesting, but if FTP and everything else is working, DNS is propogated entirely.. no idea what could be causing that, definately not DNS related.

I would say definitely IS dns related.

There are many things that can cause this error. Most common are DNS conflicts in the zone file or when a domain's IP is changed. There are a few other things too. If you could copy and paste the dns file here, it maybe be possible to discern the problem from that. Failing that, I don't mind taking a look at the server - these things are super easy to fix.

Template

<domain>. A <ip>
<domain>. MX (10) mail.<domain>.
<domain>. NS ns1.skylis.net.
<domain>. NS ns2.skylis.net.
<ip> / 24 PTR <domain>.
ftp.<domain>. CNAME <domain>.
mail.<domain>. A <ip>
webmail.<domain>. A <ip>



Skylis.Net

69.56.196.218 / 24 PTR skylis.net.
ftp.skylis.net. CNAME skylis.net.
mail.skylis.net. A 69.56.196.218
ns1.skylis.net. A 69.56.196.219
ns2.skylis.net. A 69.56.196.220
skylis.net. A 69.56.196.218
skylis.net. MX (10) mail.skylis.net.
skylis.net. NS ns1.skylis.net.
skylis.net. NS ns2.skylis.net.
valhalla.skylis.net. A 69.56.196.218
webmail.skylis.net. A 69.56.196.218
www.skylis.net. CNAME skylis.net.

What is this:

valhalla.skylis.net. A 69.56.196.218

Remove it and see it the domain magically appears....

Removed. No Effect.

I now have email fully operational, this cant be a DNS problem, but I cant see an apache issue with this.

Give it some time maybe. But usually a conflict like that would be resolved immediately. Are you sure you have a FTP user/pass set up in the Setup section?

For the domain itself? yes. I can log in domain codes on FTP.

Just updated apache a couple of minor releases. Suddently worked hehe. Thanks everyone.

Told ya it wasn't DNS related :p

man... i'm now having the same problem. unfortunately, i know nothing about upgrading apache. i'm getting a 403 Forbidden error at http://vagrantweb.com. my dns report says this: http://www.dnsreport.com/tools/dnsreport.ch?domain=vagrantweb.com

ftp is working using ftp.vagrantweb.com
email is working.

dang, this is frustrating.

DNSReport has you for 2 major fails, about your IP not being public. You have added them to your eth0 controller in PSA right?

Give me a PM with some specifics and I can diagnose the problem with the DNS.

Most of the redness that was there yesterday has gone - just that last error about the public IPs now.