Koozali.org: home of the SME Server

dnsroot failed

Offline globalsi

  • *****
  • 167
  • +0/-0
dnsroot failed
« on: November 18, 2014, 06:45:36 PM »
Hello,
I have a problem with my SME 8.1

Since 4 days, when the DNS server is set to work directly with the servers root, some names aren't resolved (for example *.orange.fr ) .
If I choose to work with another DNS server (my router for example), no problems with the same names.

I restart dnscache:
Code: [Select]
/etc/init.d/dnscache restart  -> same problems
Then I looked the file /etc/dnsroots.global :
Quote
198.41.0.4
128.9.0.107
192.33.4.12
128.8.10.90
192.203.230.10
192.5.5.241
192.112.36.4
128.63.2.53
192.36.148.17
198.41.0.10
193.0.14.129
198.32.64.12
202.12.27.33

Which is very different from what it should be: https://www.iana.org/domains/root/servers
Quote
198.41.0.4
192.228.79.201
192.33.4.12
199.7.91.13
192.203.230.10
192.5.5.241
192.112.36.4
128.63.2.53
192.36.148.17
192.58.128.30
193.0.14.129
199.7.83.42
202.12.27.33

More strange (for me) : If i run
Code: [Select]
signal-event dns-updateI can solve the first (and only the first) domain name
Example :
Code: [Select]
[root@MYSME8 ~]# ping www.orange.fr
PING d.hpc.gtm.fti.net (193.252.148.241) 56(84) bytes of data.
64 bytes from vip1.dyn.hpo.s1.fti.net (193.252.148.241): icmp_seq=1 ttl=246 time=47.5 ms
64 bytes from vip1.dyn.hpo.s1.fti.net (193.252.148.241): icmp_seq=2 ttl=246 time=63.9 ms
--- d.hpc.gtm.fti.net ping statistics ---
2 packets transmitted, 2 received, 0% packet loss, time 2426ms
rtt min/avg/max/mdev = 47.593/55.792/63.992/8.202 ms
[root@MYSME8 ~]# ping smtp.orange.fr
ping: unknown host smtp.orange.fr
[root@MYSME8 ~]# ping pop.orange.fr
ping: unknown host pop.orange.fr

[root@MYSME8 ~]# signal-event dns-update
[root@MYSME8 ~]# ping smtp.orange.fr
PING smtp.orange.fr (193.252.22.84) 56(84) bytes of data.
64 bytes from smtpauth.wanadoo.fr (193.252.22.84): icmp_seq=1 ttl=247 time=36.6 ms
64 bytes from smtpauth.wanadoo.fr (193.252.22.84): icmp_seq=2 ttl=247 time=37.2 ms
64 bytes from smtpauth.wanadoo.fr (193.252.22.84): icmp_seq=3 ttl=247 time=36.5 ms
--- smtp.orange.fr ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 7089ms
rtt min/avg/max/mdev = 36.583/36.834/37.235/0.361 ms
[root@MYSME8 ~]# ping www.orange.fr
ping: unknown host www.orange.fr
[root@MYSME8 ~]# ping pop.orange.fr
ping: unknown host pop.orange.fr


1/ Is it normal it's not up to date (I have another SME 8.1 with the same dnsroot and all is fine  :? )?
2/ How to force the update (by editing directly the file?)?
3/ Can it explain my problem of DNS resolution ?

Thanks.

Offline Daniel B.

  • *
  • 1,700
  • +0/-0
    • Firewall Services, la sécurité des réseaux
Re: dnsroot failed
« Reply #1 on: November 18, 2014, 06:52:03 PM »
Not sure why it doesn't resolve (I run several servers in france and had no problem to resolve any *.orange.fr so far), but anyway, please open a new bug to track the root DNS issue (if they are out of date, we need to update this)
C'est la fin du monde !!! :lol:

Offline CharlieBrady

  • *
  • 6,918
  • +3/-0
Re: dnsroot failed
« Reply #2 on: November 18, 2014, 08:10:08 PM »
Not sure why it doesn't resolve (I run several servers in france and had no problem to resolve any *.orange.fr so far), but anyway, please open a new bug to track the root DNS issue (if they are out of date, we need to update this)

