Slow WWW against non-WWW

Hi,

I moved servers several months ago and instantly noticed the sites were running a lot slower and have performed tests on IIS, SQL and as many other areas as possible, but I cam across a possible issue yesterday and was hoping to get some info regarding what could cause it.

If I access the site through www.domain.com it takes about 2.5 seconds from start to finish, if I access it through domain.com it takes under a second.

I did have a URL rewrite non www to www, but that I assume would make the issue the other way around, anyway, I have removed this and can already see a speed increase, but was hoping somebody could give me a clue as to why.

Also, when I do a DNS test I get


Superfluous name server listed at parent: ns1.domain1.com

A name server listed at the parent, but not at the child, was found. This is most likely an administrative error. You should update the parent to match the name servers at the child as soon as possible.

Superfluous name server listed at parent: ns2.domain1.com

A name server listed at the parent, but not at the child, was found. This is most likely an administrative error. You should update the parent to match the name servers at the child as soon as possible.

Superfluous name server listed at parent: ns3.domain1.com

A name server listed at the parent, but not at the child, was found. This is most likely an administrative error. You should update the parent to match the name servers at the child as soon as possible.

Superfluous name server listed at parent: ns4.domain1.com

A name server listed at the parent, but not at the child, was found. This is most likely an administrative error. You should update the parent to match the name servers at the child as soon as possible.

Total parent/child glue mismatch.

The parent lists name servers that the child doesnt know about, see details in advanced. This configuration could actually work but breaks very easily if one of these zones change slightly.

Too few IPv4 name servers (1).

Only one IPv4 name server was found for the zone. You should always have at least two IPv4 name servers for a zone to be able to handle transient connectivity problems.

Any help would be appreciated.

Cheers
Karl
Kbba04527Asked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

David Johnson, CD, MVPOwnerCommented:
Fix your name server errors and other dns errors.
0
Kbba04527Author Commented:
Hi,

Apologies, part of my question should have been what do those errors mean as I have added ns1. ns2. ns3. ns4. as A records on the nameserver domain to point to the server ip and that hasn't fixed it.
0
David Johnson, CD, MVPOwnerCommented:
http://www.experts-exchange.com/Networking/Protocols/DNS/Q_27845853.html

A recent question has the answer re: the name server errors.
0
Top Threats of Q1 & How to Defend Against Them

WEBINAR: Join WatchGuard CTO and our Threat Research Team on Aug. 2nd to hear the findings from our Q1 Internet Security Report! Learn more about the top threats detected in the first quarter and how you can defend your business against them!

Kbba04527Author Commented:
Hi,

I looked at this post yesterday, but couldn't identify if the ns and A records needed to be on the domain they were pointing towards or the domain that was the same as the nameserver domain?

Cheers
Karl
0
David Johnson, CD, MVPOwnerCommented:
At your registrar you make the NS records
@ Godaddy@ cloudflare
cloudflare points to my ip address in the A record..

Guessing you are hosting your own website ?? where does www.example.com point to (internally to the web server, which is also your domain controller?
example.com and www.example.com both point to the same Ip address? or does www.exaple.com point to your external ip address?
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
David Johnson, CD, MVPOwnerCommented:
you may want to add cloudflare caching.. just a suggestion
0
Kbba04527Author Commented:
My current setup for the nameserver domain is

Record type      Value      
123.123.123.123 / 24      PTR      mydomain.com.
ftp.mydomain.com.      CNAME      mydomain.com.
ipv4.mydomain.com.      A      123.123.123.123
mydomain.com.      NS      ns2.mydomain.com.
mydomain.com.      NS      ns.mydomain.com.
mydomain.com.      NS      ns3.mydomain.com.
mydomain.com.      NS      ns1.mydomain.com.
mydomain.com.      NS      ns4.mydomain.com.
mydomain.com.      A      123.123.123.123
mydomain.com.      MX (10)      mail.mydomain.com.
mail.mydomain.com.      A      123.123.123.123
mssql.mydomain.com.      A      123.123.123.123
ns.mydomain.com.      A      123.123.123.123
ns1.mydomain.com.      A      123.123.123.123
ns2.mydomain.com.      A      123.123.123.123
ns3.mydomain.com.      A      123.123.123.123
ns4.mydomain.com.      A      123.123.123.123
webmail.mydomain.com.      A      123.123.123.123
www.mydomain.com.      CNAME      mydomain.com.
0
Kbba04527Author Commented:
The DNS issue has been resolved and the issue continues.
0
David Johnson, CD, MVPOwnerCommented:
ns.mydomain.com.      A      123.123.123.123
ns1.mydomain.com.      A      123.123.123.123
ns2.mydomain.com.      A      123.123.123.123
ns3.mydomain.com.      A      123.123.123.123


You have 4 dns servers in  the same domain or does it all have the same ip address?
I can understand cloaking public ip address's but cloaking internal ip address's ?
0
Kbba04527Author Commented:
Apologies, I changed that the other day to fix the nameserver issue and a test reports no nameserver problems at all. The DNs on the domain I am having the speed difference with is

ftp.mydomain.com.      CNAME      mydomain.com.
ipv4.mydomain.com.      A      211.177.220.248
mail.mydomain.com.      A      211.177.220.248
mydomain.com.      NS      ns4.nameserver.com.
mydomain.com.      NS      ns1.nameserver.com.
mydomain.com.      NS      ns3.nameserver.com.
mydomain.com.      NS      ns2.nameserver.com.
mydomain.com.      NS      ns.mydomain.com.
mydomain.com.      A      211.177.220.248
mydomain.com.      MX (10)      mail.mydomain.com.
mssql.mydomain.com.      A      211.177.220.248
ns.mydomain.com.      A      211.177.220.248
webmail.mydomain.com.      A      211.177.220.248
www.mydomain.com.      CNAME      mydomain.com.

I have slightly changed the ips so they're not mine.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2008

From novice to tech pro — start learning today.