Topic: strange dns problem

[henrikmc]

sme 7.5.1

For some reason, my sme dns has gone mad on tomtom, it wont resolve any of its related sites.
www.tomtom.com etc.

Not sure what Im doing wrong here.

dnscache.forwarder log example:

2010-07-13 18:30:39.860339500 query 4044 7f000002:9c4c:4eaf 1 www.tomtom.com.
2010-07-13 18:30:39.860344500 cached ns tomtom.com. ns10.multrix.com.
2010-07-13 18:30:39.860348500 cached ns tomtom.com. ns20.multrix.com.
2010-07-13 18:30:39.860351500 cached 1 ns10.multrix.com.
2010-07-13 18:30:39.860355500 cached 1 ns20.multrix.com.
2010-07-13 18:30:39.860358500 tx 0 1 www.tomtom.com. tomtom.com. c1ad940a c1ad9414


2010-07-13 18:32:35.020037500 servfail www.tomtom.com. input/output error
2010-07-13 18:32:35.020042500 sent 4042 32
2010-07-13 18:32:38.040599500 servfail www.tomtom.com. input/output error
2010-07-13 18:32:38.040604500 sent 4043 32
2010-07-13 18:32:40.022276500 servfail www.tomtom.com. input/output error
2010-07-13 18:32:40.022281500 sent 4044 32

Wot?


doing a dig results in:

[root@hmcdata2 var]# dig www.tomtom.com

; <<>> DiG 9.2.4 <<>> www.tomtom.com
;; global options:  printcmd
;; connection timed out; no servers could be reached

[CharlieBrady]

For some reason, my sme dns has gone mad on tomtom, it wont resolve any of its related sites.
www.tomtom.com etc.

Not sure what Im doing wrong here.

You are not doing anything wrong. The two tomtom.com name servers at ns10.multrix.com (193.173.148.10) and ns20.multrix.com (193.173.148.20) are (maybe were?) not responding to your queries. This is just bad network design by tomtom (or their ISP).

Presumably there is a temporary problem and they will (or have already) fixed it.

[henrikmc]

You are not doing anything wrong. The two tomtom.com name servers at ns10.multrix.com (193.173.148.10) and ns20.multrix.com (193.173.148.20) are (maybe were?) not responding to your queries. This is just bad network design by tomtom (or their ISP).

Presumably there is a temporary problem and they will (or have already) fixed it.

Not sure that is correct. I can reproduce this with another domain also, so far only seen this with this one also. And setting my client to use my isp dns then it resolves fine, but squid then cant deliver the content as it ask's sme servers dns.

[CharlieBrady]

Not sure that is correct. I can reproduce this with another domain also, so far only seen this with this one also. And setting my client to use my isp dns then it resolves fine, but squid then cant deliver the content as it ask's sme servers dns.

In that case, you should be following these instructions:

Don't report problems here - Please report bugs and potential bugs in the bug tracker

Please attach the dnscache and dnscache-forwarder /current log files, and full description of what you have done and what you have observed.

FWIW, "input/output error" usually means that queries were sent to the domain's DNS content servers, and no replies were received.