True, but it doesn't matter if a few are out of date. That list is just an initial 'hint'. dnscache soon learns the up-to-date list.

Offline CharlieBrady

  • *
  • 6,918
  • +3/-0
Re: dnsroot failed
« Reply #3 on: November 18, 2014, 08:12:39 PM »
3/ Can it explain my problem of DNS resolution ?

No.

To see what dnscache is doing while trying to resolve a name, look at:

perl dnscache-log.pl < /var/log/dnscache.forwarder/current | tai64nlocal | less


Offline CharlieBrady

  • *
  • 6,918
  • +3/-0
Problems resolving *.orange.fr addresses
« Reply #4 on: November 18, 2014, 08:54:08 PM »
FWIW, this is what I see:

-bash-3.00$ host www.orange.fr
www.orange.fr is an alias for www.orange.fr.multis.x-echo.com.
www.orange.fr.multis.x-echo.com is an alias for d.hpc.gtm.fti.net.
d.hpc.gtm.fti.net has address 193.252.122.103
-bash-3.00$ host pop.orange.fr
pop.orange.fr has address 80.12.242.60
pop.orange.fr has address 80.12.242.90
pop.orange.fr has address 80.12.242.143
pop.orange.fr has address 80.12.242.149
pop.orange.fr has address 193.252.22.56
pop.orange.fr has address 193.252.22.90
pop.orange.fr has address 193.252.23.65
pop.orange.fr has address 80.12.242.8
pop.orange.fr has address 80.12.242.14
pop.orange.fr has address 80.12.242.51
-bash-3.00$ host smtp.orange.fr
smtp.orange.fr has address 193.252.22.86
smtp.orange.fr has address 193.252.22.84
-bash-3.00$

Offline globalsi

  • *****
  • 167
  • +0/-0
Re: dnsroot failed
« Reply #5 on: November 19, 2014, 01:03:30 AM »
No.

To see what dnscache is doing while trying to resolve a name, look at:

perl dnscache-log.pl < /var/log/dnscache.forwarder/current | tai64nlocal | less

