We help IT Professionals succeed at work.

DNS Setup, webpages are slow to load

pjnutt
pjnutt asked
on
I recently moved a client to a new domain server.  Since migrating to the new server, webpages are very slow to load.  I assume this has something to do with DNS.  I checked the logs, there are no errors, however; I'm not sure that DNS is setup complete or proper.  Can someone help?
Comment
Watch Question

Aaron TomoskyDirector, SD-WAN Solutions
BRONZE EXPERT

Commented:
At a cmd prompt type nslookup -debug domain.com

Author

Commented:

C:\Users\Administrator>nslookup -debug garrison.com
------------
Got answer:
    HEADER:
        opcode = QUERY, id = 1, rcode = NOERROR
        header flags:  response, auth. answer, want recursion, recursion avail.
        questions = 1,  answers = 1,  authority records = 0,  additional = 0

    QUESTIONS:
        3.1.168.192.in-addr.arpa, type = PTR, class = IN
    ANSWERS:
    ->  3.1.168.192.in-addr.arpa
        name = server.garrison.com
        ttl = 1200 (20 mins)

------------
Server:  server.garrison.com
Address:  192.168.1.3

------------
Got answer:
    HEADER:
        opcode = QUERY, id = 2, rcode = NXDOMAIN
        header flags:  response, auth. answer, want recursion, recursion avail.
        questions = 1,  answers = 0,  authority records = 1,  additional = 0

    QUESTIONS:
        garrison.com.garrison.com, type = A, class = IN
    AUTHORITY RECORDS:
    ->  garrison.com
        ttl = 3600 (1 hour)
        primary name server = server.garrison.com
        responsible mail addr = hostmaster.garrison.com
        serial  = 132
        refresh = 900 (15 mins)
        retry   = 600 (10 mins)
        expire  = 86400 (1 day)
        default TTL = 3600 (1 hour)

------------
------------
Got answer:
    HEADER:
        opcode = QUERY, id = 3, rcode = NXDOMAIN
        header flags:  response, auth. answer, want recursion, recursion avail.
        questions = 1,  answers = 0,  authority records = 1,  additional = 0

    QUESTIONS:
        garrison.com.garrison.com, type = AAAA, class = IN
    AUTHORITY RECORDS:
    ->  garrison.com
        ttl = 3600 (1 hour)
        primary name server = server.garrison.com
        responsible mail addr = hostmaster.garrison.com
        serial  = 132
        refresh = 900 (15 mins)
        retry   = 600 (10 mins)
        expire  = 86400 (1 day)
        default TTL = 3600 (1 hour)

------------
------------
Got answer:
    HEADER:
        opcode = QUERY, id = 4, rcode = NOERROR
        header flags:  response, auth. answer, want recursion, recursion avail.
        questions = 1,  answers = 1,  authority records = 0,  additional = 0

    QUESTIONS:
        garrison.com, type = A, class = IN
    ANSWERS:
    ->  garrison.com
        internet address = 192.168.1.3
        ttl = 600 (10 mins)

------------
------------
Got answer:
    HEADER:
        opcode = QUERY, id = 5, rcode = NOERROR
        header flags:  response, auth. answer, want recursion, recursion avail.
        questions = 1,  answers = 0,  authority records = 1,  additional = 0

    QUESTIONS:
        garrison.com, type = AAAA, class = IN
    AUTHORITY RECORDS:
    ->  garrison.com
        ttl = 3600 (1 hour)
        primary name server = server.garrison.com
        responsible mail addr = hostmaster.garrison.com
        serial  = 132
        refresh = 900 (15 mins)
        retry   = 600 (10 mins)
        expire  = 86400 (1 day)
        default TTL = 3600 (1 hour)

------------
Name:    garrison.com
Address:  192.168.1.3


C:\Users\Administrator>
Aaron TomoskyDirector, SD-WAN Solutions
BRONZE EXPERT

Commented:
Looks good to me. Bunch of "no error"s
I'd suggest using firebug's net tab to see what the hold up is
Principal
Commented:
Try a DNS Speed Test and see what you get.  The DNS Server you switched to may not be all that good.

I recomend www.grc.com/dns/benchmark.htm to a lot of people.

Google also has one, but I've never tried it: http://code.google.com/p/namebench/
SteveArchitect/Designer
BRONZE EXPERT

Commented:
"I assume this has something to do with DNS"
What evidence do you have to suggest this is a DNS issue?

This could relate to the gateway, the client's network settings, a busy netwwork or overloaded switch, or even webproxy settings.

Have you tried manually changing the DNS server to a known working one (maybe opendns for example) so you can see if the DNS is actually the cause of the issue?

Author

Commented:
I followed the google site and changed my DNS settings.  Although, DNS changes didn't do any good, I believe the speed of the ISP to be the issue, proving it's not DNS.  Thanks for the responses.

Explore More ContentExplore courses, solutions, and other research materials related to this topic.