DNS Fails intermittently

[Dazzled]

Thanks angelos.

This morning it has still been slow to complete loading the page components of various sites, so I prepended 220.233.0.4 into dhclient.conf to force a modem bypass (auto is still reading 220.233.0.3, 8.8.8.8 ) . The result is unchanged - connection times acceptable if not quick (eg, 280.7 ms for abc.net.au), followed by long waits for the referred files (total 17 secs for the abc news page). This forum is similar.

Some lookups to 220.233.0.4 have had packet return times of over 480 ms.

[danielp]

Hi,

This problem still persists today.

Code: Select all

> www.hertz.com
Server:		58.96.1.28
Address:	58.96.1.28#53

** server can't find www.hertz.com.Home: SERVFAIL
> www.hertz.com
Server:		58.96.1.28
Address:	58.96.1.28#53

Non-authoritative answer:
www.hertz.com	canonical name = www.hertz.com.edgekey.net.
www.hertz.com.edgekey.net	canonical name = e7128.a.akamaiedge.net.
Name:	e7128.a.akamaiedge.net
Address: 23.37.134.193

hmm.. maybe my client is attaching .Home (search domain) after it times out?

[Dazzled]

I just timed the loading of http://www.hertz.com. 679.1 ms waiting for connection, Subsequent processing brought this up to 807ms. Then a slow assembling of the files like the previous log. The first request was at 13:34:51.337 and the last at 13:36:39.140 (hs) so 108 seconds to request all components.

Edit

Code: Select all

$ dig @58.96.1.28 www.hertz.com

; <<>> DiG 9.4.2-P2.1 <<>> @58.96.1.28 www.hertz.com
; (1 server found)
;; global options:  printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 20303
;; flags: qr rd ra; QUERY: 1, ANSWER: 3, AUTHORITY: 8, ADDITIONAL: 8

;; QUESTION SECTION:
;www.hertz.com.			IN	A

;; ANSWER SECTION:
www.hertz.com.		296	IN	CNAME	www.hertz.com.edgekey.net.
www.hertz.com.edgekey.net. 896	IN	CNAME	e7128.a.akamaiedge.net.
e7128.a.akamaiedge.net.	16	IN	A	23.37.134.193

;; AUTHORITY SECTION:
a.akamaiedge.net.	2086	IN	NS	n2a.akamaiedge.net.
a.akamaiedge.net.	2086	IN	NS	n0a.akamaiedge.net.
a.akamaiedge.net.	2086	IN	NS	n5a.akamaiedge.net.
a.akamaiedge.net.	2086	IN	NS	n7a.akamaiedge.net.
a.akamaiedge.net.	2086	IN	NS	n1a.akamaiedge.net.
a.akamaiedge.net.	2086	IN	NS	n4a.akamaiedge.net.
a.akamaiedge.net.	2086	IN	NS	n6a.akamaiedge.net.
a.akamaiedge.net.	2086	IN	NS	n3a.akamaiedge.net.

;; ADDITIONAL SECTION:
n0a.akamaiedge.net.	5185	IN	A	88.221.81.192
n1a.akamaiedge.net.	8617	IN	A	88.221.81.192
n2a.akamaiedge.net.	4716	IN	A	125.56.205.213
n3a.akamaiedge.net.	5186	IN	A	88.221.81.192
n4a.akamaiedge.net.	8617	IN	A	125.56.205.213
n5a.akamaiedge.net.	4717	IN	A	184.84.223.82
n6a.akamaiedge.net.	5185	IN	A	125.56.205.212
n7a.akamaiedge.net.	8617	IN	A	125.56.205.214

;; Query time: 674 msec
;; SERVER: 58.96.1.28#53(58.96.1.28)
;; WHEN: Wed Mar 19 13:53:03 2014
;; MSG SIZE  rcvd: 391

674 ms for name server query.

[Dazzled]

Changed resolve.conf to use the modem. Still very slow lookups, eg:
dig www.hertz.com
.........
;; Query time: 2211 msec
;; SERVER: 192.168.1.1#53(192.168.1.1)
;; WHEN: Wed Mar 19 16:41:12 2014
;; MSG SIZE rcvd: 119