Hi, here the log
Code: [Select]
[root@MYSME8 ~]# > /var/log/dnscache.forwarder/current
[root@MYSME8 ~]# ping www.orange.fr
Quote
ping: unknown host www.orange.fr
Code: [Select]
[root@MYSME8 ~]# perl /var/service/dnscache/dnscache-log.pl < /var/log/dnscache.forwarder/current | tai64nlocal
Quote
2014-11-19 00:53:53.770015500 query 18459 127.0.0.2:13905:42774 a 192.168.o.100.com.
2014-11-19 00:53:53.770027500 cached nxdomain 192.168.o.100.com.
2014-11-19 00:53:53.770044500 sent 18459
2014-11-19 00:53:53.770258500 query 18460 127.0.0.2:35229:48526 aaaa 192.168.o.100.com.
2014-11-19 00:53:53.770267500 cached nxdomain 192.168.o.100.com.
2014-11-19 00:53:53.770283500 sent 18460
2014-11-19 00:53:54.585585500 query 18461 127.0.0.2:7855:16163 a www.orange.fr.
2014-11-19 00:53:54.585604500 cached ns orange.fr. ns3.orange.fr.
2014-11-19 00:53:54.585605500 cached ns orange.fr. ns2.orange.fr.
2014-11-19 00:53:54.585605500 cached ns orange.fr. ns1.orange.fr.
2014-11-19 00:53:54.585606500 cached ns orange.fr. ns4.orange.fr.
2014-11-19 00:53:54.585615500 cached a ns3.orange.fr.
2014-11-19 00:53:54.585616500 cached a ns2.orange.fr.
2014-11-19 00:53:54.585623500 cached a ns1.orange.fr.
2014-11-19 00:53:54.585624500 cached a ns4.orange.fr.
2014-11-19 00:53:54.585631500 tx 0 a www.orange.fr. orange.fr. 80.10.200.224 80.10.201.224 80.10.203.224 80.10.202.224
2014-11-19 00:53:56.565736500 query 18462 127.0.0.2:61987:10757 a www.orange.fr.
2014-11-19 00:53:56.565751500 cached ns orange.fr. ns3.orange.fr.
2014-11-19 00:53:56.565752500 cached ns orange.fr. ns2.orange.fr.
2014-11-19 00:53:56.565753500 cached ns orange.fr. ns1.orange.fr.
2014-11-19 00:53:56.565754500 cached ns orange.fr. ns4.orange.fr.
2014-11-19 00:53:56.565762500 cached a ns3.orange.fr.
2014-11-19 00:53:56.565763500 cached a ns2.orange.fr.
2014-11-19 00:53:56.565764500 cached a ns1.orange.fr.
2014-11-19 00:53:56.565765500 cached a ns4.orange.fr.
2014-11-19 00:53:56.565772500 tx 0 a www.orange.fr. orange.fr. 80.10.202.224 80.10.203.224 80.10.200.224 80.10.201.224
2014-11-19 00:53:59.585850500 query 18463 127.0.0.2:27967:32224 a www.orange.fr.
2014-11-19 00:53:59.585873500 cached ns orange.fr. ns3.orange.fr.
2014-11-19 00:53:59.585874500 cached ns orange.fr. ns2.orange.fr.
2014-11-19 00:53:59.585875500 cached ns orange.fr. ns1.orange.fr.
2014-11-19 00:53:59.585876500 cached ns orange.fr. ns4.orange.fr.
2014-11-19 00:53:59.585877500 cached a ns3.orange.fr.
2014-11-19 00:53:59.585878500 cached a ns2.orange.fr.
2014-11-19 00:53:59.585878500 cached a ns1.orange.fr.
2014-11-19 00:53:59.585887500 cached a ns4.orange.fr.
2014-11-19 00:53:59.585887500 tx 0 a www.orange.fr. orange.fr. 80.10.202.224 80.10.203.224 80.10.200.224 80.10.201.224
2014-11-19 00:54:01.145954500 query 18464 127.0.0.2:60509:21610 a 192.168.o.100.
2014-11-19 00:54:01.145970500 cached nxdomain 192.168.o.100.
2014-11-19 00:54:01.145984500 sent 18464
2014-11-19 00:54:01.146009500 query 18465 127.0.0.2:5665:899 aaaa 192.168.o.100.
2014-11-19 00:54:01.146011500 cached nxdomain 192.168.o.100.
2014-11-19 00:54:01.146028500 sent 18465
2014-11-19 00:54:01.146606500 query 18466 127.0.0.2:12686:5268 a 192.168.o.100.www.my-wwwdomain.com.
2014-11-19 00:54:01.146608500 cached nxdomain 192.168.o.100.www.my-wwwdomain.com.
2014-11-19 00:54:01.146620500 sent 18466
2014-11-19 00:54:01.146641500 query 18467 127.0.0.2:20085:22087 aaaa 192.168.o.100.www.my-wwwdomain.com.
2014-11-19 00:54:01.146648500 cached nxdomain 192.168.o.100.www.my-wwwdomain.com.
2014-11-19 00:54:01.146667500 sent 18467
2014-11-19 00:54:01.147087500 query 18468 127.0.0.2:28658:13295 a 192.168.o.100.com.
2014-11-19 00:54:01.147095500 cached ns 100.com. ns1.duowanns.com.
2014-11-19 00:54:01.147101500 cached ns 100.com. ns2.duowanns.com.
2014-11-19 00:54:01.147102500 cached ns 100.com. ns3.duowanns.com.
2014-11-19 00:54:01.147109500 cached a ns1.duowanns.com.
2014-11-19 00:54:01.147109500 cached a ns2.duowanns.com.
2014-11-19 00:54:01.147116500 cached a ns3.duowanns.com.
2014-11-19 00:54:01.147126500 tx 0 a 192.168.o.100.com. 100.com. 124.95.153.169 222.73.62.137 119.188.71.249 119.188.71.250 124.95.153.170 183.61.2.251 183.61.2.250 222.73.62.136 222.73.62.138 183.61.2.249 119.188.71.251 124.95.153.171
2014-11-19 00:54:01.147334500 query 18469 127.0.0.2:33102:19307 aaaa 192.168.o.100.com.
2014-11-19 00:54:01.147342500 cached ns 100.com. ns1.duowanns.com.
2014-11-19 00:54:01.147343500 cached ns 100.com. ns2.duowanns.com.
2014-11-19 00:54:01.147350500 cached ns 100.com. ns3.duowanns.com.
2014-11-19 00:54:01.147351500 cached a ns1.duowanns.com.
2014-11-19 00:54:01.147357500 cached a ns2.duowanns.com.
2014-11-19 00:54:01.147358500 cached a ns3.duowanns.com.
2014-11-19 00:54:01.147364500 tx 0 aaaa 192.168.o.100.com. 100.com. 124.95.153.171 222.73.62.137 119.188.71.251 183.61.2.249 222.73.62.136 124.95.153.170 124.95.153.169 222.73.62.138 183.61.2.250 119.188.71.250 119.188.71.249 183.61.2.251
2014-11-19 00:54:01.554654500 nxdomain 124.95.153.171 180 192.168.o.100.com.
2014-11-19 00:54:01.554663500 sent 18469
2014-11-19 00:54:01.556612500 nxdomain 124.95.153.169 180 192.168.o.100.com.
2014-11-19 00:54:01.556621500 sent 18468
2014-11-19 00:54:01.557393500 query 18470 127.0.0.2:40570:21693 a 192.168.o.100.
2014-11-19 00:54:01.557393500 cached nxdomain 192.168.o.100.
2014-11-19 00:54:01.557399500 sent 18470
2014-11-19 00:54:01.557447500 query 18471 127.0.0.2:48589:31790 aaaa 192.168.o.100.
2014-11-19 00:54:01.557448500 cached nxdomain 192.168.o.100.
2014-11-19 00:54:01.557448500 sent 18471



