Koozali.org: home of the SME Server

dnsroot failed

Offline globalsi

  • ****
  • 167
  • +0/-0
Re: dnsroot failed
« Reply #15 on: November 19, 2014, 11:10:59 PM »
Thank Charlie for all the answers.

It seems that there actually is a problem with orange.fr, but the blocking problem must come from my SME.
Orange is the largest ISP in France and hundreds of thousands of users use it every day.

Furthermore, I have this problem with only this SME, all my other servers (SME or not) have no problems with orange.

I try to put logs more complete.

guest22

Re: dnsroot failed
« Reply #16 on: November 19, 2014, 11:43:15 PM »
Sorry if I speak bad, English is not my native language.  :(
I meant that I misunderstood what Daniel was writing.
I would not say that Daniel had asked me to do it.


No apology required at all. This is a global community.

Offline globalsi

  • ****
  • 167
  • +0/-0
Re: dnsroot failed
« Reply #17 on: November 20, 2014, 12:58:47 AM »
When i restart dnscache,
Code: [Select]
[root@MYSME8 ~]# > /var/log/dnscache.forwarder/current ; signal-event dns-updateThere is immediately the problem with 192.168.o.100 instead of 192.168.0.100

Quote
2014-11-20 00:42:13.788187500 starting
2014-11-20 00:42:14.580552500 query 1 127.0.0.2:11735:17932 a 192.168.o.100.
2014-11-20 00:42:14.580566500 tx 0 a 192.168.o.100. . 192.58.128.30 193.0.14.129 192.203.230.10 199.7.91.13 199.7.83.42 128.63.2.53 202.12.27.33 192.5.5.241 198.41.0.4 192.228.79.201 192.33.4.12 192.112.36.4 192.36.148.17
2014-11-20 00:42:14.580614500 query 2 127.0.0.2:65192:55283 aaaa 192.168.o.100.
2014-11-20 00:42:14.580622500 tx 0 aaaa 192.168.o.100. . 192.58.128.30 128.63.2.53 192.5.5.241 193.0.14.129 192.112.36.4 202.12.27.33 198.41.0.4 192.203.230.10 192.228.79.201 192.36.148.17 199.7.91.13 192.33.4.12 199.7.83.42
2014-11-20 00:42:14.614415500 nxdomain 192.58.128.30 3600 192.168.o.100.
2014-11-20 00:42:14.614456500 sent 1
2014-11-20 00:42:14.614994500 nxdomain 192.58.128.30 3600 192.168.o.100.
2014-11-20 00:42:14.615002500 sent 2
2014-11-20 00:42:14.615537500 query 3 127.0.0.2:65166:47736 a 192.168.o.100.www.my-wwwdomain.com.
2014-11-20 00:42:14.615538500 tx 0 a 192.168.o.100.www.my-wwwdomain.com. . 192.228.79.201 192.58.128.30 192.33.4.12 192.203.230.10 193.0.14.129 199.7.83.42 199.7.91.13 198.41.0.4 192.112.36.4 128.63.2.53 192.5.5.241 192.36.148.17 202.12.27.33
2014-11-20 00:42:14.615776500 query 4 127.0.0.2:12483:14387 aaaa 192.168.o.100.www.my-wwwdomain.com.
2014-11-20 00:42:14.615777500 tx 0 aaaa 192.168.o.100.www.my-wwwdomain.com. . 199.7.83.42 198.41.0.4 192.5.5.241 199.7.91.13 192.36.148.17 192.228.79.201 192.58.128.30 193.0.14.129 202.12.27.33 192.33.4.12 128.63.2.53 192.203.230.10 192.112.36.4
2014-11-20 00:42:14.662921500 rr 199.7.83.42 172800 a a.gtld-servers.net. 192.5.6.30
2014-11-20 00:42:14.662922500 rr 199.7.83.42 172800 a b.gtld-servers.net. 192.33.14.30
2014-11-20 00:42:14.662922500 rr 199.7.83.42 172800 a c.gtld-servers.net. 192.26.92.30
2014-11-20 00:42:14.662923500 rr 199.7.83.42 172800 a d.gtld-servers.net. 192.31.80.30
2014-11-20 00:42:14.662923500 rr 199.7.83.42 172800 a e.gtld-servers.net. 192.12.94.30
2014-11-20 00:42:14.662932500 rr 199.7.83.42 172800 a f.gtld-servers.net. 192.35.51.30
2014-11-20 00:42:14.662933500 rr 199.7.83.42 172800 a g.gtld-servers.net. 192.42.93.30
2014-11-20 00:42:14.662933500 rr 199.7.83.42 172800 a h.gtld-servers.net. 192.54.112.30
2014-11-20 00:42:14.662934500 rr 199.7.83.42 172800 a i.gtld-servers.net. 192.43.172.30
2014-11-20 00:42:14.662935500 rr 199.7.83.42 172800 a j.gtld-servers.net. 192.48.79.30
2014-11-20 00:42:14.662939500 rr 199.7.83.42 172800 a k.gtld-servers.net. 192.52.178.30
2014-11-20 00:42:14.662940500 rr 199.7.83.42 172800 a l.gtld-servers.net. 192.41.162.30
2014-11-20 00:42:14.662940500 rr 199.7.83.42 172800 a m.gtld-servers.net. 192.55.83.30
2014-11-20 00:42:14.662945500 rr 199.7.83.42 172800 ns  com. a.gtld-servers.net.
2014-11-20 00:42:14.662946500 rr 199.7.83.42 172800 ns  com. b.gtld-servers.net.
2014-11-20 00:42:14.662959500 rr 199.7.83.42 172800 ns  com. c.gtld-servers.net.
2014-11-20 00:42:14.662960500 rr 199.7.83.42 172800 ns  com. d.gtld-servers.net.
2014-11-20 00:42:14.662961500 rr 199.7.83.42 172800 ns  com. e.gtld-servers.net.
2014-11-20 00:42:14.662961500 rr 199.7.83.42 172800 ns  com. f.gtld-servers.net.
2014-11-20 00:42:14.662962500 rr 199.7.83.42 172800 ns  com. g.gtld-servers.net.
2014-11-20 00:42:14.662962500 rr 199.7.83.42 172800 ns  com. h.gtld-servers.net.
2014-11-20 00:42:14.662963500 rr 199.7.83.42 172800 ns  com. i.gtld-servers.net.
2014-11-20 00:42:14.662963500 rr 199.7.83.42 172800 ns  com. j.gtld-servers.net.
...

I want to try to change for a few seconds, the LAN IP address of my server (for example 192.168.11.100) and then set the original. This could force the reconfiguration of dnscache and remove this 192.168.o.100.  :D

Do you find it a good idea?

Offline CharlieBrady

  • *
  • 6,918
  • +3/-0
Re: dnsroot failed
« Reply #18 on: November 20, 2014, 02:20:55 AM »
Do you find it a good idea?

No because you don't know what is causing the 192.168.o.100 lookup, and you also don't know whether that has anything to do with the www.orange.fr lookup problem.

You shouldn't be doing this;

Code: [Select]
[root@MYSME8 ~]# > /var/log/dnscache.forwarder/current

You will be losing log messages by doing that.

You should also look at both dnscache and dnscache.forwarder log files - together they will give you a more complete view of what is happening.

I see you also have aaaa record lookups in your log, so you have IPv6 enabled on at least one device on your network.

Since this might be a bug, you'd be better off reporting your investigations via the bug tracker, where you can at least attach complete log files, rather than showing very short segments of them here.

Offline globalsi

  • ****
  • 167
  • +0/-0
Re: dnsroot failed
« Reply #19 on: November 20, 2014, 09:44:41 AM »