[angelos]

Hi Dazzled,

Your issue has been raised to our Sysadmins. We will get back to you soon.

Please do not hesitate to post more info on this as and when you find any.

[Dazzled]

Pings are good this morning. Lookups are improved:
(using hertz.com, that gave danielp trouble)

$ dig @220.233.0.4 http://www.hertz.com
...
;; Query time: 488 msec
;; SERVER: 220.233.0.4#53(220.233.0.4)
;; WHEN: Thu Mar 20 08:32:09 2014
;; MSG SIZE rcvd: 391

$ dig @220.233.0.3 http://www.hertz.com
...
;; Query time: 252 msec
;; SERVER: 220.233.0.3#53(220.233.0.3)
;; WHEN: Thu Mar 20 08:32:22 2014
;; MSG SIZE rcvd: 391

$ dig @8.8.8.8 http://www.hertz.com
...
;; Query time: 31 msec
;; SERVER: 8.8.8.8#53(8.8.8.
;; WHEN: Thu Mar 20 08:32:36 2014
;; MSG SIZE rcvd: 119

[Dazzled]

Here is a log for this forum home page this morning, using the modem (currently 220.233.0.3, 8.8.8. as name server. The waiting times column is the period between constructing a request and a server reply. Not perfect, but usable.

danielp's Hertz site is still annoyingly slow, but it is built from very many parts.

[stickmatrix]

I'm also having DNS issues where I can't connect to a website and might have to refresh it multiple times before it works.
What's worse is I'm using a program which checks in intermittently to make sure I'm using a valid serial and it will prompt to log-in if the dns if i don't reach the ip on the first try and interrupt whatever i'm doing.

auto dns gave me 58.96.1.28 and 220.233.0.3

Also having issues if i use opendns or google dns, happens on any website at random and nothing specific.

[SysAdmin]

Same story tonight. For the forum, GET https://forum.exetel.com.au/ took 12.7 secs to reply, GET styles/Exetel/template/styleswitcher.js took another 4.9 secs for a reply. Name servers unchanged.

Google searches are much slower.

Can you try 220.233.0.4 as your primary DNS server tonight?

That server has been upgraded to better hardware with (much) more resources. So far, from our usage here, it's looking good.

Andrew

[Dazzled]

Shall do. I'm on nameserver 192.168.1.1 (that is 220.233.0.3) at present.

[SysAdmin]

Shall do. I'm on nameserver 192.168.1.1 (that is 220.233.0.3) at present.

Thanks. I'm going to do one more change to it (so there might be a momentary hiccup in the next 30 mins - not something I'm happy about but, well...) and, hopefully, that'll be that.

[SysAdmin]

Shall do. I'm on nameserver 192.168.1.1 (that is 220.233.0.3) at present.

Thanks. I'm going to do one more change to it (so there might be a momentary hiccup in the next 30 mins - not something I'm happy about but, well...) and, hopefully, that'll be that.

And done. Unless there's an issue now it's not getting touched.

Andrew

[Dazzled]

Righto. Using 220.233.0.4. danielp's Hertz site is much improved, though it is really a dog's breakfast. I'm happy so far.

This forum is as follows (the blue bars are wait times):

[thejeg]

For those who are still having DNS issues, please make sure that you do a hard reset on your modem reconfigure and let the modem obtain auto DNS settings.

We have done some changes and this will trigger for the DNS settings to be changed. But for those who are still having problems, a Hard reset is a must.

[danielp]

So far it is better across 58.96.1.28, 220.233.0.[34] - with 220.233.0.4 looking pretty good. I see hot cache hits at 33ms over adsl, with an upper limit of around 700ms. I'll keep testing before I commit this to my modem.

Do all customers really need to reset their modem (why???)? I heard many neighbours using the service complaining that their service wasn't working well. Some where fairly irate.

If you're in the mood to fix other DNS issues, 58.96.1.28 still won't resolve (SERVFAIL) http://www.nsa.gov. The other servers do.