192.168.o.100.com. is strange
My SME8.1 is a gateway
ROUTER (192.168.1.1) --- (192.168.1.100) SME8 (192.168.0.100) ----- LAN 192.168.0.1/24
my DomainName is : www.my-wwwdomain.com
my HostName is : MYSME8

Thks.

Offline globalsi

  • *****
  • 167
  • +0/-0
Re: dnsroot failed
« Reply #6 on: November 19, 2014, 01:18:09 AM »
Not sure why it doesn't resolve (I run several servers in france and had no problem to resolve any *.orange.fr so far), but anyway, please open a new bug to track the root DNS issue (if they are out of date, we need to update this)

Hi,
Yes, I haven't this problem on my others servers.

bug reported : http://bugs.contribs.org/show_bug.cgi?id=8673  :-P

Offline CharlieBrady

  • *
  • 6,918
  • +3/-0
Re: dnsroot failed
« Reply #7 on: November 19, 2014, 03:00:20 PM »
Then I looked the file /etc/dnsroots.global :

/etc/dnsroots.global is not used in the dnscache configuration of SME server. The contents of that file has no relevance. It doesn't matter whether it matches the list at iana.org or not.

Offline CharlieBrady

  • *
  • 6,918
  • +3/-0
Re: dnsroot failed
« Reply #8 on: November 19, 2014, 03:10:19 PM »
Yes, I haven't this problem on my others servers.

So that should lead you to suspect something unusual about the configuration of that server.

Quote
bug reported : http://bugs.contribs.org/show_bug.cgi?id=8673  :-P

You've reported the wrong thing. You've reported your concerns about /etc/dnsroots.global, whereas your real problem is the failure of name resolution on that particular server.

Offline CharlieBrady

  • *
  • 6,918
  • +3/-0
Re: dnsroot failed
« Reply #9 on: November 19, 2014, 03:41:23 PM »
192.168.o.100.com. is strange

My guess is you have entered 192.168.o.100 somewhere in place of 192.168.0.100. I'd look at:

grep -r 192.168.o.100 /home/e-smith/db

Whether that has anything to do with your problem with www.orange.fr is an open question.

Offline globalsi

  • *****
  • 167
  • +0/-0
Re: dnsroot failed
« Reply #10 on: November 19, 2014, 03:57:48 PM »
My guess is you have entered 192.168.o.100 somewhere in place of 192.168.0.100. I'd look at:

grep -r 192.168.o.100 /home/e-smith/db

Whether that has anything to do with your problem with www.orange.fr is an open question.

