Hey guys,
I'm having a problem with my dns server. I am running it on my SM server. It takes an average of 4 seconds to get into one of my sites.. for instance
;; Query time: 4146 msec
;; SERVER: 216.185.111.10#53(ns1.servermatrix.com)
;; WHEN: Sun Nov 27 04:22:54 2005
;; MSG SIZE rcvd: 113
And I was using the command dig @ns1.servermatrix.com www.instagator.com
So I don't get it, why does it take so long to resolve?
Any help would be appreciated!
Runing Linux RHE with Cpanel!
******RESOLVED - SEE LAST POST TO PEOPLE THAT EMAILED ME
Full Version: Slow Name Resolution for websites on my server
Whats your CPU load look like?
Load is at 0.03 .. Nothing is wrong with the server itself..
Its just the dns resolution is slow.. once you wait the 4 seconds, its fine, surf page to page np. Can't figure it out
Its just the dns resolution is slow.. once you wait the 4 seconds, its fine, surf page to page np. Can't figure it out
OK.. This is whats happening, reason why its taking so long is that nameserver 1 is failing.. and I have no clue why.
Windows IP Configuration
Successfully flushed the DNS Resolver Cache.
C:Documents and SettingsInstagator>nslookup ns1.instagator.com
*** Can't find server name for address 192.168.1.1: Non-existent domain
*** Default servers are not available
Server: UnKnown
Address: 192.168.1.1
*** UnKnown can't find ns1.instagator.com: Server failed
C:Documents and SettingsInstagator>nslookup ns2.instagator.com
*** Can't find server name for address 192.168.1.1: Non-existent domain
*** Default servers are not available
Server: UnKnown
Address: 192.168.1.1
Non-authoritative answer:
Name: ns2.instagator.com
Address: 69.xx.xxx.211
It found the second one, but not the first one, why would it do that?
Windows IP Configuration
Successfully flushed the DNS Resolver Cache.
C:Documents and SettingsInstagator>nslookup ns1.instagator.com
*** Can't find server name for address 192.168.1.1: Non-existent domain
*** Default servers are not available
Server: UnKnown
Address: 192.168.1.1
*** UnKnown can't find ns1.instagator.com: Server failed
C:Documents and SettingsInstagator>nslookup ns2.instagator.com
*** Can't find server name for address 192.168.1.1: Non-existent domain
*** Default servers are not available
Server: UnKnown
Address: 192.168.1.1
Non-authoritative answer:
Name: ns2.instagator.com
Address: 69.xx.xxx.211
It found the second one, but not the first one, why would it do that?
Both those URLs resolve for me. Is there actually a working name server running on 192.168.1.1, which is what your PC is using for name resolution? I'm guessing not - it looks like it has cached ns2.instagator.com but not ns1 hence it responds ok for ns2 but not ns1.
Can't believe this issue is still ongoing.. I have tried everything.. I think my next move is to whipe the system clean and then start from scratch because I had a ticket opened for over 2 weeks in orbit but empty promises..
Can any of the staff look at this ticket? 996284PLNT
Can any of the staff look at this ticket? 996284PLNT
192.168.1.1 is most likely the router in your home/office. Go into the router's config pages and see what it is using for DNS resolution.
Ok. Just to point one thing out. This has NOTHING to do with my router or my ISP dns server. This is server side (meaning the box i get from server matrix) . The DiG command is run staight from my server. So Disregard any 192 ips.
The dig command you show is using ns1.servermatrix.com. The nameserver on your machine wouldn't be called that.
You cut and pasted a windows dns query that used 192.168.1.1 as the name server, twice.
Try posting a query that actually uses your nameserver.
For example if I do: "nslookup ns2.instagator.com ns1.instagator.com" I get an authoritative answer in milliseconds.
Your DNSreport looks fine: http://www.dnsreport.com/tools/dnsreport.c...=instagator.com
You cut and pasted a windows dns query that used 192.168.1.1 as the name server, twice.
Try posting a query that actually uses your nameserver.
For example if I do: "nslookup ns2.instagator.com ns1.instagator.com" I get an authoritative answer in milliseconds.
Your DNSreport looks fine: http://www.dnsreport.com/tools/dnsreport.c...=instagator.com
Ok since you are using the DNSREPORT website. Here's my peeve and you can actually see the problem with my server. If you were to run a report on instagator.com, did you notice that there is a 4 second delay before the NS field comes up. it actually stops there for 4 seconds and then it continues. Now, if you were to run a different website, such as yahoo or any other one, there's a slight ms delay, but no 4 second delay.
Again, ns1.servermatrix.com i used as an example. i can use any public domain ns in the dig command and run it, it will come up with a 4 second dig query.
And yes, I used 192.168.1.1 as a nameserver. But that's not the issue. Like I stated previsouly, disregard that.
Again, ns1.servermatrix.com i used as an example. i can use any public domain ns in the dig command and run it, it will come up with a 4 second dig query.
And yes, I used 192.168.1.1 as a nameserver. But that's not the issue. Like I stated previsouly, disregard that.
CODE
bitesize:~ xistence$ dig ns1.instagator.com
; <<>> DiG 9.2.2 <<>> ns1.instagator.com
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 38417
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0
;; QUESTION SECTION:
;ns1.instagator.com. IN A
;; ANSWER SECTION:
ns1.instagator.com. 172800 IN A 69.93.194.210
;; Query time: 106 msec
;; SERVER: 10.10.10.33#53(10.10.10.33)
;; WHEN: Sun Dec 18 22:23:30 2005
;; MSG SIZE rcvd: 52
bitesize:~ xistence$ dig ns2.instagator.com
; <<>> DiG 9.2.2 <<>> ns2.instagator.com
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 9628
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0
;; QUESTION SECTION:
;ns2.instagator.com. IN A
;; ANSWER SECTION:
ns2.instagator.com. 172791 IN A 69.93.194.211
;; Query time: 11 msec
;; SERVER: 10.10.10.33#53(10.10.10.33)
;; WHEN: Sun Dec 18 22:23:39 2005
;; MSG SIZE rcvd: 52
; <<>> DiG 9.2.2 <<>> ns1.instagator.com
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 38417
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0
;; QUESTION SECTION:
;ns1.instagator.com. IN A
;; ANSWER SECTION:
ns1.instagator.com. 172800 IN A 69.93.194.210
;; Query time: 106 msec
;; SERVER: 10.10.10.33#53(10.10.10.33)
;; WHEN: Sun Dec 18 22:23:30 2005
;; MSG SIZE rcvd: 52
bitesize:~ xistence$ dig ns2.instagator.com
; <<>> DiG 9.2.2 <<>> ns2.instagator.com
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 9628
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0
;; QUESTION SECTION:
;ns2.instagator.com. IN A
;; ANSWER SECTION:
ns2.instagator.com. 172791 IN A 69.93.194.211
;; Query time: 11 msec
;; SERVER: 10.10.10.33#53(10.10.10.33)
;; WHEN: Sun Dec 18 22:23:39 2005
;; MSG SIZE rcvd: 52
This is asking my caching nameserver to retrieve the records, after flushing any of it's records.
Those are 11 msec response times.
Ok... Then explain this example that I just took:
; <<>> DiG 9.2.4 <<>> @ns1.servermatrix.com instagator.com
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 9878
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 0
;; QUESTION SECTION:
;instagator.com. IN A
;; ANSWER SECTION:
instagator.com. 86400 IN A 69.93.194.213
;; AUTHORITY SECTION:
instagator.com. 14400 IN NS ns1.instagator.com.
instagator.com. 14400 IN NS ns2.instagator.com.
;; Query time: 4144 msec
;; SERVER: 216.185.111.10#53(ns1.servermatrix.com)
;; WHEN: Mon Dec 19 03:19:11 2005
;; MSG SIZE rcvd: 84
Why is the query time high?
Why is DNSREPORTS ns section hangs for 4 seconds?
After the initial cache, its fine. ms response time.
; <<>> DiG 9.2.4 <<>> @ns1.servermatrix.com instagator.com
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 9878
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 0
;; QUESTION SECTION:
;instagator.com. IN A
;; ANSWER SECTION:
instagator.com. 86400 IN A 69.93.194.213
;; AUTHORITY SECTION:
instagator.com. 14400 IN NS ns1.instagator.com.
instagator.com. 14400 IN NS ns2.instagator.com.
;; Query time: 4144 msec
;; SERVER: 216.185.111.10#53(ns1.servermatrix.com)
;; WHEN: Mon Dec 19 03:19:11 2005
;; MSG SIZE rcvd: 84
Why is the query time high?
Why is DNSREPORTS ns section hangs for 4 seconds?
After the initial cache, its fine. ms response time.
After a tremendous time researching this issue - Root cause was found.
IPv6 Was causing the delay. Bind was also affected by this which should have been resolved in 9.2.6.
Disabling IPv6 in /etc/modules.conf - I added the line "alias net-pf-10 off"
Reboot the server - no more high dig results.
yay for me.
Only 8 months later.
IPv6 Was causing the delay. Bind was also affected by this which should have been resolved in 9.2.6.
Disabling IPv6 in /etc/modules.conf - I added the line "alias net-pf-10 off"
Reboot the server - no more high dig results.
yay for me.
Only 8 months later.
Wow. Only 8 months? Congratulations? 
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.