# No DNS resolving on RED

**URL:** <https://community.ipfire.org/t/no-dns-resolving-on-red/2118>\
**Category:** DNS\
**Created:** [29 April 2020 19:42 UTC](https://community.ipfire.org/t/no-dns-resolving-on-red/2118 "2020-04-29T19:42:07Z")\
**Posts on this page:** 11\
**Page:** 1

<div class="post-metadata">

**Author:** ![anon54383833](https://community.ipfire.org/letter_avatar_proxy/v4/letter/a/9dc877/32.png) [@anon54383833](https://community.ipfire.org/u/anon54383833)\
**Post date:** [29 April 2020 19:42 UTC](https://community.ipfire.org/t/no-dns-resolving-on-red/2118/1 "2020-04-29T19:42:07Z")

</div>

I first failed to upgrade from core 142 to 144. ‘pakfire update’ responded with '‘Giving up: …’ and pakfire logs stated ’ ‘DOWNLOAD INFO: HTTP-Status-Code: 500 - 500  
Can’t connect to [www.mirrorservice.org:443](http://www.mirrorservice.org:443) (Name or service not known)’. Pinging [www.mirrorservice.org](http://www.mirrorservice.org) from RED failed but pinging 212.219.56.184 responded o.k. I am running ipfire (red/green/blue/orange) for quite some time now without major interruption and unchanged configuration  
After I have added ‘nameserver 8.8.8.8’ to /etc/resolv.conf everything worked again. I am not sure if this is the right way to do and would appreciate some advise.

---

<div class="post-metadata">

**Author:** ![sklammer](https://community.ipfire.org/user_avatar/community.ipfire.org/sklammer/32/233_2.png) [@sklammer](https://community.ipfire.org/u/sklammer)\
**Post date:** [29 April 2020 20:12 UTC](https://community.ipfire.org/t/no-dns-resolving-on-red/2118/2 "2020-04-29T20:12:47Z")

</div>

Hello Bernd,

As far as I know the DNS System has been reorganized in the meanwhile. Have you entered the DNS Servers in “Network”-\>“Domain Name System” ?

Greetings

Steffen

---

<div class="post-metadata">

**Author:** ![anon54383833](https://community.ipfire.org/letter_avatar_proxy/v4/letter/a/9dc877/32.png) [@anon54383833](https://community.ipfire.org/u/anon54383833)\
**Post date:** [29 April 2020 20:19 UTC](https://community.ipfire.org/t/no-dns-resolving-on-red/2118/3 "2020-04-29T20:19:05Z")

</div>

Hi Steffen,

yes, I have 8.8.8.8, 8.8.4.4 and 1.1.1.1.  
DNS resolution works without the added /etc/resolv.conf entries for all but RED.

Best Regards  
Bernd

---

<div class="post-metadata">

**Author:** ![anon54383833](https://community.ipfire.org/letter_avatar_proxy/v4/letter/a/9dc877/32.png) [@anon54383833](https://community.ipfire.org/u/anon54383833)\
**Post date:** [29 April 2020 21:15 UTC](https://community.ipfire.org/t/no-dns-resolving-on-red/2118/4 "2020-04-29T21:15:01Z")

</div>

I just saw my problem might be related to this one [https://community.ipfire.org/t/after-update-to-core-141-no-more-pakfire-list-availble/1378/](https://community.ipfire.org/t/after-update-to-core-141-no-more-pakfire-list-availble/1378/)

The temporary work around to proceed with the upgrade from 142 to 144 is to add the DNS server IP to /etc/resolv.conf like I have done. Seems that etc/resolv.conf will be regenerated at reboot.

Let’s see if the upgrade has solved the issue (I can only reboot tonight).

---

<div class="post-metadata">

**Author:** ![anon54383833](https://community.ipfire.org/letter_avatar_proxy/v4/letter/a/9dc877/32.png) [@anon54383833](https://community.ipfire.org/u/anon54383833)\
**Post date:** [30 April 2020 12:46 UTC](https://community.ipfire.org/t/no-dns-resolving-on-red/2118/5 "2020-04-30T12:46:38Z")

</div>

The upgrade didn’t fix the issue. I will reply here [https://community.ipfire.org/t/after-update-to-core-141-no-more-pakfire-list-availble/1378/19](https://community.ipfire.org/t/after-update-to-core-141-no-more-pakfire-list-availble/1378/19) as the topic reflects my problem.

---

<div class="post-metadata">

**Author:** ![pmueller](https://community.ipfire.org/user_avatar/community.ipfire.org/pmueller/32/9019_2.png) [@pmueller](https://community.ipfire.org/u/pmueller)\
**Post date:** [30 April 2020 15:23 UTC](https://community.ipfire.org/t/no-dns-resolving-on-red/2118/6 "2020-04-30T15:23:52Z")

</div>

Hi,

could you please post:

- a screenshot of your DNS configuration
- any lines in `/var/log/messages` containing `unbound`
- the output of `ping 8.8.8.8`

Thanks, and best regards,  
Peter Müller

---

<div class="post-metadata">

**Author:** ![anon54383833](https://community.ipfire.org/letter_avatar_proxy/v4/letter/a/9dc877/32.png) [@anon54383833](https://community.ipfire.org/u/anon54383833)\
**Post date:** [30 April 2020 16:13 UTC](https://community.ipfire.org/t/no-dns-resolving-on-red/2118/7 "2020-04-30T16:13:03Z")

</div>

Hi Peter,

DNS config and messages are attached.  
`ping -c 5 8.8.8.8` returns:

PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.  
64 bytes from 8.8.8.8: icmp\_seq=1 ttl=58 time=12.7 ms  
64 bytes from 8.8.8.8: icmp\_seq=2 ttl=58 time=30.3 ms  
64 bytes from 8.8.8.8: icmp\_seq=3 ttl=58 time=29.8 ms  
64 bytes from 8.8.8.8: icmp\_seq=4 ttl=58 time=14.5 ms  
64 bytes from 8.8.8.8: icmp\_seq=5 ttl=58 time=19.9 ms

— 8.8.8.8 ping statistics —  
5 packets transmitted, 5 received, 0% packet loss, time 4006ms  
rtt min/avg/max/mdev = 12.736/21.491/30.361/7.446 ms

 ![DNS](https://community.ipfire.org/uploads/default/original/2X/4/4e0dde95388a8006dc53af4638866adae77af372.png) [dnsUnbound.zip](https://community.ipfire.org/uploads/short-url/jZU3hDYJdbqNmmTyWKHgtjBy7k2.zip) (54.8 KB)

Thanks in advance  
Bernd

---

<div class="post-metadata">

**Author:** ![anon54383833](https://community.ipfire.org/letter_avatar_proxy/v4/letter/a/9dc877/32.png) [@anon54383833](https://community.ipfire.org/u/anon54383833)\
**Post date:** [1 May 2020 21:20 UTC](https://community.ipfire.org/t/no-dns-resolving-on-red/2118/8 "2020-05-01T21:20:59Z")

</div>

I freshly installed ipfire today and still face the same problem.

---

<div class="post-metadata">

**Author:** ![pmueller](https://community.ipfire.org/user_avatar/community.ipfire.org/pmueller/32/9019_2.png) [@pmueller](https://community.ipfire.org/u/pmueller)\
**Post date:** [2 May 2020 05:49 UTC](https://community.ipfire.org/t/no-dns-resolving-on-red/2118/9 "2020-05-02T05:49:59Z")

</div>

Hi,

sorry for the delay.

Your problem is apparently caused by a syntax error in `/etc/unbound/hosts.conf`:

```
Apr 30 03:31:40 ipfire unbound: [2177:0] error: error parsing local-data at 20 'server1.myipfire 60 IN A 192.168.3.62': Syntax error, could not parse the RR's type

```

Would you mind posting the content of that file here so we can see what is going wrong?

Thanks, and best regards,  
Peter Müller

---

<div class="post-metadata">

**Author:** ![anon54383833](https://community.ipfire.org/letter_avatar_proxy/v4/letter/a/9dc877/32.png) [@anon54383833](https://community.ipfire.org/u/anon54383833)\
**Post date:** [2 May 2020 14:56 UTC](https://community.ipfire.org/t/no-dns-resolving-on-red/2118/10 "2020-05-02T14:56:32Z")

</div>

Thanks Peter. It is working now, but I don’t know why.

I freshly installed ipfire and configured as described earlier. DNS did not resolve on RED and I was therefore not able to install any addons or configure IPS. So I added the nameserver IP in /etc/resolv.conf and then was able to finish the installation and configuration. After reboot tonight /etc/resolv.conf was regenerated as expected without my added nameserver IP and DNS is working correctly on RED now.

There still seems to be a bug but at least a workaround (in my case) exists. Hope this might help others, too.

Thanks again and  
Best Regards  
Bernd

---

<div class="post-metadata">

**Author:** ![pmueller](https://community.ipfire.org/user_avatar/community.ipfire.org/pmueller/32/9019_2.png) [@pmueller](https://community.ipfire.org/u/pmueller)\
**Post date:** [2 May 2020 18:36 UTC](https://community.ipfire.org/t/no-dns-resolving-on-red/2118/11 "2020-05-02T18:36:02Z")

</div>

Hi,

well, I am glad things work by now, but it certainly is not satisfying to  
reinstall and modifying `/etc/resolv.conf`. 😑

Anyway, if you have any more clue about it’s root cause, please open up a  
ticket at [https://bugzilla.ipfire.org/](https://bugzilla.ipfire.org/). Thank you.

Best regards,  
Peter Müller