That's a good idea but for information, my configuration was working since nearly 1 year so i don't think I had entered 192.168.o.100 instead of 192.168.0.100

Code: [Select]
[root@MYSME8 ~]# grep -r 192.168.o.100 /home/e-smith/db
[root@MYSME8 ~]# grep -r 192.168.0.100 /home/e-smith/db
Quote
/home/e-smith/db/configuration:InternalInterface=interface|Broadcast|192.168.0.255|Configuration|static|Driver|tg3|HWAddress|a0:b3:cc:e1:12:e2|IPAddress|192.168.0.100|NICBondingOptions|miimon=200 mode=active-backup|Name|eth0|Netmask|255.255.255.0|Network|192.168.0.0
/home/e-smith/db/configuration:LocalIP=192.168.0.100

 :(


Offline globalsi

  • *****
  • 167
  • +0/-0
Re: dnsroot failed
« Reply #11 on: November 19, 2014, 04:03:24 PM »
So that should lead you to suspect something unusual about the configuration of that server.

You've reported the wrong thing. You've reported your concerns about /etc/dnsroots.global, whereas your real problem is the failure of name resolution on that particular server.

I thought Daniel was talking about root DNS out of date.
As you said, i also think the problem is in my configuration and not a a general bug. Should I report this as a bug ?

Thks
« Last Edit: November 19, 2014, 04:10:58 PM by globalsi »

Offline CharlieBrady

  • *
  • 6,918
  • +3/-0
Re: dnsroot failed
« Reply #12 on: November 19, 2014, 05:35:41 PM »
I thought Daniel was talking about root DNS out of date.

No, Daniel didn't say that. You did. Daniel said "if they are out of date, we need to update this".

Quote
As you said, i also think the problem is in my configuration and not a a general bug. Should I report this as a bug ?

We don't know whether there is a bug. You said that www.orange.fr does not resolve, but the log file you showed doesn't show that lookup failing - it's not complete enough.

If you think there might be a bug, then you should create a bug report.

Offline CharlieBrady

  • *
  • 6,918
  • +3/-0
Re: dnsroot failed
« Reply #13 on: November 19, 2014, 08:05:14 PM »
Maybe the problem is that orange.fr has misleading information about its nameservers

http://dnscheck.pingdom.com/?domain=orange.fr&timestamp=1415286687

Listed at g.ext.nic.fr. are:

;; AUTHORITY SECTION:
orange.fr.      172800   IN   NS   ns2.orange.fr.
orange.fr.      172800   IN   NS   ns.wanadoo.fr.
orange.fr.      172800   IN   NS   ns2.wanadoo.fr.
orange.fr.      172800   IN   NS   ns1.orange.fr.

;; ADDITIONAL SECTION:
ns1.orange.fr.      172800   IN   A   80.10.201.224
ns2.orange.fr.      172800   IN   A   80.10.202.224
ns2.wanadoo.fr.      172800   IN   A   80.12.255.159

But listed at ns2.wanadoo.fr are:

;; ANSWER SECTION:
orange.fr.      172800   IN   NS   ns1.orange.fr.
orange.fr.      172800   IN   NS   ns3.orange.fr.
orange.fr.      172800   IN   NS   ns4.orange.fr.
orange.fr.      172800   IN   NS   ns2.orange.fr.

;; ADDITIONAL SECTION:
ns1.orange.fr.      172800   IN   A   80.10.201.224
ns2.orange.fr.      172800   IN   A   80.10.202.224
ns3.orange.fr.      172800   IN   A   80.10.200.224
ns4.orange.fr.      172800   IN   A   80.10.203.224

Looks like the delegation at nic.fr needs to be fixed.

Offline globalsi

  • *****
  • 167
  • +0/-0
Re: dnsroot failed
« Reply #14 on: November 19, 2014, 10:58:54 PM »
No, Daniel didn't say that. You did. Daniel said "if they are out of date, we need to update this".

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.


We don't know whether there is a bug. You said that www.orange.fr does not resolve, but the log file you showed doesn't show that lookup failing - it's not complete enough.

If you think there might be a bug, then you should create a bug report.


Since I do not think this is a general bug (for now), I'm not going to create a bug report.

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 »